Re: Releasing package updates in multiple Fedora releases

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@xxxxxxxxxxxxx
https://www.happyassassin.net



_______________________________________________
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux