On 26. 06. 19 13:34, Martin Kolman wrote:
On Tue, 2019-06-25 at 16:30 -0500, mcatanzaro@xxxxxxxxx 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.
https://pagure.io/fedora-ci/general/issue/45
https://pagure.io/fedora-ci/general/issue/46
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/devel@xxxxxxxxxxxxxxxxxxxxxxx
