From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 4E2801581EE for ; Sat, 22 Mar 2025 15:34:25 +0000 (UTC) Received: from lists.gentoo.org (bobolink.gentoo.org [140.211.166.189]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) (Authenticated sender: relay-lists.gentoo.org@gentoo.org) by smtp.gentoo.org (Postfix) with ESMTPSA id 1030A3432C5 for ; Sat, 22 Mar 2025 15:34:25 +0000 (UTC) Received: from bobolink.gentoo.org (localhost [127.0.0.1]) by bobolink.gentoo.org (Postfix) with ESMTP id 1261F1104B4; Sat, 22 Mar 2025 15:33:43 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by bobolink.gentoo.org (Postfix) with ESMTPS id 5AE371104AB for ; Sat, 22 Mar 2025 15:33:42 +0000 (UTC) Received: from [192.168.1.1] (c144-156.icpnet.pl [85.221.144.156]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 522C5343228; Sat, 22 Mar 2025 15:33:41 +0000 (UTC) Message-ID: Subject: Re: [gentoo-dev] The uncertain future of repository mirrors From: =?UTF-8?Q?Micha=C5=82_G=C3=B3rny?= To: gentoo-dev@lists.gentoo.org Date: Sat, 22 Mar 2025 16:33:37 +0100 In-Reply-To: <7783ccc4-9c48-4303-a68a-2e572f815d32@gentoo.org> References: <6b358608f6e244cb96ce527ad47b3e0483eaf0c6.camel@gentoo.org> <7783ccc4-9c48-4303-a68a-2e572f815d32@gentoo.org> Organization: Gentoo Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-LJqFKA0UN+VfKYXemNSB" User-Agent: Evolution 3.54.3 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 X-Archives-Salt: 714ec838-0660-450b-a901-0f31cceedb7d X-Archives-Hash: 950826b23410c4917019606665c17f1e --=-LJqFKA0UN+VfKYXemNSB Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, 2025-03-22 at 08:20 -0700, Jay Faulkner wrote: > On 3/21/2025 6:42 PM, Ionen Wolkens wrote: > > On Fri, Mar 21, 2025 at 02:32:31PM +0100, Micha=C5=82 G=C3=B3rny wrote: > > > Hello, everyone. > > >=20 > > > 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. > >=20 > > > 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). >=20 >=20 > In the OpenStack community, we will put a final commit on HEAD of the=20 > primary branch removing all the content and putting an EOL notice in the= =20 > readme (e.g. https://opendev.org/openstack/ironic-lib ). This may be a= =20 > good solution in this case as well, potentially? >=20 Not sure. It would mean that `emerge --sync` will replace all ebuilds with a README file that user might not even notice. I suppose an explicit "repository not found" error may be better here. --=20 Best regards, Micha=C5=82 G=C3=B3rny --=-LJqFKA0UN+VfKYXemNSB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- iQFGBAABCgAwFiEEx2qEUJQJjSjMiybFY5ra4jKeJA4FAmfe2FESHG1nb3JueUBn ZW50b28ub3JnAAoJEGOa2uIyniQOuVEH/0uMY1y9gk9mHSpEuH95ufz7X6jR16Qs faQ0FwLo3a9SLGI4BdZ8TJefTJU/0sUvzxBRKGJjBTe4ZGBR8KGDqHClK5Uu7xMK nnSfsSoLO/Rf7ISsm7V8fObAzQA4BK+o8DCKVdrNlipE1ao38tEqy+E2YP8b+SGO +iM20ZhvBFzdbLHI4Kl/EDK9aif1lgP4QZgup1WTnpoBJdngohzzslv7+2i5R248 0nijRfqCbbis0/ctL8HDP3xCP3WcONB7NYRNWFo4tVC///4NsGg/FCzWbjgIzoL5 G0gf7jwDf4tOx7UwSK9uSXDpK3zcRLtrNm1BOCCU1Zn/4i/9kmjdAso= =dSE3 -----END PGP SIGNATURE----- --=-LJqFKA0UN+VfKYXemNSB--