I get this error updating nut in F26: # dnf upgrade nut nut-client Last metadata expiration check: 0:00:00 ago on Mon Oct 2 15:11:47 2017. Dependencies resolved. Problem: cannot install the best update candidate for package nut-2.7.4-7.fc26.x86_64 - nothing provides libipmimonitoring.so.6()(64bit) needed by nut-2.7.4-14.fc26.x86_64 =================================================================================================================================================================================================================== Package Arch Version Repository Size =================================================================================================================================================================================================================== Upgrading: nut-client x86_64 2.7.4-14.fc26 updates 212 k Skipping packages with broken dependencies: nut x86_64 2.7.4-14.fc26 updates 1.8 M Transaction Summary =================================================================================================================================================================================================================== Upgrade 1 Package Skip 1 Package Total size: 212 k Is this ok [y/N]: y Downloading Packages: [SKIPPED] nut-client-2.7.4-14.fc26.x86_64.rpm: Already downloaded Running transaction check Transaction check succeeded. Running transaction test The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Error: Transaction check error: file /usr/sbin/upsmon from install of nut-client-2.7.4-14.fc26.x86_64 conflicts with file from package nut-2.7.4-7.fc26.x86_64 file /usr/sbin/upssched from install of nut-client-2.7.4-14.fc26.x86_64 conflicts with file from package nut-2.7.4-7.fc26.x86_64 Error Summary -------------
It looks like some packages may be out of sync. As a workaround, you can update nut from the updates-testing repo: `dnf update --enablerepo updates-testing nut`
Ok, that have worked. Thanks.
Seems to be resolved now...