On Tue, Jul 30, 2019 at 04:15:31PM +0200, Florian Weimer wrote: > * Pierre-Yves Chibon: > > > What does it mean for us as packagers? > > -------------------------------------- > > > > When you run `fedpkg build` on Rawhide, your package will be built in > > a new koji tag (which will be the default target for Rawhide). The > > package will be picked up from this koji tag, signed and moved onto a > > second tag. Bodhi will be notified by koji once this new build is > > signed and will automatically create an update for it (you will be > > notified about this by email by bodhi directly) with a “Testing” > > status. If the package maintainer has not opted in into the CI > > workflow, the update will be pushed to “Stable” and the build will be > > pushed into the regular Rawhide tag, making it available in the > > Rawhide buildroot, just as it is today. > > What are the actual tag names? I have a glibc build which appears to be > stuck in f31-updates-candidate: > > <https://koji.fedoraproject.org/koji/buildinfo?buildID=1344222> > > I wonder if this is caused by gating, or if it's something else. It's robosignatory acting up again :( I think this may be related to the mass-rebuild being merged, cf Kevin's comment in: https://pagure.io/fedora-infrastructure/issue/8041#comment-585310 To answer your question: - builds land in f31-updates-candidate - robosignatory signs them and moves them to f31-updates-testing - bodhi picks them up from there - once CI passes, bodhi moves them to f31 Best, Pierre _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
