From: Florian Schmaus <flow@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] The uncertain future of repository mirrors
Date: Sun, 30 Mar 2025 13:24:38 +0200 [thread overview]
Message-ID: <fe438273-e6a9-4b0e-83ec-373851977847@gentoo.org> (raw)
In-Reply-To: <87b23159542cbdeac7970756b83db946@levelnine.at>
[-- Attachment #1.1.1: Type: text/plain, Size: 1071 bytes --]
On 30/03/2025 10.11, Michael Mair-Keimberger wrote:
> On 2025-03-21 14:32, Michał Górny wrote:
>> Hello, everyone.
>>
>> TL;DR: I'm thinking of shutting down all gentoo-mirror repositories,
>> except for gentoo and guru.
>
> Hi,
>
> I guess i'm a bit late in this discussion but i wanted to let you know
> this would also affect my gentoo qa scripts. (https://
> gentooqa.levelnine.at). Right now i'm checking the gentoo, guru, kde,
> science and pentoo repositories, syncing the repos from gentoo-mirror
> for the pre-created metadata.
> While the gentoo repository is probably the most valuable, kde, science
> and pentoo checks would be non functional and i probably would have to
> remove them. (at least until i update my script to create the metadata
> myself..)
Updating the script would ideally just consist of adding the line
pkg repo metadata regen --use-local $REPO
to the script.
As radhermit wrote, pkgcraft is pretty fast these days. I do this for
multiple repos on every sync and barely notice it.
- Flow
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 21567 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
prev parent reply other threads:[~2025-03-30 11:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 13:32 [gentoo-dev] The uncertain future of repository mirrors Michał Górny
2025-03-21 14:12 ` orbea
2025-03-21 14:44 ` Michał Górny
2025-03-21 23:50 ` orbea
2025-03-22 7:01 ` Michał Górny
2025-03-22 13:47 ` orbea
2025-03-21 14:12 ` Alexey Sokolov
2025-03-21 14:44 ` Michał Górny
2025-03-21 14:47 ` Alexey Sokolov
2025-03-21 14:55 ` Michał Górny
2025-03-22 1:42 ` Ionen Wolkens
2025-03-22 15:20 ` Jay Faulkner
2025-03-22 15:33 ` Michał Górny
2025-03-22 20:35 ` Richard Freeman
2025-03-22 15:38 ` Sam James
2025-03-22 15:46 ` Michał Górny
2025-03-23 9:46 ` [gentoo-dev] " Anna Vyalkova
2025-03-23 10:17 ` [gentoo-dev] " Gerion Entrup
2025-03-23 17:50 ` Ionen Wolkens
2025-03-24 12:46 ` Mitchell Dorrell
2025-03-25 20:51 ` Michał Górny
2025-03-25 23:15 ` Jay Faulkner
2025-03-26 6:01 ` Michał Górny
2025-03-26 16:00 ` Jay Faulkner
2025-03-28 8:27 ` Florian Schmaus
2025-03-30 8:11 ` Michael Mair-Keimberger
2025-03-30 9:34 ` Tim Harder
2025-03-30 11:24 ` Florian Schmaus [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fe438273-e6a9-4b0e-83ec-373851977847@gentoo.org \
--to=flow@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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