Learn more about these different git repos.
Other Git URLs
These days, when the PR workflow is more and more prevalent, it is sad that fedpkg insist on specifying --release, where custom branch is used. IOW this is pain point:
fedpkg
--release
$ git checkout -b ror8 $ fedpkg srpm Parsing specfile for used sources failed: Could not find release from branch name 'ror8'. Please specify with --release. ... snip ...
I think fedpkg could do better and there are two scenarios I can think of:
rawhide
For building srpm, it matters a little what the --release is. For other task such as fedpkg scratch-build --srpm, it matter a bit more, but it would be still good default. In the worst, case confirmation such as:
srpm
fedpkg scratch-build --srpm
$ fedpkg scratch-build --srpm Parsing specfile for used sources failed: Could not find release from branch name 'ror8'. Defaulting to 'rawhide': [Y/n]
Would still be better possibility IMHO.
git log
It should be possible to derive the branch from git log. I understand it won't be 100% correct, but it should be good enough. For example, this is my current case:
$ git log --oneline 22db815 (HEAD -> ror8) Update to Action Text 8.0.1. e8010d3 (origin/rawhide, origin/main, origin/f42, origin/HEAD, rawhide) Rebuilt for https://fedoraproject.org/wiki/Fedora_42_Mass_Rebuild c66681a (origin/f41) Rebuilt for https://fedoraproject.org/wiki/Fedora_41_Mass_Rebuild 3c39215 (origin/f40) Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild 7b6800f Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild 7b5f19a (origin/f39) Update to actiontext 7.0.8 ... snip ...
There is high chance that the ror8 branch was created from rawhide.
ror8
This request was triggered by this question:
https://pagure.io/fedora-docs/package-maintainer-docs/issue/178
Log in to comment on this ticket.