unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: 43637@debbugs.gnu.org
Cc: zimoun <zimon.toutoune@gmail.com>
Subject: [bug#43637] [PATCH] gnu: packages: Add grokmirror.
Date: Sat, 26 Sep 2020 16:58:20 -0400	[thread overview]
Message-ID: <878scww903.fsf@kyleam.com> (raw)
In-Reply-To: <20200926204819.30602-1-kyle@kyleam.com>

A recent message on bug-guix [1] mentioned cloning the archives at
<https://yhetil.org>.  public-inbox archives, including those at
yhetil.org, publish a grokmirror-compatible manifest.  So, if you're
interested in mirroring the Guix-related archives at yhetil.org for any
reason [2], you can use grokmirror to do so in a way that's nicer than
periodically hitting yhetil.org with a git-fetch call for each
Guix-related inbox.

You can clone (and then later update) Guix-related inboxes with

    $ grok-pull -vc /path/to/config

and a config file that looks something like this:

--8<---------------cut here---------------start------------->8---
[core]
toplevel = /path/to/inboxes
manifest = ${toplevel}/manifest.js.gz
log = ${toplevel}/grok.log
loglevel = info
objstore = ${toplevel}/objstore

[pull]
pull_threads = 2
include = /guix-*

[remote]
site = https://yhetil.org
manifest = ${site}/manifest.js.gz
--8<---------------cut here---------------end--------------->8---

[1] https://issues.guix.gnu.org/43528#4
    CAJ3okZ0g25+-wsL2OepE+xMR5QWShmS73hSHsjEmEgYBiOWwAg@mail.gmail.com

[2] to have a fast local copy, to publish your own mirror, to feed the
    archives into some other tool...




  reply	other threads:[~2020-09-26 20:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-26 20:48 [bug#43637] [PATCH] gnu: packages: Add grokmirror Kyle Meyer
2020-09-26 20:58 ` Kyle Meyer [this message]
2020-09-27 20:51 ` bug#43637: " Ludovic Courtès
2020-09-27 21:14   ` [bug#43637] " Kyle Meyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878scww903.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=43637@debbugs.gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).