From: Eric Wong <e@80x24.org>
To: "Dom (shymega) Rodriguez" <shymega@shymega.org.uk>
Cc: meta@public-inbox.org
Subject: Re: Figuring out `public-inbox-fetch`
Date: Thu, 5 Sep 2024 19:33:08 +0000 [thread overview]
Message-ID: <20240905193308.M675816@dcvr> (raw)
In-Reply-To: <24ogn66q2fp42dkbjvg7ypmznb3wlfuuhf45i6vnmitvn2yb3t@b4ww562o7vkt>
"Dom (shymega) Rodriguez" <shymega@shymega.org.uk> wrote:
> Hi.
>
> I've recently been setting up a `public-inbox` mirror on my workstation.
>
> I've cloned the epochs for a few Linux kernel lists, and Spectrum, and
> used `public-inbox-init` to add the lists to the configuration in
> `$HOME`.
>
> However, I'm finding the documentation rather lacking (happy to make
> patches once I figure it out) in terms of examples in some instances.
>
> For example, the `public-inbox-fetch` command, I've pointed the `-C`
> argument to say, `linux-mediatek/git/0.git`, and get the following
> output:
>
> ````
> $ public-inbox-fetch -C projects/mailing-lists/linux-mediatek/git/0.git
That should be pointed to the inbox directory, not the git epoch,
(although epoch seems to work, too...):
$ public-inbox-fetch -C projects/mailing-lists/linux-mediatek/
You shouldn't need to go into deeper directory levels in normal day-to-day use.
> # inbox URL: http://lore.kernel.org/linux-mediatek/
> # /etc/profiles/per-user/shymega/bin/curl -Sf -R -o m-xfHa.tmp http://lore.kernel.org/linux-mediatek/manifest.js.gz
> % Total % Received % Xferd Average Speed Time Time Time Current
> Dload Upload Total Spent Left Speed
> 0 0 0 0 0 0 0 0 --:--:-- --:-100 162 100 162 0 0 5290 0 --:--:-- --:--:-- --:--:-- 5400
> # git --git-dir=/home/shymega/projects/mailing-lists/linux-mediatek/git/0.git fetch
> warning: redirecting to https://lore.kernel.org/linux-mediatek/0/
> # git clone --mirror http://lore.kernel.org/linux-mediatek/git/1.git /home/shymega/projects/mailing-lists/linux-mediatek/git/1.git
> Cloning into bare repository '/home/shymega/projects/mailing-lists/linux-mediatek/git/1.git'...
> remote: Not Found
> fatal: repository 'http://lore.kernel.org/linux-mediatek/git/1.git/' not found
> error: could not lock config file /home/shymega/projects/mailing-lists/linux-mediatek/git/1.git/config: No such file or directory
> git config -f /home/shymega/projects/mailing-lists/linux-mediatek/git/1.git/config include.path ../../all.git/config failed: $?=65280
Everything said, I'm not sure why it's trying 1.git here when
linux-mediatek only has the 0.git epoch...
Viewing the manifest via:
curl https://lore.kernel.org/linux-mediatek/manifest.js.gz | zcat | less
confirms there's only one epoch..
> Am I on the right path here? I'm not sure what I'm doing wrong.
I wonder if something got mangled by lore doing the redirects from http to
https. Perhaps changing the url in git/0.git/config to use https will help
*shrug*
You can also try my slower lore mirror https://yhbt.net/lore/linux-mediatek/
I use for dogfooding new changes.
Also, are you using public-inbox.git or the v1.9.0 release?
I really need to get the 2.0 features done and released but real life
has been sucking more and more every year :x
> Sorry for the 'newbie' question. Although, we all were at one point or
> another.
No worries, it's good for pointing out flaws in documentation :>
> Other than this, I'm relatively happy with `public-inbox` mirroring. I'm
> making a developer-oriented multi-'adapter' NNTP server at the moment,
> which I'm hoping to use myself.
Cool :>
next prev parent reply other threads:[~2024-09-05 19:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 18:45 Figuring out `public-inbox-fetch` Dom (shymega) Rodriguez
2024-09-05 19:33 ` Eric Wong [this message]
2024-09-06 22:42 ` Dom (shymega) Rodriguez
2024-09-07 13:54 ` Eric Wong
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240905193308.M675816@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
--cc=shymega@shymega.org.uk \
/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.
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).