unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: "Dom (shymega) Rodriguez" <shymega@shymega.org.uk>
To: meta@public-inbox.org
Subject: Figuring out `public-inbox-fetch`
Date: Thu, 5 Sep 2024 19:45:16 +0100	[thread overview]
Message-ID: <24ogn66q2fp42dkbjvg7ypmznb3wlfuuhf45i6vnmitvn2yb3t@b4ww562o7vkt> (raw)

[-- Attachment #1: Type: text/plain, Size: 2164 bytes --]

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
# 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
````

Am I on the right path here? I'm not sure what I'm doing wrong.

Sorry for the 'newbie' question. Although, we all were at one point or
another.

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.

Thank you.

Best wishes,
--
Dom Rodriguez

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2024-09-05 18:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05 18:45 Dom (shymega) Rodriguez [this message]
2024-09-05 19:33 ` Figuring out `public-inbox-fetch` Eric Wong
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=24ogn66q2fp42dkbjvg7ypmznb3wlfuuhf45i6vnmitvn2yb3t@b4ww562o7vkt \
    --to=shymega@shymega.org.uk \
    --cc=meta@public-inbox.org \
    /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).