On 22. 04. 20 10:25, Susi Lehtola wrote:
Hello,
first, I'm sorry for a partial screw-up of the libxc soname bump announcement.
It appears I am not alone: there are a few soname bumps each month, many of them
still unannounced.
I'd guess the biggest problem is that a lot of packages have soname bumps hidden
by * globs. I.e. the maintainers update thei package without even realizing
they've bumped.
This is getting better and better now, as more packages follow the rule not to
do this and use a more strict glob.
This raises the question: shouldn't there be some sort of automatic tool for
making soname bump announcements? It seems to me that this is a thing where
computers easily beat humans: query for dependent packages, and shoot their
maintainers an email. Maybe something that could go in fedpkg? Whenever changed
sonames are detected, hold the update aside and start ringing the alarm bells?
If somebody does this, note that there are basically 3 steps here:
1.
$ repoquery --repo=rawhide --source --whatrequires 'libfoo.so.1.0()(64bit)'
2.
https://pagure.io/fedora-misc-package-utilities/blob/master/f/find-package-maintainers
3.
Write and send e-mail.
However, do you propose that this would happen automagically when the soname is
bumped? What if I am already in touch with the dependent package owners?
IMHO better automation would be to gate stuff at reverse rpmdeplint:
https://pagure.io/fedora-ci/general/issue/46
There are 2 problems with that:
- such check in the CI does not exist yet
- gating is still opt-in
See also:
https://pagure.io/fesco/issue/2343
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
