Using `dnf` to compare filesystem contents with repositories

asked 2018-07-21 21:16:50 -0600

193 ●1 ●12 ●15

Following a trail of one bug, I've discovered that my bsdtar utility is 0 length.

# ls -l `which bsdtar`
-rwxr-xr-x. 1 root root 0 Feb  3 19:47 /usr/bin/bsdtar

Perhaps long ago a mistake in pipe command that was run under sudo, overwrote it. Or maybe filesystem failure.

With dnf provides I can figure out that the package name is bsdtar and reinstall it, but I'd like to check if files in other installed packages became corrupted too. Is it possible to do this with dnf?

edit retag flag offensive close merge delete

add a comment

3

answered 2018-07-24 06:12:01 -0600

Aeyoun

1390 ●12 ●34 ●55 https://daniel.priv.no/

updated 2018-07-24 06:16:52 -0600

Fixing the problem

You can identify the package with the following command:

dnf provides /usr/bin/bsdtar

…and reinstall said package with this command:

dnf reinstall bsdtar

Comparing a file to a known-good copy in a repo

cd /tmp
dnf download bsdtar
rpm2cpio bsdtar*.rpm | cpio -idmv
diff /usr/bin/bsdtar /tmp/usr/bin/bsdtar

edit flag offensive delete link

Comments

That fixes the problem, but only with one package. Thanks for the diff part, though. I think I can do what I want with combined - rpm -Va, this command, and a little bit of scripting.