Ian Pilcher wrote:

From the what the actual ... department:

$ sudo dnf install libsavl-0.0-0.fc35.x86_64.rpm Last metadata expiration check: 2:44:13 ago on Tue 01 Feb 2022 10:04:49 AM CST. Error: Problem: conflicting requests - nothing provides /usr/sbin/ldconfig needed by libsavl-0.0-0.fc35.x86_64 (try to add '--skip-broken' to skip uninstallable packages)

$ rpm -q --whatprovides /usr/sbin/ldconfig glibc-2.34-11.fc35.x86_64

$ sudo rpm -ihv libsavl-0.0-0.fc35.x86_64.rpm Verifying... ################################# [100%] Preparing... ################################# [100%] Updating / installing... 1:libsavl-0.0-0.fc35 ################################# [100%]

Anyone have any idea what the heck is going on?

I'm guessing libsavl-0.0-0.fc35.x86_64.rpm is a locally built package?

I think the issue is that glibc doesn't really provide /usr/sbin/ldconfig. It installs the file as /sbin/ldconfig.

I haven't looked, but I'm guessing that `rpm -q --whatprovides` is looking at the file and then finding that /sbin/ldconfig is the same as /usr/sbin/ldconfig.

If you check the provides of glibc, you get:

$ rpm -q glibc glibc-2.34-8.fc35.x86_64

$ rpm -q --provides glibc | grep ldconfig ldconfig

Compare `dnf provides /sbin/ldconfig` and `dnf provides /usr/sbin/ldconfig` as well as `dnf repoquery --whatrequires /sbin/ldconfig` and `dnf repoquery --whatrequires /usr/sbin/ldconfig`.

You should be able to adjust the Requires in the libsavl pacakge to fix that. Whether there are bugs worth chasing and fixing in the rpm and dnf handling here, I don't know.