Alex Lancaster <alexl <at> users.sourceforge.net> writes:
> Can this be fixed as well? Also, you might consider chain-build in
> rawhide to rebuild a series of packages against each other so that the
> rawhide push passes repoclosure and doesn't have any broken deps, even
> transiently. Otherwise you could also ask rel-eng for a buildroot
> override.
Buildroot overrides are not useful for Rawhide. They're what is used to build
chains of dependent packages in releases. (You can't just chain-build them
because updates-candidate doesn't populate the buildroots.)
Basically, chain-building works if and only if sequential building (with enough
waiting for the buildroot's "newRepo" task to complete) works without needing
manual tagging. So you can chain-build in Rawhide, you have to request manual
tagging and wait for rel-eng to act on it and then for the automatic newRepo to
happen in releases.
Kevin Kofler
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
