Today I run “zypper dup” and got the following information about conflicts/problems (see below). I did not proceed, as I wish to figure out what is happening and how to solve it.
Apparently, the correct libQt6Core cannot be found:
Computing distribution upgrade...
10 Problems:
Problem: the installed python38-PyQt6-6.1.1-3.4.x86_64 requires 'libQt6Core.so.6(Qt_6.1.3_PRIVATE_API)(64bit)', but this requirement cannot be provided
Problem: the installed qt6-quick3d-6.0.3-1.11.x86_64 requires 'libQt6Gui.so.6(Qt_6.1.3_PRIVATE_API)(64bit)', but this requirement cannot be provided
Problem: the installed libQt6Gui6-6.1.3-1.3.x86_64 requires 'libQt6DBus6 = 6.1.3', but this requirement cannot be provided
Problem: the installed libQt6Gui6-6.1.3-1.3.x86_64 requires 'libQt6OpenGL.so.6(Qt_6.1.3_PRIVATE_API)(64bit)', but this requirement cannot be provided
Problem: the installed libQt6OpenGL6-6.1.3-1.3.x86_64 requires 'libQt6Widgets6 = 6.1.3', but this requirement cannot be provided
Problem: the to be installed libQt6Concurrent6-6.2.0-1.1.x86_64 requires 'libQt6Core6 = 6.2.0', but this requirement cannot be provided
Problem: the to be installed libQt6Network6-6.2.0-1.1.x86_64 requires 'libQt6Core6 = 6.2.0', but this requirement cannot be provided
Problem: the to be installed libQt6Sql6-6.2.0-1.1.x86_64 requires 'libQt6Core6 = 6.2.0', but this requirement cannot be provided
Problem: the to be installed libQt6Test6-6.2.0-1.1.x86_64 requires 'libQt6Core6 = 6.2.0', but this requirement cannot be provided
Problem: the to be installed libQt6Xml6-6.2.0-1.1.x86_64 requires 'libQt6Core6 = 6.2.0', but this requirement cannot be provided
Problem: the installed python38-PyQt6-6.1.1-3.4.x86_64 requires 'libQt6Core.so.6(Qt_6.1.3_PRIVATE_API)(64bit)', but this requirement cannot be provided
deleted providers: libQt6Core6-6.1.3-1.3.x86_64
Solution 1: deinstallation of python38-PyQt6-6.1.1-3.4.x86_64
Solution 2: keep obsolete libQt6Core6-6.1.3-1.3.x86_64
Solution 3: break python38-PyQt6-6.1.1-3.4.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c):
I see that libQt6 is present, but there may be some confusion regarding its version number:
# zypper if libQt6Core6
Loading repository data...
Reading installed packages...
Information for package libQt6Core6:
------------------------------------
Repository : openSUSE-20210131-0
Name : libQt6Core6
Version : 6.2.0-1.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 5.7 MiB
Installed : Yes (automatically)
Status : out-of-date (version 6.1.3-1.3 installed)
Source package : qt6-base-6.2.0-1.1.src
Summary : Qt 6 Core library
Description :
The Qt 6 Core library. It adds these features to C++:
* a mechanism for object communication called signals and slots
* queryable and designable object properties
* hierarchical and queryable object trees that organize
* object ownership in a natural way with guarded pointers (QPointer)
* a dynamic cast that works across library boundaries
Is this a version conflict with the packages or just a confusion with version naming?
Add the first becasue it may be important. If I run “zypper up” it says that a bunch of things are not going to be updated, including the above cited package libQt6 and related.
Packages in a repository are updated as soon as they are published and build OK. Not all packages are equal though, some prevent publishing a new snapshot, but not the one at hand.
Cancel zypper dup and wait a few days, it goes away (I don’t think reporting an issue is warranted in this case)
If you absolutely need to proceed to upgrade some other package, then “keep obsolete” is possibly a reasonable choice
It’s curious how many folks feel compelled to take action in this screen. I’ll file an issue to improve wording a bit.
Asking zypper to perform “as it deemed best” is insane. It lacks context. Learn how to rollback snapshots just in case. Also “zypper up” is not a recommended approach. “zypper dup” always. Packman was not the issue and you probably lost multimedia functionality in Firefox.
Inevitably zypper reports update conflicts in my OpenSUSE Tumbleweed installation. In the past (when I was an absolute noob), I tried one of the options offered by zypper (e.g. deinstallation of package(s), ignoring dependencies, etc.) That often triggered other conflicts and ultimately an unstable or broken system, in my experience. What I’ve found better is a bit of patience and time until relevant packages in all my repositories are updated and/or dependencies fixed. It may take few days or even about a week before things seem to iron out by themselves. Wait a few days, clean the local zypper cache before refreshing and then attempt a dup:
$ sudo zypper cc -a
$ sudo zypper ref
$ sudo zypper dup
It’s a bit frustrating to wait and have a system potentially vulnerable. I also think of new users to OpenSUSE or Linux who wouldn’t know what to do or could bork their system.
I don’t see those very often. When I do see a conflict, I usually go with the option to keep an obsolete package. And yes, sometimes this will cause additional conflicts.
Having been out of the office for some weeks, I found that I had some 1164 updates waiting (now 1165). I am working on a project involving openFOAM, here is what I found when attempting to update:
Update Error
problem with the installed libcerf1-1.17-23.15.x86_64
the to be installed openfoam-selector-1.0.6-1.39.noarch requires 'perl(:MODULE_COMPAT_5.34.1)', but this requirement cannot be provided
nothing provides 'libboost_system.so.1.76.0()(64bit)' needed by the to be installed
From what I find in this thread, I draw the conclusion that I am advised not to try to solve the problem myself, but wait till there is a solution. If somebody has a better solution for my particular problem, I am all ears.
Now:
Would there be a way (‘alarm knob’) to inform that there is a problem with the update and the failure message itself ( ‘… by the to be installed’)?
Your openFOAM problem is something different. As it is in the science repository and the Tumbleweed support is kind of “experimental”…
Tumbleweed support should be regarded as a purely random event.
You can lock your openFoam packages so that you can update the rest of your system at least.
(Or remove openFOAM temporary and cross your fingers that the devs are able to create proper packages for TW in the future…)
Hi
The switch to perl 5.36.0 cause numerous fallouts from leaf packages, most just needed rebuilding, some needed patches applied. Looks like openfoam-selector rebuilt ok, if you have the science repo active. I would force a refresh and the use zypper -vvv dup to see if it now upgrades properly.
For libboost76 that has been long gone in Tumbleweed… at 79 these days…
I have been able to make upgrades some 1100 objects, but I am giving up on openFOAM under Tumbleweed for the moment; removed openFOAM. Your reply was indeed most helpful: Thanks!
I gather you dislike new packaging and provisioning models. But you should be able to get this tool running easily with podman, a stable distro image (Leap/Debian/etc) and one of x11docker/distrobox/toolbox.
What I really dislike, is not being able running openFOAM under openSUSE. Tumbleweed seems to be some kind of a moving target, so I am contemplating switching to 15.4. The project I am working on has no explicit deadline, so I think I have the following options: 1) switch to 15.4 (an easy task?) 2) switch to Windows 10, or 3) go for podman.
Comments and suggestions are appreciated (as always).
You must weight your original reasons to go for Tumbleweed against your wish to have a stable environment for your project development. We can not do that for you, specially as we do not know why you choose for Tumbleweed on the development system in the first place.
The development project utilizing openFOAM started in May this year (months after I switched from 15.2 to Tumbleweed); that Tumbleweed potentially constitutes an unstable operating system - as you seem to imply - was unknown to me.
Was I am asking for is what would one having experience with openFOAM suggest is the better alternative: 1) switch to 15.4 (an easy task?) 2) switch to Windows 10, or 3) go for podman.
I did not really imply that Tumbleweed is “unstable” (at least I hope not). But there is a difference in the policy between Leap and Tumbleweed. And while I understand that Tumbleweed is general experienced as stable (in the meaning of having not may bugs released with new versions), it is still a rolling release. That means that from the point of view of a user there can be changes to experience with every new Tumbleweed snapshot.
For me, stability also means that I do not get a changed user interface of a program with a new snapshot, being it small or large. I get already fed up when two buttons in a GUI exchange position. The Tumbleweed user might love that, because it is the newest. So it is Leap for me. Getting surprises about once a year is enough.