Zypper dup missing requirement libQt6Core.so.6(Qt_6.9.2_PRIVATE_API)(64bit)

English Install/Boot/Login
1

I’ve just done a “zypper dup” today and got:

tumbleweed:~ # zypper dup
Loading repository data…
Reading installed packages…
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See ‘man zypper’ for more information about this command.
Computing distribution upgrade…

Problem: 1: the to be installed texmaker-6.0.1-3.1.x86_64 requires ‘libQt6Core.so.6(Qt_6.9.2_PRIVATE_API)(64bit)’, but this requirement cannot be provided
deleted providers: libQt6Core6-6.9.2-1.1.x86_64

Solution 1: deinstallation of texmaker-6.0.1-2.2.x86_64
Solution 2: keep obsolete libQt6Core6-6.9.2-1.1.x86_64
Solution 3: break texmaker-6.0.1-3.1.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c/d/?] (c):

2

This is one of the packages where the maintainer did not apply the Qt 6.10 patch yet. Somebody needs to open a bugreport.

https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/KMEOWKIFQUKNE2AEN4NOW3RHGHL7CZUL/

1 Like
3

Because I spent a few minutes how to resolve it, here is a short instruction for Leap 16.0. The patch was added to the Texmakerone month ago but I needed to add appropriate repo (in my default repo the Texmaker has not been updated yet):

sudo zypper addrepo https://download.opensuse.org/repositories/Publishing/16.0/Publishing.repo
sudo zypper refresh
sudo zypper install texmaker
4

I doubt this “solves” it. It is a by-pass until the real patch is implemented.

5

I assume that after updating the the lib automated integration tests passed.

6

Sorry, I am not sure what you are saying here. But I mean that when the patch hits the normal Tumbleweed snapshot, one better checks if the packages installed from that Leap 16.0 repo are switched back to those of the Tumbleweed repo and that then one should remove (at least disable) that extra repo.

7

You stated that this is not a solution to the problem, but a by-pass. Because you didn’t explain what you meant, I was forced to guess what you were thinking. The only thing that came to my mind was that the applied fix (library upgrade) might break the integration with the rest of the system. That’s why I mentioned integration tests, which should catch such an error.

Now I understand what you meant. I still believe this solution is good for an already working system with applications. For me, preparing the document is more important than wondering whether adding a repository from the official domain makes sense.

8

And the texmaker-6.0.1-4.1.x86_64.rpm that includes this patch is in Tumbleweed.