When I ran check-update today, there were a few new packages, but one throw an err I haven’t seen before.
$ sdnf chup
Last metadata expiration check: 0:31:59 ago on tor 6 apr 2023 13:38:34.
NetworkManager-libnm-devel.x86_64 1:1.40.0-6.el8_7 powertools
EC: 100
$ sdnf yup
Last metadata expiration check: 0:32:08 ago on tor 6 apr 2023 13:38:34.
Error:
Problem: cannot install the best update candidate for package NetworkManager-libnm-devel-1:1.40.0-5.el8_7.x86_64
- nothing provides NetworkManager-libnm(x86-64) = 1:1.40.0-6.el8_7 needed by NetworkManager-libnm-devel-1:1.40.0-6.el8_7.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
EC: 1
Before starting to troubleshoot it…It seems there was an update, but they forgot to push the main package, right? Or why would you only update the header/devel files? Anyone else who got the same msg?
· Eric
# dnf repoquery -q NetworkManager-libnm-devel NetworkManager-libnm --latest=1
NetworkManager-libnm-1:1.40.0-6.el8_7.i686
NetworkManager-libnm-1:1.40.0-6.el8_7.x86_64
NetworkManager-libnm-devel-1:1.40.0-6.el8_7.i686
NetworkManager-libnm-devel-1:1.40.0-6.el8_7.x86_64
This is what’s available. We do not manually pick and choose the packages that are distributed and there are no issues with the repositories. A mirror may have not fully synced.
Thanks! Yes, I guess that can take some time. But, it looks like all the pieces are there - just not working.
$ sdnf chup
Last metadata expiration check: 0:16:00 ago on fre 7 apr 2023 00:42:50.
NetworkManager-libnm-devel.x86_64 1:1.40.0-6.el8_7 powertools
EC: 100
$ dnf repoquery -q NetworkManager-libnm-devel NetworkManager-libnm --latest=1
NetworkManager-libnm-1:1.40.0-6.el8_7.i686
NetworkManager-libnm-1:1.40.0-6.el8_7.x86_64
NetworkManager-libnm-devel-1:1.40.0-6.el8_7.i686
NetworkManager-libnm-devel-1:1.40.0-6.el8_7.x86_64
$ dnf ls available NetworkManager-libnm*
Last metadata expiration check: 0:09:14 ago on fre 7 apr 2023 00:50:01.
Available Packages
NetworkManager-libnm.i686 1:1.40.0-6.el8_7 baseos
NetworkManager-libnm.x86_64 1:1.40.0-6.el8_7 baseos
NetworkManager-libnm-devel.i686 1:1.40.0-6.el8_7 powertools
NetworkManager-libnm-devel.x86_64 1:1.40.0-6.el8_7 powertools
$ dnf ls installed NetworkManager-libnm*
Installed Packages
NetworkManager-libnm.x86_64 1:1.40.0-5.el8_7 @baseos
NetworkManager-libnm-devel.x86_64 1:1.40.0-5.el8_7 @powertools
$ sdnf up
Last metadata expiration check: 0:17:21 ago on fre 7 apr 2023 00:42:50.
Error:
Problem: cannot install the best update candidate for package NetworkManager-libnm-devel-1:1.40.0-5.el8_7.x86_64
- nothing provides NetworkManager-libnm(x86-64) = 1:1.40.0-6.el8_7 needed by NetworkManager-libnm-devel-1:1.40.0-6.el8_7.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
EC: 1
So, with both installed, and both updates show up as available - but only the -devel pkg showed up as outdated? Shouldn’t NetworkManager-libnm show up in check-update as well?
Looks like something happened now…
Got a load of NetworkManager pkgs now. 
$ sdnf chup | grep Network*
NetworkManager.x86_64 1:1.40.0-6.el8_7 baseos
NetworkManager-adsl.x86_64 1:1.40.0-6.el8_7 baseos
NetworkManager-bluetooth.x86_64 1:1.40.0-6.el8_7 baseos
NetworkManager-libnm.x86_64 1:1.40.0-6.el8_7 baseos
NetworkManager-libnm-devel.x86_64 1:1.40.0-6.el8_7 powertools
NetworkManager-team.x86_64 1:1.40.0-6.el8_7 baseos
NetworkManager-tui.x86_64 1:1.40.0-6.el8_7 baseos
NetworkManager-wifi.x86_64 1:1.40.0-6.el8_7 baseos
NetworkManager-wwan.x86_64 1:1.40.0-6.el8_7 baseos
Guess I’m good to go now.
// It’ll have to wait to after the hockey game, of course. 