On Saturday 02 June 2007 10:21:03 Denis Leroy wrote: > how should we tackle this in the future ? > > 1) go towards an automated rebuild system, where the firefox maintainer > can ask for automated rebuilds of the handful of packages that depend on it > > 2) instead, notify (automatically) the maintainers of the affected > packages as soon as a firefox successful build appears in koji, but > otherwise don't slow down the firefox release I think it depends on the nature of the update and the flaw. Koji does have dep information in the database. What is missing is a utility to run once a new package is tagged to check if the build it is replacing is specifically needed by anything and thus there are broken deps. Theoretically the maintainer for those other packages and the maintainer that did the build could be notified via email that the dep problem exists so that they can work out a solution. Patches anybody? -- Jesse Keating Release Engineer: Fedora
Attachment:
pgpu2UnSHGWuv.pgp
Description: PGP signature
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
