Updated to the latest upstream RC release: libtirpc-1-3-4-rc2
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2023-ab6ed662ccPlease log in to add feedback.
This update has been submitted for testing by steved.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
Works.
Update description doesn't match version of shipped contents.
libtirpc-1.3.3.rc2 != libtirpc-1.3.4.rc2
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
Updated to the latest upstream RC release: libtirpc-1-3-4-rc2 mean I update to latest upstream RC (aka upstream tag)
The NVR is 1.3.3-1.rc2 increased from 1.3.3-1.rc1 which is fine
Works without issues till now
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
steved edited this update.
@besser82 are good with this??
Works
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
This update can be pushed to stable now if the maintainer wishes
This update has been submitted for stable by steved.
@steved the versioning is not in line with Fedora guidelines. If it's 1.3.4rc2 you're meant to version it as
1.3.4~rc2(these days, in the past it would have been version1.3.4, release0.1.rc2). See https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/ . This versioning is pretty confusing, I agree with @besser82.This update has been pushed to stable.
To make it a 1.3.4 I would have to make a new release... 1.3.4.rc3 means 1.3.4 is not released... aka the rc2...