Tumbleweed update fails looking for certain python2-sip... packages

English Install/Boot/Login
1

My Tumbleweed is set up to use the “standard” repos only, with packman prioritized higher according to https://forums.opensuse.org/showthread.php/531333-Zypper-dup-priorities:

sudo zypper lr -P
# | Alias               | Name                        | Aktiviert | GPG-Überprüfung | Aktualisierung | Priorität
--+---------------------+-----------------------------+-----------+-----------------+----------------+----------
1 | libdvdcss           | libdvdcss                   | Ja        | (r ) Ja         | Ja             |   90     
3 | packman             | packman                     | Ja        | (r ) Ja         | Ja             |   90     
2 | openSUSE-20170712-0 | openSUSE-20170712-0         | Nein      | ----            | ----           |   99     
4 | repo-debug          | openSUSE-Tumbleweed-Debug   | Nein      | ----            | ----           |   99     
5 | repo-non-oss        | openSUSE-Tumbleweed-Non-Oss | Ja        | (r ) Ja         | Ja             |   99     
6 | repo-oss            | openSUSE-Tumbleweed-Oss     | Ja        | (r ) Ja         | Ja             |   99     
7 | repo-source         | openSUSE-Tumbleweed-Source  | Nein      | ----            | ----           |   99     
8 | repo-update         | openSUSE-Tumbleweed-Update  | Ja        | (r ) Ja         | Ja             |   99

I do follow the recommended procedure of doing

zypper ref
zypper dup

eventually followed by a check what

zypper dup --allow-vendor-change

has to say when zypper dup alone (i.e. with --no-allow-vendor-change by default) asks questions I can’t answer easily.

When trying to do a Tumbleweed update from 20190209 to the current state today, zypper dup reports two package problems (“two packages cannot be supplied”):

Distributions-Aktualisierungen werden verarbeitet...
2 Probleme:
Problem: python2-qt4-4.12.3-1.3.x86_64 benötigt python2-sip(api) = 12.5, kann jedoch nicht zur Verfügung gestellt werden
Problem: python2-sip-4.19.13-2.3.x86_64 benötigt python2-sip-common = 4.19.13, kann jedoch nicht zur Verfügung gestellt werden

Problem: python2-qt4-4.12.3-1.3.x86_64 benötigt python2-sip(api) = 12.5, kann jedoch nicht zur Verfügung gestellt werden
  Gelöschte Anbieter: python2-sip-4.19.13-2.3.x86_64
 Lösung 1: Deinstallation von python2-qt4-4.12.3-1.3.x86_64
 Lösung 2: veraltetes python2-sip-4.19.13-2.3.x86_64 beibehalten
 Lösung 3: python2-qt4-4.12.3-1.3.x86_64 durch Ignorieren einiger Abhängigkeiten brechen

At this point I quit zypper dup, not having seen yet the proposed solutions for the second problem.

zypper dup --allow-vendor-change produces the same failure reports. Quitting it, too, of course.

Checking the repositories with YaST for python2-sip(api) and python2-sip-common, I do see only python2-sip 4.19.13-2.3 being installed / 4.19.14-1.1 being available.

How should I proceed with updating Tumbleweed?

Thanks in advance.

2

I’ve just had the same “problem”…

It’s unlikely anything requires “python2-qt4” so you could probably choose the option to remove it.

You can check first by:

rpm -q --whatrequires python2-qt4

If you do have anything that requires it, then during the zypper dup you should be given the option to retain an obsolete package.

3

Maybe it is not needed, but for the future:
This does not provide much useful information, apart from the fact that you have repos and that they have names and aliases. To see what repos you have, one needs to see where they are, The URLs. Thus better use

zypper lr -d

in the future.

(Or, if you want to help non Germans in understanding:

LANG=C zypper lr -d

)

4

Thank you very much, good to remember.

5

Thanks. I checked as directed:

[myself@susytmblwdke ~]$ rpm -q --whatrequires python2-qt4
no package requires python2-qt4

[myself@susytmblwdke ~]$ rpm -q --whatrequires python2-sip
no package requires python2-sip

And additionally:

