user/libvncserver (< 0.9.12-r0), user/libfm (< 1.3.1-r1): should be purged from mirrors
Bugzilla ID | 184 |
Reporter | Max Rees (sroracle) |
Assignee | A. Wilcox (awilfox) |
Reported | 2019-08-19 03:45:01 -0500 |
Modified | 2019-08-23 09:50:45 -0500 |
Status | RESOLVED FIXED |
Version | 1.0-BETA3 |
Hardware | Adélie Linux / All |
Importance | --- / normal |
Description
apk skips upgrading libvncserver because the sover of its shared libraries decreased during the bump from 0.9.11 to 0.9.12:
$ apk info -P libvncserver
libvncserver-0.9.12-r0 provides:
so:libvncclient.so.1=0.9.12
so:libvncserver.so.1=0.9.12
libvncserver-0.9.11-r1 provides:
so:libvncclient.so.1=1.0.0
so:libvncserver.so.1=1.0.0
According to upstream[1], this is intentional. Therefore libvncserver{,-dev}-0.9.11-r1.apk needs to be purged from the mirrors.
https://github.com/LibVNC/libvncserver/issues/122#issuecomment-271849456
[1]apk skips upgrading libfm because so:libfm-extra.so.4 was moved to a separate libfm-extra package in libfm 1.3.1-r1:
$ apk info -P libfm
libfm-1.3.1-r0 provides:
so:libfm-extra.so.4=4.1.2
so:libfm-gtk.so.4=4.1.2
so:libfm.so.4=4.1.2
cmd:libfm-pref-apps
cmd:lxshortcut
libfm-1.3.1-r1 provides:
so:libfm-gtk.so.4=4.1.2
so:libfm.so.4=4.1.2
cmd:libfm-pref-apps
cmd:lxshortcut
$ apk info -P libfm-extra
libfm-extra-1.3.0.2-r0 provides:
so:libfm-extra.so.4=4.1.1
libfm-extra-1.3.1-r0 provides:
so:libfm-extra.so.4=4.1.2
It does not seem smart enough to select libfm-extra on its own without either 1. manually adding libfm=1.3.1-r1 or 2. removing libfm{,-dev,-doc,-lang}-1.3.1-r0 from the mirrors. Note that libfm-extra would match a libfm*-1.3.1-r0 glob.