Package: libgl1
Version: 1.0.0-1
Severity: normal
Hi,
if the system got messed up by some proprietary installer, it may be
well possible that some cruft libGL.so.1.X.Y outside the control of dpkg
is left on the system and takes precedence over libGL.so.1.0.0
Like in #879041: libglvnd0: Nvidia-Installer 384.90: "An incomplete
installation of libglvnd was found." where an old copy of the MESA
libGL.so.1.2.0 was left and was still ebing used.
ldconfig will give precedence to the file with the highest filename
version as the target of the SONAME link libGL.so.1. So unfortunately
libGL.so.1.0.0 will always be the loser.
Renaming libGL.so.1.0.0 (or just adding a symlink with a higher version
to it) would circumvent these bugs by giving precedence to the libglvnd
libGL.so.1.
The following filenames have been in use in the past and present:
libgl1: /usr/lib/x86_64-linux-gnu/libGL.so.1.0.0
libgl1-fglrx-glx: /usr/lib/x86_64-linux-gnu/fglrx/fglrx-libGL.so.1.2
libgl1-fglrx-legacy-glx: /usr/lib/x86_64-linux-gnu/fglrx/fglrx-libGL.so.1.2
libgl1-glvnd-nvidia-glx: /usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1.0.0
libgl1-mesa-glx: /usr/lib/x86_64-linux-gnu/libGL.so.1.2
libgl1-mesa-glx: /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0
libgl1-mesa-swx11: /usr/lib/x86_64-linux-gnu/libGL.so.1.5.08005
libgl1-mesa-swx11: /usr/lib/x86_64-linux-gnu/libGL.so.1.6.0
I would suggest to add a symlink
libGL.so.1.7.0 -> libGL.so.1.0.0
That also means to adjust the SONAME link to
libGL.so.1 -> libGL.so.1.7.0
to ship the link like it would be created by ldconfig, otherwise it may
trigger errors in some library symlink validation test in piuparts.
Also give me a notice before uploading such a change s.t. I can adjust
glx-diversions accordingly and you can bump the Breaks against the
glx-diversions versions not knowing about the new filename.
It may be worthwile suggesting such a rename to upstream, too.
Andreas