[myself@susytmblwdke ~]$ zypper search --requires python2-qt4
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...

S | Name                   | Zusammenfassung                                   | Typ  
--+------------------------+---------------------------------------------------+------
  | python2-pyface         | Traits-capable windowing framework                | Paket
  | python2-qscintilla-qt4 | Python  Bindings for the C++ Editor Class Library | Paket
i | python2-qt4            | PyQt - python bindings for Qt 4                   | Paket
  | python2-qt4-devel      | PyQt - devel part of python bindings for Qt 4     | Paket
  | python2-vispy          | Interactive visualization in Python               | Paket

[myself@susytmblwdke ~]$ zypper search --requires python2-sip
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...

S  | Name                      | Zusammenfassung                                   | Typ  
---+---------------------------+---------------------------------------------------+------
   | python2-QtPy              | Abstraction layer on top of Qt bindings           | Paket
   | python2-jupyter_qtconsole | Jupyter Qt console                                | Paket
   | python2-qscintilla-qt4    | Python  Bindings for the C++ Editor Class Library | Paket
   | python2-qscintilla-qt5    | Python  Bindings for the C++ Editor Class Library | Paket
i  | python2-qt4               | PyQt - python bindings for Qt 4                   | Paket
   | python2-qt4-devel         | PyQt - devel part of python bindings for Qt 4     | Paket
   | python2-qt5               | PyQt - python bindings for Qt 5                   | Paket
   | python2-qt5-devel         | PyQt - devel part of python bindings for Qt 5     | Paket
i+ | python2-sip               | SIP tool to use python sip bindings               | Paket
   | python2-sip-devel         | SIP tool to create python bindings                | Paket

The rpm outputs tell me to just delete both packages python2-qt4 and python2-sip in question. Sorry, I am not exactly sure how to read the zypper search outputs with respect to the i and i+ status. Do they tell me the same?

6

[QUOTE=111MilesToGo;2895048]Thanks. I checked as directed:

[myself@susytmblwdke ~]$ rpm -q --whatrequires python2-qt4
no package requires python2-qt4

[myself@susytmblwdke ~]$ rpm -q --whatrequires python2-sip
no package requires python2-sip

OK… Then during zypper dup select the option to delete python2-qt4 ( Lösung 1: Deinstallation von python2-qt4-4.12.3-1.3.x86_64 ) and all should be fine.

7

