Chain builds for non-rawhide

Jesse Keating jkeating at redhat.com
Tue Oct 12 23:09:49 UTC 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/7/10 11:59 PM, Thomas Spura wrote:
> How about let bodhi do the tagging?
> When there is an update, you could click on "tag this package", and
> bodhi will do the rest. If the update is deleted or obsoleted by
> another one, the tag will be deleted again.
> 
> This doesn't solve the problem, that maintainers could tag a package
> and never push the update out, but that could happen with manual
> tagging too, isn't it?

We've (as in releng and some members of fesco) have discussed something
like this in the past.  We've wanted some functionality out of bodhi to
track things like buildroot contents used for packages, and if an update
is requested to go live it would block on whether or not a buildroot
component also has gone live or is requested to go live.  Until we get
some sort of automation on prevention of this, we won't likely be
automating or making it easier to do buildroot overrides.

- -- 
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAky06r0ACgkQ4v2HLvE71NU9VQCfV9FoOrbsNOiZbu00AibJUtd7
3NkAoIA9DDV1AY9pwAFXEjTbuxCAI8yB
=DW7X
-----END PGP SIGNATURE-----


More information about the devel mailing list