Upgrading to libQt6Gui6-6.7.0 seems lead to a maze of dependency issues, anyone else?

English Applications
1

Tumbleweed KDE here, when trying a zypper dup today I was informed that

> 
> the installed python311-PyQt6-6.6.1-1.5.x86_64 requires 'libQt6Core.so.6(Qt_6.6.3_PRIVATE_API)(64bit)', but this requirement cannot be provided
> deleted providers: libQt6Core6-6.6.3-1.1.x86_64
> 
> Problem: 2: the installed calibre-7.4.0-2.2.x86_64 requires 'libQt6Gui.so.6(Qt_6.6.3_PRIVATE_API)(64bit)', but this requirement cannot be provided
> deleted providers: libQt6Gui6-6.6.3-1.1.x86_64
> 
> Problem: 3: the installed python311-PyQt6-6.6.1-1.5.x86_64 requires 'libQt6Core.so.6(Qt_6.6.3_PRIVATE_API)(64bit)', but this requirement cannot be provided
> deleted providers: libQt6Core6-6.6.3-1.1.x86_64

The system is in fact trying to upgrade the library to libQt6Gui6-6.7.0, and whichever solution I choose, either I don’t upgrade anything or I break/uninstall something I care about. Has anyone had the same issue? I tried to check the mailing lists in case something was brought up but they seem to be down.

2 Likes
2

Hello,

I had also some problem today and ended with removing some python312 rpm

2024-04-10 22:19:15|remove |python312-PyQt6-3D|6.6.0-2.5|x86_64|root@hpprol2|
2024-04-10 22:19:16|remove |python312-PyQt6-Charts|6.6.0-2.5|x86_64|root@hpprol2|
2024-04-10 22:19:20|remove |python312-PyQt6-DataVisualization|6.6.0-2.4|x86_64|root@hpprol2|
2024-04-10 22:19:21|remove |python312-PyQt6-QScintilla|2.14.1-2.3|x86_64|root@hpprol2|

I think that these objects have not been rebuild against libQt6xxxx-6.7.0. Removing these python rpm gives no problem on my system.
I see that you have also a problem with calibre. So removing it is not a solution if you use it.

I suggest to wait next snapshot to see if it resolves the problem, if not open a bug report.

Regards
Philippe

1 Like
3

Hi,

this has been discussed also here:

and here:

3 Likes
4

I’m facing the same issue. So the only solution for now is to postpone the upgrade?

5

Yes. This happens sometimes: a package does not compile and if it is a dependency for other packages that leads to a cascade of problems. Waiting for the particular problem to be solved is often a the best strategy in such cases.

3 Likes
6

cool, thanks, hope it will be fixed soon because there’s a big kde update available

7

If I understand correctly, the package has now been fixed and the patch accepted. So perhaps the fix is probably reaching the repository soon.

2 Likes
8

That is great news, since even with a new snapshot things did not improve. Thanks!

1 Like
9

It seems to be resolved now.

1 Like
10

The repo has been updated. I have just updated successfully.

1 Like
11

Works for me too, thanks to everyone!

1 Like