Right, not pushing to all branches is in line with official guidelines: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#stable-releasesEspecially I don't like my packages being FTBFS due to other packagers pushing their updates everywhere. If there was at least included mass-prebuild step in the initial list to ensure there is no breakage in dependent packages.
Vít Dne 19. 06. 23 v 9:22 Richard W.M. Jones napsal(a):
On Sun, Jun 18, 2023 at 09:16:28AM +0000, Mattia Verga via devel 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. 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?So one alternative is *not* to push the change to all branches. Unless it's really necessary, such as fixing an essential bug, I tend to leave older Fedora branches on a stable release, to reduce churn for users. eg: $ cd fedora/libnbd $ for f in f* rawhide ; do (cd $f && fedpkg verrel); done Using libnbd.spec libnbd-1.0.2-1.fc29 Using libnbd.spec libnbd-1.2.2-1.fc30 Using libnbd.spec libnbd-1.4.1-1.fc31 Using libnbd.spec libnbd-1.6.2-1.fc32 Using libnbd.spec libnbd-1.6.5-1.fc33 Using libnbd.spec libnbd-1.8.6-1.fc34 Using libnbd.spec libnbd-1.10.5-1.fc35 Using libnbd.spec libnbd-1.12.7-1.fc36 Using libnbd.spec libnbd-1.14.2-1.fc37 Using libnbd.spec libnbd-1.16.1-1.fc38 Using libnbd.spec libnbd-1.16.1-2.fc39 (Also note 'fedpkg clone -B' option to use a separate subdirectory for each branch, much more intuitive IMHO.) Rich.
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature
_______________________________________________ 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
