Fedora Silverblue hardlink errors when running rpm-ostree update

Anyone have insight on what to do with an error like this?

I’ve run into this with two silverblue installs on two different machines now, different packages on each machine.

[user@localhost ~]$ sudo rpm-ostree update
⠒ Receiving objects: 99% (7005/7051) 1.6 MB/s 218.0 MB 
1336 metadata, 5715 content objects fetched; 213477 KiB transferred in 142 seconReceiving objects: 99% (7005/7051) 1.6 MB/s 218.0 MB... done
Checking out tree fd39645... done
Enabled rpm-md repositories: fedora-cisco-openh264 updates fedora updates-archive
rpm-md repo 'fedora-cisco-openh264' (cached); generated: 2020-08-25T19:10:34Z
Updating metadata for 'updates'... done
rpm-md repo 'updates'; generated: 2020-12-12T00:42:26Z
rpm-md repo 'fedora' (cached); generated: 2020-10-19T23:27:19Z
Updating metadata for 'updates-archive'... done
rpm-md repo 'updates-archive'; generated: 2020-12-12T01:32:57Z
Importing rpm-md... done
Resolving dependencies... done
Will download: 44 packages (33.2 MB)
Downloading from 'updates'... done
Importing packages... done
Checking out packages... done
error: Checkout vim-enhanced-2:8.2.2115-1.fc33.x86_64: Hardlinking ab/4a0895ca254af3b2723cd907c171e9eb41aad71ba821f90b68e4afe9cb9918.file to vim.sh: File exists
2 Likes

Sorry, no solution, but same problem here. What I did was:

rpm-ostree uninstall vim
rpm-ostree upgrade
systemctl reboot
rpm-ostree install vim

The upgrade worked after uninstallation, but the install-command after the reboot puts out the same error:

error: Checkout vim-enhanced-2:8.2.2115-1.fc33.x86_64: Hardlinking ab/4a0895ca254af3b2723cd907c171e9eb41aad71ba821f90b68e4afe9cb9918.file to vim.sh: File exists

Perhaps it’s just a matter of removing some file/hardlink manually? But which? – I’m not confident fiddling around in rpm-ostree managed filesystems. Any tips appreciated, vim is a rather essential tool for me.

__
s.

I have this same problem on a desktop and laptop. These things usually work themselves out within a day or two (I’ve never known it to be longer) when they’re caught and fixed. I find waiting for the correction worthwhile for the stability Silverblue gives. In the mean time @gidmoth, it may be worthwhile rolling back to a deployment that contains the previous version of Vim.

Ok, thx @hondje, would have done that, but I found another solution. At least as of Fedora Silverblue 33.20201210.0 vim seems to be part of the default install. Perhaps because I had vim installed before, or for some other reason, vim doesn’t appear as vim, but only as /bin/vi. After I symlinked this in my $PATH like so:

ln -s /bin/vi ~/.local/bin/vim

I have vim like before. Perhaps the addition to the default-Image broke the layered package install, but I’ not sure. This workaround works for me at least, and the /bin/vi is actually a fully-featured vim as far as I can tell.

__
s.

I solved this by uninstalling vim-minimal:

rpm-ostree override remove vim-minimal
rpm-ostree install vim-enhanced

Looks like as of today, this has been fixed. I was able to update without a problem and everything seems fine now thankfully.

Thanks to the people who fixed this!