-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't update because of issue with vim-enhanced #115
Comments
This reminds me coreos/rpm-ostree#2231 that was supposed to be addressed in https://github.com/ostreedev/ostree/releases/tag/v2020.7 (that's already part of Silverblue 33). Any idea @cgwalters ? |
I actually tried to run the upgrade on my machine and I can reproduce it as well. |
I can confirm that this is also happening on my second machine running Silverblue. Layered packages are identical. |
I have the exact same issue. |
I am victim to this as well. I had to uninstall vim-enhanced to allow the update to complete without erroring. Which it did complete, but now I get the same error when I try to re-install vim-enhanced, so no joy here. |
What I do not understand: why is vim not part of the base image? Is it not one of the two main text editors on Linux (Vim and Emacs)? I know it's not part of the normal Fedora workstation either but again, in my opinion it should be. |
Vi still works, so the vim-core which is part of the base installation of SB is still working. |
As both packages now both ship the same files, rpm-ostree will not allow them to be installed at the same time (nor DNF would). In this case, you need to replace |
Can you try:
|
trying it now, it seems to be working, I'll let you know how the reboot works. |
If you are upgrading: remove vim-enhanced, upgrade, re-add vim-enhanced as described above. |
It works as described by @travier, |
@travier Your solution is working. Just one question, do you need |
You probably don't need it in the common case (admin user logged on an active seat / graphical session). |
The solution by @travier:
is a good workaround as long as you don't need something that depends on
Either
Well, why vim-minimal & vim-enhanced did not conflict up to 8.2.2115-2 then? |
This is indeed strange as I have both |
This is probably another instance of https://src.fedoraproject.org/rpms/nfs-utils/pull-request/9#comment-59201. (I.e. no relationship between vim-enhanced and vim-minimal means you can install mismatched versions of both. And since they would both try to install a separate version of |
Reproduced this in my pet container:
|
Ah! The versions of
but it will blow up once $ rpm-ostree status State: idle AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot Deployments: ostree://fedora:fedora/33/x86_64/silverblue Version: 33.20201210.0 (2020-12-10T00:51:13Z) BaseCommit: fd39645fcf9da4279bd89bb9c8c5b020d31bc94bcbcb76bd33efa2795e1defe3 GPGSignature: Valid signature by 963A2BEB02009608FE67EA4249FD77499570FF31 Diff: 2 downgraded, 1 added LayeredPackages: ansible fprintd fprintd-pam gnome-boxes gnome-tweak-tool gstreamer1-plugins-ugly-free ipa-client krb5-workstation libfprint libguestfs libvirt-client vim-enhanced-8.2.2072-1.fc33.x86_64 virt-viewer Isn't it a dependency resolution issue by |
I run the command 'rpm-ostree override remove vim-minimal --install vim-enhanced' and can confirm that it works! |
FWIW, dnf and rpm-ostree use the same dependency solver (libsolv) :). I think the easiest fix for this is to make Another way is to do something like this in
For now, as noted above, as long as you make sure that you're pulling in the same version of both, it should be fine (which should be the case if you're upgrading to the latest versions available and not pinning to a specific NEVRA of either). |
I was able to update without any workaround needed today. |
Hi,
I tried to update my machine today with
rpm-ostree update
and I`m getting this output:This is the output of
rpm-ostree status
:I noticed, that I have the vim layered, but when trying to uninstall it with
rpm-ostree uninstall vim
I'm getting similar output as onrpm-ostree update
:The text was updated successfully, but these errors were encountered: