Problema: 1: clang-tools-19.1.7-bp156.7.1.x86_64 da installare è in conflitto con ‘vim-plugin-llvm < 19.1.7’ fornito da llvm17-vim-plugins-17.0.6-150600.3.7.1.noarch installato
Soluzione 1: Verranno eseguite le azioni indicate:*
non installare patch:openSUSE-2025-173-1.noarch*
non installare patch:openSUSE-2025-57-1.noarch*
Soluzione 2: disinstallazione di clang-tools-17.0.6-150600.3.7.1.x86_64*
Soluzione 3: disinstallazione di llvm17-vim-plugins-17.0.6-150600.3.7.1.noarch*
Scegliere tra le soluzioni precedenti per numero o annulla [1/2/3/a/d/?] (a): a SCRIPT: opensuse.org-online_update ------- END OF OUTPUT
I never turn off the system; it’s on 24/7, except when I go on vacation. When I got back, I turned everything on and it started again.
The system works perfectly, but I’d like to understand how to fix it, what it’s referring to, and what may have triggered it.
Thanks in advance. You’re always helpful and, above all, you manage to help me understand and fill in my gaps.
Hi @dadozts, while my Italian is really poor , this is highlighting a conflict between packages when it checks for new OpenSUSE updates. It then offers various options on how to deal with those conflicts. In order to fix these you need to run zypper interactively. This means you need to go the command line.
If you’re using a SSH client like PuTTY log in as root and run:
zypper refresh && zypper up --no-recommends
If you are using the WebUI System Shell then you need to run this with sudo, i.e.
`sudo zypper refresh && sudo zypper up --no-recommends
and it will ask for the root password before proceeding.
The safest option to choose in this case it probably going with Soluzione 1 not installing either of the patches at this time. It might be that the versions are temporarily out of sync (and clang and the llvm plugin are connected) and conflicting because of that. If that’s the case, this issue might resolve itself with the next update showing up… though it might not for a while.
Are you using clang/llvm in vim? I don’t have it on my Rockstor box, though that might not mean anything. I want to say I saw this error (or something similar related to clang) on a Leap 15.6 Desktop install but it seemed to have resolved itself after performing another zypper update a few days after seeing it.