Also in Bodhi the maintainer wrote: “Updated to the latest RC release: nfs-utils-2-8-6-rc3” but set wrong version number: Making sure you're not a bot!
You should run that as sudo dnf upgrade --refresh to ensure that you are receiving the most up to date version info.
According to this the info is correct.
$ sudo dnf list --available libnfsidmap nfs-utils --refresh
Updating and loading repositories:
Repositories loaded.
Available packages
libnfsidmap.i686 1:2.8.5-0.rc3.fc43 updates
libnfsidmap.x86_64 1:2.8.5-0.rc3.fc43 updates
nfs-utils.x86_64 1:2.8.5-0.rc3.fc43 updates
Be aware that the upstream versions may not match the released versions, and that versions on both bohdi and koji may not have passed the testing necessary before release. Updates do not happen the same instant that upstream releases new versions. The maintainers must process and package the new version and then it must undergo testing before release. This process and flow can often take 2 weeks or more.
You should run that as sudo dnf upgrade --refresh to ensure that you are receiving the most up to date version info.
This what I usually do. I didn’t add --refresh this time because I already have ran sudo dnf upgrade --refresh a few seconds before that.
According to this the info is correct.
The issue is not how DNF5 works but how the NFS related packages were updated and built. The maintainer updated the version of those NFS relate packages incorrectly. You can see that even in the Changelog at Koji:
* Sat Feb 28 2026 Steve Dickson <steved@redhat.com> 2.8.5-0.rc3)
- Updated to the latest RC release: nfs-utils-2-8-6-rc3
So, according to that the change was made on koji on Feb 28, Today is Mar 3. Only 3 days have passed, and it takes a minimum of 1 week and often as much as 2 weeks for updates to be released. The change to 2.8.6 is not even in the updates-testing repo yet. It also requires that all related packages have to be updated to be version synced as well.
Please practice a little patience and understanding of the flow of software (development, packaging, and testing) and you can be assured that when it has properly passed testing the updates will be available.
Again, the version of this and other NFS related packages was updated incorrectly by the maintainer. This is obvious, don’t you see it by yourself? Don’t you see that 5 != 6 ?
Don’t you see this text:
Updated to the latest RC release: nfs-utils-2-8-6-rc3
inside the Bodhi page of the nfs-utils-2.8.5-0.rc3.fc43 package? Don’t you see any inconsistency in the versions?
It doesn’t seem to be a typo, but probably a bug in some script the maintainer use. Evidence from the changelog:
* Sat Feb 28 2026 Steve Dickson <steved@redhat.com> 2.8.5-0.rc3)
- Updated to the latest RC release: nfs-utils-2-8-6-rc3
* Sat Jan 31 2026 Steve Dickson <steved@redhat.com> 2.8.4-2.rc3
- Updated to the latest RC release: nfs-utils-2-8-5-rc3
* Fri Jun 27 2025 Steve Dickson <steved@redhat.com> 2.8.3-2.rc3
- Updated to the latest RC release: nfs-utils-2-8-4-rc3
If you can, create a ticket in Bugzilla (https://bugzilla.redhat.com/) and file it under the right attributes (there’s a fedora project, then there’s all the packages).
There’s nothing to see here, it’s just a number. Business as usual.
* Sat Feb 14 2026 Steve Dickson <steved@redhat.com> 2.8.5-0
- Updated to latest upstream release: nfs-utils-2-8-5 (bz 2439968)
* Sat Jan 31 2026 Steve Dickson <steved@redhat.com> 2.8.4-2.rc3
- Updated to the latest RC release: nfs-utils-2-8-5-rc3
