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 00C681581EE for ; Tue, 25 Mar 2025 20:52:12 +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 DC56C343498 for ; Tue, 25 Mar 2025 20:52:12 +0000 (UTC) Received: from bobolink.gentoo.org (localhost [127.0.0.1]) by bobolink.gentoo.org (Postfix) with ESMTP id 57A261104B5; Tue, 25 Mar 2025 20:51:26 +0000 (UTC) Received: from smtp.gentoo.org (dev.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) server-digest SHA256) (No client certificate requested) by bobolink.gentoo.org (Postfix) with ESMTPS id A3711110296 for ; Tue, 25 Mar 2025 20:51:25 +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 CB47E34319E; Tue, 25 Mar 2025 20:51:24 +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: Tue, 25 Mar 2025 21:51:21 +0100 In-Reply-To: References: <6b358608f6e244cb96ce527ad47b3e0483eaf0c6.camel@gentoo.org> Organization: Gentoo Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-gJQSwh+lpvP31oSrDCwY" 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: e4856845-8695-4fdc-a6c5-1e46c59f03a8 X-Archives-Hash: 45b09060de4ab3313ffb87c04ec1652c --=-gJQSwh+lpvP31oSrDCwY Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, 2025-03-24 at 08:46 -0400, Mitchell Dorrell wrote: > I've been following the discussion, but I still don't know enough to have > an opinion. Why was this infrastructure created in the first place? There's a number of reasons, and they are still valid today: 1. Syncing against a mirror with metadata cache makes package managers faster, and some simpler tools more functional. However, this only works as long as the mirror is updated -- when things break and we disable one, people end up with outdated repository. 2. We check repositories for major issues, such as ebuilds failing because of old EAPI or removed eclass. However, we don't have time to file bugs and deal with the feedback. 3. Having a single place with all the repositories make it possible to do some cross-repository searches and analysis easier. For example, we can estimate how many ebuilds from third-party repositories are still using a particular eclass. 4. In the end, mirroring repositories mean there's a copy if the original repository is removed. The way we merge things, we also preserve the history when upstream repository is force-pushed. The flip side is that if the repository owner tries to remove some data from history, we normally preserve it. 5. We provide git mirrors with history for repositories that use non- history-preserving protocols like rsync. --=20 Best regards, Micha=C5=82 G=C3=B3rny --=-gJQSwh+lpvP31oSrDCwY Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- iQFGBAABCgAwFiEEx2qEUJQJjSjMiybFY5ra4jKeJA4FAmfjF0kSHG1nb3JueUBn ZW50b28ub3JnAAoJEGOa2uIyniQOqLUH/iwLTd0V6gC4k1B4MNx5qqcT7lj5BJt/ wcgNJu6CeWoevu6VqwW1AMmh22i+tsZoT7Cz47BFZ8OxWqgtXCrBLBcPRcfFtMei XnIYAovLkTzEuF7R/HSP2jNOgD31mI5NkELy97/WYkTJdKlf+EchNUeYadO2/uv+ /MyI7c/78RHsXMOBln558QODxBMpuoXGG2NPQILWAdv1g9blk/9Zc6ZUDnOy/xFG eNFYZOr/QBiBTfO7Qwp4fTyYyeDfFoH1G8XwE+tnDSVrkg/WHLbCk+Z9a3PjofAo +xKbG6FGG6whxlf24t9PjiZ7MP4GEPRWR34pGFqrgMoJuPv8HJejW5Q= =9b3d -----END PGP SIGNATURE----- --=-gJQSwh+lpvP31oSrDCwY--