On 19-06-2023 11:04, Miroslav Suchý wrote:
Dne 18. 06. 23 v 11:16 Mattia Verga via devel napsal(a):
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 know several ways:
1) Tito
https://github.com/rpm-software-management/tito
This requires upstream modification. Namely .tito/releasers.conf
https://github.com/rpm-software-management/tito/blob/master/.tito/releasers.conf
Then you can (e.g. in the Tito git repo itself) run:
tito release fedora
or
tito release copr
and it will build the package in Fedora's Koji for all configured
versions. Or in Copr. As you configure it.
2) Even better is Packit
https://packit.dev/
You have many ways to use it. My favorite way is to use
pull-from-upstream
https://packit.dev/posts/pull-from-upstream/
You just make sure you have record in https://release-monitoring.org/
and then put .packit.yaml in Fedora's dist-git. And when upstream has a
new release you will receive a pull request to src.fedoraproject.org for
all configure branches. And when it merges it (can) build in Koji and
submit Bodhi update for you.
With Packit you can use full automation or only some steps. And
combine it as you like it. If you do not like triggereing by release
monitoring, you can initiate it from command line. It is up to you.
Sounds like these tools are worth mentioning in the docs, seeing how
many people face the same challenge.
-- Sandro
_______________________________________________
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
