On Sun, Jun 18, 2023 at 5:17 AM Mattia Verga via devel <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > For the 99% of packages I maintain I usually perform the same workflow > when updating them: > > 1. Update spec and source in Rawhide > 2. commit and push > 3. fedpkg build > 4. fedpkg switch-branch f* > 5. git merge rawhide > 6. push and fedpkg build > > And repeat 4-5-6 for every f*/epel* branches where I want to push the > update. > With fbrnch, you can run `fbrnch parallel --all-fedora`, which will do steps 2.5 (i.e., the push part) through 6 for all Fedora branches (in parallel), and wait for all builds to finish, then produce updates for all of them except rawhide. > This is quite boring and time wasting... is there a more efficient way > to use my packaging time? Do you think fedpkg can be enhanced to have a > single command which makes 4-5-6 to all specified branches? > > Mattia > _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
