• [gentoo-dev] [RFC] Exposing sync/* repositories better

    From =?UTF-8?Q?Micha=C5=82_G=C3=B3rny?=@21:1/5 to All on Sat Mar 22 12:50:01 2025
    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

    --
    Best regards,
    Michał Górny


    -----BEGIN PGP SIGNATURE-----

    iQFGBAABCgAwFiEEx2qEUJQJjSjMiybFY5ra4jKeJA4FAmfeodcSHG1nb3JueUBn ZW50b28ub3JnAAoJEGOa2uIyniQObAsH/1pn/4CcmLqH672HgKaCvY8TpBvkhrqB MozEXL2ttWZ3LlA3/ccLG7L08fyLcyUmpQntpGi2WOlmsS2ek31bed45/7Uf7sa0 xPAemp8rE7zaUouECe8wwk9lspW2XCKmOasMZnKgH7BTBISbChqRyR5lduUTy0wg gdwHaz/2oThv7mk2ZPnePdlA1mRgqtYaReUGPldQoUbGXMyy2qjHQob/9cDomeXn N9BxkFG7rmEvgRKLcqIyrKaD9lEVFDLycgh4+opbWnhYiNMB/Gnh7wMGIqlmwTbH 7Yny2+vzId3WNC6T3mhDTdiMfzTF72Fvw2UK5C5ZYLfqHdo2DRClUls=
    =X1Cq
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?q?Micha=C5=82=20G=C3=B3rny?@21:1/5 to All on Sat Mar 22 16:50:01 2025
    Add the "sync" sources for ::gentoo and ::guru repositories
    that provide the extra combined metadata and md5-cache. While arguably
    this is not the same thing, the list already includes rsync source
    which is actually closer to the "sync" repositories than the upstream repositories.
    ---
    files/overlays/repositories.xml | 13 +++++++++++++
    1 file changed, 13 insertions(+)

    diff --git a/files/overlays/repositories.xml b/files/overlays/repositories.xml index a338df5..ca1a2ca 100755
    --- a/files/overlays/repositories.xml
    +++ b/files/overlays/repositories.xml
    @@ -1686,6 +1686,13 @@
    <email>bug-wranglers@gentoo.org</email>
    </owner>
    <source type="rsync">rsync://rsync.gentoo.org/gentoo-portage</source>
    + <!-- repositories with extra metadata and md5-cache -->
    + <source type="git">https://github.com/gentoo-mirror/gentoo.git</source>
    + <source type="git">git+ssh://github.com/gentoo-mirror/gentoo.git</source> + <source type="git">https://anongit.gentoo.org/git/repo/sync/gentoo.git</source>
    + <source type="git">git://anongit.gentoo.org/repo/sync/gentoo.git</source> + <source type="git">git+ssh://git@git.gentoo.org/repo/sync/gentoo.git</source>
    + <!-- bare repositories -->
    <source type="git">https://anongit.gentoo.org/git/repo/gentoo.git</so