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 27C8A1581EE for ; Sat, 22 Mar 2025 11:41:59 +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 19A42343271 for ; Sat, 22 Mar 2025 11:41:59 +0000 (UTC) Received: from bobolink.gentoo.org (localhost [127.0.0.1]) by bobolink.gentoo.org (Postfix) with ESMTP id B203F1104B4; Sat, 22 Mar 2025 11:41:16 +0000 (UTC) Received: from smtp.gentoo.org (mail.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 E3D181104AB for ; Sat, 22 Mar 2025 11:41:15 +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 211C43431F7; Sat, 22 Mar 2025 11:41:14 +0000 (UTC) Message-ID: <297ed0af9a4d70ebb27e55cf154b57a0e7e22af6.camel@gentoo.org> Subject: [gentoo-dev] [RFC] Exposing sync/* repositories better From: =?UTF-8?Q?Micha=C5=82_G=C3=B3rny?= To: gentoo-dev@lists.gentoo.org Date: Sat, 22 Mar 2025 12:41:11 +0100 Organization: Gentoo Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-/QGMQXk6EUAaRIRETkQV" 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: a548370c-945b-4f68-b623-fa7c7cfcec1c X-Archives-Hash: 1c61c424ff92c663568fc9b420f72fb7 --=-/QGMQXk6EUAaRIRETkQV Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, everyone. TL;DR: should we expose "syncing" mirrors directly in our base repositories.xml? Per my previously announcement, I'd like to wind down the "public" service of mirroring all Gentoo repositories, and limit it to the few repositories we have control over -- at least ::gentoo and ::guru. This makes me want to reconsider how we're publishing these mirrors right now. Just to clarify, we are talking about these mirrors: https://github.com/gentoo-mirror/gentoo https://gitweb.gentoo.org/repo/sync/gentoo.git and: https://github.com/gentoo-mirror/guru https://gitweb.gentoo.org/repo/sync/guru.git Currently, our primary repositories.xml file [1] lists only rsync and the "standard" git repository. The "mirror" repositories are overimposed on them in a separate repository [2]. eselect-repo defaults to using the latter. What I'm wondering about is whether we should add the aforementioned mirror repositories into the former repositories.xml, and sunset the latter. I think it would improve the consistency, given that the "mirror" repository has the same contents as rsync (unlike the "standard" repository) -- but I'm not sure if this won't break somebody's workflow. WDYT? [1] https://gitweb.gentoo.org/data/api.git/tree/files/overlays/repositories= .xml [2] https://qa-reports.gentoo.org/output/repos/repositories.xml --=20 Best regards, Micha=C5=82 G=C3=B3rny --=-/QGMQXk6EUAaRIRETkQV Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- iQFGBAABCgAwFiEEx2qEUJQJjSjMiybFY5ra4jKeJA4FAmfeodcSHG1nb3JueUBn ZW50b28ub3JnAAoJEGOa2uIyniQObAsH/1pn/4CcmLqH672HgKaCvY8TpBvkhrqB MozEXL2ttWZ3LlA3/ccLG7L08fyLcyUmpQntpGi2WOlmsS2ek31bed45/7Uf7sa0 xPAemp8rE7zaUouECe8wwk9lspW2XCKmOasMZnKgH7BTBISbChqRyR5lduUTy0wg gdwHaz/2oThv7mk2ZPnePdlA1mRgqtYaReUGPldQoUbGXMyy2qjHQob/9cDomeXn N9BxkFG7rmEvgRKLcqIyrKaD9lEVFDLycgh4+opbWnhYiNMB/Gnh7wMGIqlmwTbH 7Yny2+vzId3WNC6T3mhDTdiMfzTF72Fvw2UK5C5ZYLfqHdo2DRClUls= =X1Cq -----END PGP SIGNATURE----- --=-/QGMQXk6EUAaRIRETkQV--