From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.2 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id C90991F548; Thu, 5 Sep 2024 19:33:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=80x24.org; s=selector1; t=1725564788; bh=CoPcalTVnfgOz3XqCWSKkwlA7fdLJd47bdMDuidH9no=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=YEgP+YglYywVGM3zV3M56AYOrG3eAeBi2oWMcIfN37LnfYSUcrtgG7Mm1sHQG0ptl k5YjPZ3w4HJKpuDZUKqO8mimUi2yZx0nj9Z6Ps6Re2w8StIZ3LXd1sYm2gIgKGmLLt hMmuPvlOIVX52eOCM1ymJHaTRwKwrYZ+FGVUP0cE= Date: Thu, 5 Sep 2024 19:33:08 +0000 From: Eric Wong To: "Dom (shymega) Rodriguez" Cc: meta@public-inbox.org Subject: Re: Figuring out `public-inbox-fetch` Message-ID: <20240905193308.M675816@dcvr> References: <24ogn66q2fp42dkbjvg7ypmznb3wlfuuhf45i6vnmitvn2yb3t@b4ww562o7vkt> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <24ogn66q2fp42dkbjvg7ypmznb3wlfuuhf45i6vnmitvn2yb3t@b4ww562o7vkt> List-Id: "Dom (shymega) Rodriguez" 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 :>