Learn more about these different git repos.
Other Git URLs
The docs miss the important part on how to push a minorbump to an older release without having to bump pkgrel to all newer releases.
Example: I have foo-1.0.0-1.fc36 and foo-1.0.0-1.fc35 I want to bump the F35 package to foo-1.0.0-1.fc35.1 How can I do that? I can add the .1 after %autorelease, but after committing to the F35 branch I suppose I will have a pkgrel bump...
foo-1.0.0-1.fc36
foo-1.0.0-1.fc35
foo-1.0.0-1.fc35.1
.1
Sorry for responding this late.
This is a downside of the simplified "bump the release for each commit" algorithm which FESCO asked us to use rather than the (supposedly more sophisticated but also much more complicated and less robust) algorithm we started implementing in the prototype which should have done what you want without intervention of the package maintainer. However, we don't need minor bumps because there is no requirement for a clean E-V-R upgrades between Fedora releases anymore, i.e. the upgrade mechanisms essentially do something like dnf distro-sync which would in this case simply downgrade the package from -2.fc35 to -1.fc36.
dnf distro-sync
-2.fc35
-1.fc36
Metadata Update from @nphilipp: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
I've never heard of that. Is that documented anywhere? The Fedora Packaging Guidelines still says that a clean E-V-R upgrade is required between releases. See: https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/#_you_need_to_change_an_old_branch_without_rebuilding_the_others and https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/#_rawhide_is_allowed_to_lag_temporarily
Login to comment on this ticket.