Hi,
I have a similar problem (but on a much smaller scale): The certbot stack
comprises ~ a dozen packages which should be updated in lockstep. We push the
same version to all supported Fedora releases + EPEL (mostly).
To do that somewhat efficiently I built/extended some scripts:
https://github.com/FelixSchwarz/fedpkgscripts
Basically these handle issues like:
- merge a branch to N other branches
- push git changes in N branches
- build branch X for N packages (either in mock, in COPR or with koji)
- check for unpushed/uncommitted changes in a repo
- pull git changes for N packages
- set the new version in a spec file based on bugzilla queries, download the new
sources, verify with gpg and run "fedpkg new-sources" if verification is
successful
+ some other stuff I probably just did not remember
currently really a lot of "ad hoc" code but I'd be happy to contribute to a
common set of tools :-)
Felix
_______________________________________________
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
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
