On 6/18/23 04:28, Adam Williamson wrote:
On Sun, 2023-06-18 at 09:16 +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?I have this in my command history: for i in f37 f38 rawhide; do fedpkg switch-branch $i; git pull; git merge rawhide; fedpkg push; fedpkg build --nowait; done
Similar: In my .bashrc:fpbr() { for rel in $*; do fedpkg switch-branch $rel; git merge rawhide && git push && fedpkg build --nowait; done; }
You're addition of git pull is a good thing. -- Orion Poplawski he/him/his - surely the least important thing about me IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
