Problem with python3-poppler-qt5

Hello!
Since yesterday, after doing zypper dup, I’ve been getting this result:

 Problem: python3-poppler-qt5-0.75.0-2.9.x86_64 requires python3-sip(api) = 12.7, but this requirement cannot be provided
  deleted providers: python3-sip-4.19.24-2.1.x86_64
 Solution 1: deinstallation of python3-poppler-qt5-0.75.0-2.9.x86_64
 Solution 2: keep obsolete python3-sip-4.19.24-2.1.x86_64
 Solution 3: break python3-poppler-qt5-0.75.0-2.9.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): 1
Resolving dependencies...
Computing distribution upgrade...

Which results in the removal of several related packages, (and the ‘laptop’ pattern, which I think has been changed to ‘mobile’? Am I correct?). My question is: should I proceed, considering that I might lose features and software usability (and perhaps find myself in need of changing software or adding new software)? or should I wait for a few days (if a fix is scheduled)? Thanks in advance and my apologies if this question is not very clear or not very useful.

I thought (?) I’d read a bug report about that quite recently, but am unable to find it, so maybe not…

Personally I’d go with Solution 2: keep obsolete python3-sip-4.19.24-2.1.x86_64 for the moment and see what happens.

Checking, I notice that the package is not installed here.

If I attempt to install python3-poppler-qt5 then I get a similar conflict.

My suggestion: go with solution 2 for now. Maybe it will clear up by the next update.

Thank you tannington and nrickert for your kind replies.
I’ve tried option 2, but that only seems to create more trouble:

 Problem: python3-poppler-qt5-0.75.0-2.9.x86_64 requires python3-sip(api) = 12.7, but this requirement cannot be provided
  deleted providers: python3-sip-4.19.24-2.1.x86_64
 Solution 1: deinstallation of python3-poppler-qt5-0.75.0-2.9.x86_64
 Solution 2: keep obsolete python3-sip-4.19.24-2.1.x86_64
 Solution 3: break python3-poppler-qt5-0.75.0-2.9.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): 2
Resolving dependencies...
Computing distribution upgrade...
2 Problems:
Problem: python3-qt5-devel-5.15.1-2.1.x86_64 requires python3-sip-devel >= 4.19.23, but this requirement cannot be provided
Problem: python3-qt5-devel-5.15.1-2.1.i586 requires python3-sip-devel >= 4.19.23, but this requirement cannot be provided

Problem: python3-qt5-devel-5.15.1-2.1.x86_64 requires python3-sip-devel >= 4.19.23, but this requirement cannot be provided
  not installable providers: python3-sip-devel-5.4.0-1.1.i586[download.opensuse.org-oss]
                   python3-sip-devel-5.4.0-1.1.x86_64[download.opensuse.org-oss]
 Solution 1: deinstallation of python-qt5-common-devel-5.15.1-1.1.noarch
 Solution 2: keep obsolete python-qt5-common-devel-5.15.1-1.1.noarch
 Solution 3: remove lock to allow removal of python3-sip-4.19.24-2.1.x86_64
 Solution 4: break python3-qt5-devel-5.15.1-2.1.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c/d/?] (c): 2

Problem: python3-qt5-devel-5.15.1-2.1.i586 requires python3-sip-devel >= 4.19.23, but this requirement cannot be provided
  not installable providers: python3-sip-devel-5.4.0-1.1.i586[download.opensuse.org-oss]
                   python3-sip-devel-5.4.0-1.1.x86_64[download.opensuse.org-oss]
 Solution 1: deinstallation of python-qtwebengine-qt5-sip-5.15.1-1.1.noarch
 Solution 2: deinstallation of python3-poppler-qt5-0.75.0-2.9.x86_64
 Solution 3: keep obsolete python-qtwebengine-qt5-sip-5.15.1-1.1.noarch
 Solution 4: break python3-qt5-devel-5.15.1-2.1.i586 by ignoring some of its dependencies

Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c/d/?] (c): 

As you both suggested, perhaps it is wise to just wait and see what happens next week. Unless any other idea does come up?
Thanks in advance!

Yes, I’d hold off for a day or two and then try again.

(The bug report I thought I seen, which I’ve now found, was relating to python3 packages, but is not the same as your problem:
https://bugzilla.opensuse.org/show_bug.cgi?id=1178814
https://bugzilla.opensuse.org/show_bug.cgi?id=1178843 )

Thank you! :slight_smile: I’ll report any changes that might happen in the coming days.

I went through that yesterday.
First I checked if I actually need those ‘offending’ packages.
I had only one package (meteo-qt) that required python-sip. I did rebuild meteo-qt without the requirement for python-sip and deleted python-sip (used OBS). I also had the other packages that are mentioned in your post, but I no longer need them because I no longer build rpm’s locally. Deleted them all and I see no negative effects of this. If you let python-qt-devel install, it will pull in all kind of development packages (dozens), you can avoid that if you delete python-qt-common-devel before you zypper dup. If you need those packages then you should wait some time, but do not expect a quick fix. If I see that correctly the root cause is actually calibre 5.x, because it requires python3-qt5-sip and that package was pushed into tumbleweed and that then triggered the issues.
If you intend to delete the ‘offending’ packages make sure you have a working backup in case you need to go back. I hope it is understandable what I wrote, because English is not my native language.

Took a look at this,
May require insight of someone who actually builds apps using python-sip,
Appears that python-sip is a set of C/C++ bindings that hasn’t been updated since forever, but still works.
The version of python-sip that you already have is likely the last version that will ever be built, so save it.
Then there is this other package python-sip(api) which I speculate is another set of bindings that modify access further.
I don’t see that this package has ever been built for openSUSE/SUSE but should be available from PyPi and various rpm repositories.
If your build requires this API package, it’ll fail without it even if you have the original python-sip package.

TSU