From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Jay Faulkner <jayf@gentoo.org>
Subject: Re: [gentoo-dev] The uncertain future of repository mirrors
Date: Sat, 22 Mar 2025 16:46:26 +0100 [thread overview]
Message-ID: <c5a5d1e28a8b6038fbc18216e2bf8b17e59da8cb.camel@gentoo.org> (raw)
In-Reply-To: <87tt7l2hze.fsf@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1593 bytes --]
On Sat, 2025-03-22 at 15:38 +0000, Sam James wrote:
> Jay Faulkner <jayf@gentoo.org> writes:
>
> > On 3/21/2025 6:42 PM, Ionen Wolkens wrote:
> > > On Fri, Mar 21, 2025 at 02:32:31PM +0100, Michał Górny wrote:
> > > > Hello, everyone.
> > > >
> > > > TL;DR: I'm thinking of shutting down all gentoo-mirror repositories,
> > > > except for gentoo and guru.
> > > Unfortunate, but just to say that I have nothing to say against
> > > dropping these if it's a maintenance burden.
> > >
> > > > So what I'm thinking about is winding most of the project down. We'd
> > > > stop mirroring third-party repositories, and remove most of gentoo-
> > > > mirror organization.
> > > Had one concern but complete removal (rather than keeping mirrors
> > > archived) would mostly handle it. Aka so that users can't keep
> > > sync'ing with these dead mirrors by mistake (often caused issues when
> > > we removed overlays but mirror stayed behind, users wouldn't notice a
> > > thing until lacking updates started to break things).
> >
> >
> > In the OpenStack community, we will put a final commit on HEAD of the
> > primary branch removing all the content and putting an EOL notice in
> > the readme (e.g. https://opendev.org/openstack/ironic-lib ). This may
> > be a good solution in this case as well, potentially?
>
> We can even inject a news item for the repository.
>
I'm thinking of doing a news item in ::gentoo instead. That should have
better UX than the same news item duplicated over a hundred
repositories.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next prev parent reply other threads:[~2025-03-22 15:47 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 [this message]
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
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=c5a5d1e28a8b6038fbc18216e2bf8b17e59da8cb.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=jayf@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