Nit-pick: With some unrelated changes in fedora 31 and 30, builds from this fedora 32 update now have a lower NVR than the builds from fedora 31 or 30.
When doing such "unrelated fixes" in older branches, it's recommended to append .1 to the Release (like 1%{?dist}.1, and then incrementing that postfix number) instead of incrementing the Release like normal. This preserves a correct upgrade path within and across releases.
Well, it's mostly true that "upgrade path" doesn't matter anymore (you're right that dist-upgrades do distro-sync - and downgrade - now by default).
In this case, this turned out to not be a problem, but in other cases, I found updates that were missing from f32 entirely (which is a problem, since package downgrades aren't exactly supported, and it's not good for f32 to be missing bugfixes and security updates).
This update has been submitted for testing by catanzaro.
catanzaro edited this update.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
Nit-pick: With some unrelated changes in fedora 31 and 30, builds from this fedora 32 update now have a lower NVR than the builds from fedora 31 or 30.
When doing such "unrelated fixes" in older branches, it's recommended to append
.1
to the Release (like1%{?dist}.1
, and then incrementing that postfix number) instead of incrementing the Release like normal. This preserves a correct upgrade path within and across releases.Hm, I thought we didn't care about upgrade path anymore because dist-upgrade downgrades everything automatically... is that wrong?
I can remember to do this in the future, though.
I have another change to make anyway, so I'll call it -7 to fix the upgrade path.
Well, it's mostly true that "upgrade path" doesn't matter anymore (you're right that dist-upgrades do distro-sync - and downgrade - now by default).
In this case, this turned out to not be a problem, but in other cases, I found updates that were missing from f32 entirely (which is a problem, since package downgrades aren't exactly supported, and it's not good for f32 to be missing bugfixes and security updates).
But thanks for fixing it anyway :)
This update has been obsoleted by webkit2gtk3-2.28.0-7.fc32.