The trouble with this is that another packager might be unresponsive or be unable to fix or simple refuses to fix their package (eg. because of your SONAME update) and now you can't release that to anyone in a stable branch. Even if your package is more core than the other person's blocking package.
On Mon, Jul 06, 2026 at 10:05:11PM +0100, Adam Williamson wrote: > Gating all updates for stable releases on it would mean you could no > longer ship updates with detectable dependency issues, unless you waive > the failure - which implies explicitly taking responsibility for > shipping a broken package, or breaking another package. Sure, but why take responsibility for someone else's problem! Having said that I'm not really opposed to this, but I think waiving it shouldn't come with some implication that it's your problem, when it may be another packager's problem. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com nbdkit - Flexible, fast NBD server with plugins https://gitlab.com/nbdkit/nbdkit -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
