On 03/09/2021 14:56, Fabian Arrotin wrote: > Hi, > > Long awaited feature request is now implemented on > https://cbs.centos.org : you can now start requesting 9s tags to build > against/for CentOS Stream 9 ! > > I already created some tags/targets for SIGs that already requested it > some time ago through our dedicated infra tracker (reminder: > https://pagure.io/centos-infra/issues) > > Worth knowing that the following repositories are enabled by default for > all newly created 9s tags: > - BaseOS > - AppStream > - CRB > > What's possible to add ? I know that for 8/8s some SIGs (like Cloud SIG > for openstack) rely on other repositories, like HighAvailability , or > others. > Feel free to ask such repositories to be added to your build tags. > > It's also possible to build against CentOS Stream 9 buildroots if the > pushed repositories don't include all -devel / runtime packages that you > need at buildtime. > For that, consider also asking for it if/when needed. > > Important ! > Due to the way Stream 9 will be delivered (more news on that later, > probably through Brian and/or Carl), I have locked all -release tags for 9s. > > What does that mean ? > That you can build pkgs, and also tag to -testing (that will go out as > usual to buildlogs.centos.org) but not to -release (even if tag is > created already). > > Once we'll have figured out how to properly sign+push SIG content out, > we'll announce the plan and also unlock the -release SIG tags > > Stay tuned for more information about that soon. > Hey SIG members ! Just to let you know that mirrormanager is in place so we have unlocked the -release tags for stream 9, so if you tag to -release, that would push your repo content to http://mirror.stream.centos.org/SIGs/9-stream/ We'll do a follow-up next week about the centos-release-* packages , moving to their own new repo/sig so that it would be built and pushed directly from cbs, but that needs a modification first in stream 9 distro content itself (basically the .repo and the dedicated gpg public key that will be used to sign these release pkgs) Once you'll have content available, mirrormanager should be able (normally but we can then ask Adrian Reber to investigate that) to detect new repositories/repodata under /SIGs/9-stream and so start producing valid metalink for these repositories. Based on information I got from Adrian, the logic/pattern to use to call for metalink would be : repo=centos-<sig-name>-sig-<project>-<release>-9-stream&arch=<basearch> So if we have a look at infra sig, using infra9s-infra-common-release as cbs/koji tag, it's this path on mirror.stream.centos.org: http://mirror.stream.centos.org/SIGs/9-stream/infra/x86_64/infra-common/ and metalink being : curl 'https://mirrors.centos.org/metalink?repo=centos-infra-sig-infra-common-9-stream&arch=x86_64' variant for source and debug repo=centos-infra-sig-infra-common-debug-9-stream&arch=x86_64 repo=centos-infra-sig-infra-common-source-9-stream&arch=source Once we'll have more content we'll be able to validate that but main announce here is that all -release tags for stream 9 are now unlocked -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20211124/7aecac1e/attachment-0002.sig>