On Wed, Apr 22, 2020 at 3:26 AM Susi Lehtola <jussilehtola@xxxxxxxxxxxxxxxxx> wrote:
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?
This is far from automatic but this is my workflow (now with the availability of side tags):
1. Update the spec file
2. Perform a local mock build for rawhide (fedpkg mockbuild)
3. rm -f the debugsource packages because abppkgdiff has not been updated to deal with the fact we have both debuginfo and debugsource packages generated now.
4. Run fedabipkgdiff --dso-only --from fc33 /path/to/results/build
5. Nothing scary in the output (or zero diff)? fedpkg build (and sleep easy) -> DONE
ELSE:
6. "$ dnf repoquery --repo=rawhide --provides <pkgname>" skim through the results for the important bits and then:
$ dnf repoquery --repo=rawhide --source --whatrequires "<important bits>"
7. Create a side-tag
8. Make sure all dependencies rebuild
9. Submit side-tag update in Bodhi.
Automating 6 & 7 would be very helpful.
Thanks,
Richard
_______________________________________________ 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
