Description of problem: fwupd-0.1.5-3.fc22.x86_64.rpm is missing a dependency on libfwup.so.0.4()(64bit) Version-Release number of selected component (if applicable): 0.1.5-3.fc22.x86_64 How reproducible: Every time Steps to Reproduce: 1. Attempt to install or update fwupd Actual results: error: Failed dependencies: libfwup.so.0.4()(64bit) is needed by fwupd-0.1.5-3.fc22.x86_64 Expected results: Success Additional info: libfwup.so.0.5 is installed by fwupdate-libs-0.5-3.fc22.x86_64
I don't see why dnf wouldn't pick this up automatically. Either way, I've not seen this on f23 or f24, but please re-open this if you still see it.
Dnf does pick it up automatically. See this output: [nobody@nowhere foobar]# dnf check-update Last metadata expiration check performed 0:07:10 ago on Fri Apr 1 09:07:39 2016. fwupd.x86_64 0.1.5-3.fc22 updates [nobody@nowhere foobar]# dnf update Last metadata expiration check performed 0:07:18 ago on Fri Apr 1 09:07:39 2016. Dependencies resolved. ==================================================================================================================================== Package Arch Version Repository Size ==================================================================================================================================== Skipping packages with broken dependencies: fwupd x86_64 0.1.5-3.fc22 updates 112 k Transaction Summary ==================================================================================================================================== Skip 1 Package Nothing to do. Complete! It may not exist in f23 or f24, but (I'm not trying to be sarcastic here) I filed the bug against f22, and as of this moment it still exists in f22. As far as I know f22 is still supported.
I think you need to move to f23 or f24 at this point, sorry.
I know that the reason I couldn't upgrade to F23 is not anyone at Fedora's concern, but, the reason I couldn't upgrade to F23 was that F23 broke vmWare. I know some people consider it blasphemy that I use proprietary software, but I haven't found an open source virtualization package that is as stable, and works as well as vmWare. Eventually a workaround was found, and I did upgrade. This bug doesn't effect me any more, but, I'm really not sure why this wasn't fixed. It didn't require any troubleshooting, or writing code, it was just a simple dependency issue that only required adjusting the spec file and repackaging.