Please add to Staging:adi:121

There is a way to uninstall it (Obsoletes), but the point was/is that we do not want it uninstalled (via Obsoletes), since something else may still be using it. IOW, the Obsoletes causes the solver to require an exclusive decision (either–or) between sigrok3 and sigrok4 for no practical reason, since both can exist at the same time.

For the vast majority of shared libraries, only the newest ABI version is wanted, any older version is only relevant for third party repositories/software. Currently on my 2 year old TW installation, I have about a dozen packages installed with different ABI versions. None but the latest version of each library is actually required, but to clean up the system I have to manually find and remove each one. Examples are: - libav{util,codec,format} - libthrift - libboost_{filesystem,iostreams,random,system,...} - libgtk-vnc - ...

Jan Engelhardt (jengelh) - almost 7 years ago

reviewer

Old packages (like sigrok3) will be removed on zypper dup if and when it processes the package "openSUSE-release" (which is regenerated about once or twice a day). This contains all the lines necessary to obsolete/purge packages from as old as openSUSE 12.1.

Then obviously something is broken:

grep libboost_filesystem1_62 /etc/products.d/openSUSE.prod <obsoletepackage>libboost_filesystem1_62_0</obsoletepackage> grep libboost_log1_6 /etc/products.d/openSUSE.prod <obsoletepackage>libboost_log1_61_0</obsoletepackage>

libboost_filesystem1_62 seems to be kept as the dependent libboost_log1_62 has not been obsoleted (but libboost_log1_64 is available ...).

Stefan Brüns (StefanBruens) - almost 7 years ago

author source maintainer

Parser ate html tags ...

grep libboost_filesystem1_62 /etc/products.d/openSUSE.prod (obsoletepackage)libboost_filesystem1_62_0(/obsoletepackage)

grep libboost_log1_6 /etc/products.d/openSUSE.prod (obsoletepackage)libboost_log1_61_0(/obsoletepackage)

Jan Engelhardt (jengelh) - almost 7 years ago

reviewer

obs/Factory/_product:openSUSE-release$ grep -P 'boost.*62' 
Provides: weakremover(libboost_filesystem1_62_0)

Looks mostly ok. libboost_log seems partially missing indeed. @dimstar ?

Is legal just busy, or is something missing?