On Tue, 2019-06-25 at 16:30 -0500, [email protected] wrote: > Let's ensure this at least doesn't happen for the same library again > and again. > > In [1], change SHOULD NOT -> MUST NOT. > > Require maintainers (or provenpackagers) to fix violations like [2] > when unannounced soname bumps occur. > > (If anyone wants to write a script to detect such problems proactively, > even better.) Couldn't some of the upcoming gating initiatives catch incidental soname bumps ?
I can imagine a test running on all builds, that checks for soname bump and gates the package if the soname bump is not appropriately marked up somewhere (say via some identifier in the package change log). Alternatively I guess reverse dependency tests could catch this, if systemd gating tests run & failed with the updated qrencode package, keeping the qrencode package gated. > > If we don't fix [2] the problem will just occur again. > > [1] > https://docs.fedoraproject.org/en-US/packaging-guidelines/#_listing_shared_library_files > [2] > https://src.fedoraproject.org/rpms/qrencode/blob/f48205000af5397008dbd645abb941e0dbb49636/f/qrencode.spec#_63 > > _______________________________________________ > 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] _______________________________________________ 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]