[quote="“tannington,post:6,topic:135463”]

Sorry to have to keep on. Things ain’t that easy. Previously, I had not yet selected a solution for the first problem; now that I did it, zypper dup comes up with the second problem:

sudo zypper dup
[sudo] Passwort für root: 
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...
Warnung: Sie sind im Begriff, eine Distributionsaktualisierung mit allen aktivierten Repositorys durchzuführen. Vergewissern Sie sich, dass diese Repositorys kompatibel sind, bevor Sie fortfahren. Weitere Informationen zu diesem Kommando finden Sie unter 'man zypper'.
Distributions-Aktualisierungen werden verarbeitet...
2 Probleme:
Problem: python2-qt4-4.12.3-1.3.x86_64 benötigt python2-sip(api) = 12.5, kann jedoch nicht zur Verfügung gestellt werden
Problem: python2-sip-4.19.13-2.3.x86_64 benötigt python2-sip-common = 4.19.13, kann jedoch nicht zur Verfügung gestellt werden

Problem: python2-qt4-4.12.3-1.3.x86_64 benötigt python2-sip(api) = 12.5, kann jedoch nicht zur Verfügung gestellt werden
  Gelöschte Anbieter: python2-sip-4.19.13-2.3.x86_64
 Lösung 1: Deinstallation von python2-qt4-4.12.3-1.3.x86_64
 Lösung 2: veraltetes python2-sip-4.19.13-2.3.x86_64 beibehalten
 Lösung 3: python2-qt4-4.12.3-1.3.x86_64 durch Ignorieren einiger Abhängigkeiten brechen

Wählen Sie aus den obigen Lösungen mittels Nummer oder Sie (u)eberspringen, (w)iederholen oder brechen (a)b [1/2/3/u/w/a] (a): 1

Problem: python2-sip-4.19.13-2.3.x86_64 benötigt python2-sip-common = 4.19.13, kann jedoch nicht zur Verfügung gestellt werden
  Gelöschte Anbieter: python-sip-common-4.19.13-2.3.x86_64
 Lösung 1: Deinstallation von puddletag-1.2.0-2.5.noarch
 Lösung 2: veraltetes python-sip-common-4.19.13-2.3.x86_64 beibehalten
 Lösung 3: python2-sip-4.19.13-2.3.x86_64 durch Ignorieren einiger Abhängigkeiten brechen

Wählen Sie aus den obigen Lösungen mittels Nummer oder Sie (u)eberspringen, (w)iederholen oder brechen (a)b [1/2/3/u/w/a] (a):

I must say I’m lost by now. Looking at puddletag which shows up only now:

[myself@susytmblwdke ~]$ zypper info --requires puddletag*
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...


Informationen zu Paket puddletag:
---------------------------------
Repository         : openSUSE-Tumbleweed-Oss
Name               : puddletag              
Version            : 1.2.0-2.5              
Arch               : noarch                 
Anbieter           : openSUSE               
Installierte Größe : 3,6 MiB                
Installiert        : Ja                     
Status             : aktuell                
Quellpaket         : puddletag-1.2.0-2.5.src
Zusammenfassung    : An audio tag editor    
Beschreibung       :                        
    puddletag is an audio tag editor (primarily created) for GNU/Linux similar
    to the Windows program, Mp3tag. Unlike most taggers for GNU/Linux, it uses
    a spreadsheet-like layout so that all the tags you want to edit by hand are
    visible and easily editable. The usual tag editor features are supported
    like extracting tag information from filenames, renaming files based on
    their tags by using patterns and basic tag editing. Then there’re
    Functions, which can do things like replace text, trim it, do case
    conversions, etc. Actions can automate repetitive tasks. Doing web lookups
    using Amazon (including cover art), Discogs (does cover art too!), FreeDB
    and MusicBrainz is also supported. There’s quite a bit more, but I’ve
    reached my comma quota. Supported formats: ID3v1, ID3v2 (mp3), MP4 (mp4,
    m4a, etc.), VorbisComments (ogg, flac), Musepack (mpc), Monkey’s Audio
    (.ape) and WavPack (wv).
Anforderungen      : [8]                    
    /usr/bin/python
    python-qt4
    python-pyparsing
    python-configobj
    python-mutagen
    python(abi) = 2.7
    /bin/sh
    update-desktop-files

puddletag calls for python-qt4, but it seems that one is not present:

[myself@susytmblwdke ~]$ zypper info python-qt4
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...


Paket 'python-qt4' nicht gefunden.

Looks strange to me. Asking the YaST software installer to check the dependencies on my Tumbleweed KDE, it comes up with “all okay”. Launching puddletag (from Plasma desktop or Konsole) goes well, no complaints; I just don’t want to let puddletag work on audio files right now, it’s getting too involved.

Please, how should I get rid of those dependency problems now while trying to update Tumbleweed? I am sort of willing to delete python2-qt4-4.12.3-1.3. Should I keep the outdated python-sip-common-4.19.13-2.3? Anyway, I don’t quite understand what’s going on here, so my foremost tendency is to refrain from updateing Tumbleweed for the time being, in the hope that with the next update these problems might go away. Hope is never forbidden …, but actually I don’t quite think waiting would help.

8

Ah… OK.

For the moment then, don’t uninstall python2-qt4 and keep the obsolete python2-sip, that should at least allow the zypper dup to complete.

It’s not a problem that will go away though, you’ll have to select those options on subsequent “dups”.

Puddletag, it seems is quite old, and the last release appears to have been in 2016, unfortunately it uses python2 and qt4. Perhaps consider a different audio tagger, kid3 maybe would suit your needs?

9

Thank you, tannington. Getting rid of puddletag resolves it all, making the python2-xxx in question obsolete.

I will give kid3 a close look. Still, Mp3tag on Windows is the classic, which is one of the reasons I still need a Windoze VM.

Thanks!