On 2010-08-29 02:53, Russ Allbery wrote: > Kejia柯嘉 <w.ke...@gmail.com> writes: > >> I re-installed `libgl1-mesa-glx'. Yes, everything works pretty good >> now. Thank you. > > Thanks! > > Andreas, it looks like the alternative setup during initial install may > fail if there's no libgl1 already installed on the system. While that's > probably relatively hard if one has any GUI programs installed, we should > handle that case somehow.
Problem is if there is some libGL.so.1 not owned by any package pointing to something else than libGL.so.1.2 - after diverting that file it becomes a dangling symlink which is not a valid target for an alternative. I already committed some validation for the diverted libGL.so.1 to fix 594416 which was a similar problem: * if libGL.so.1 is not owned by any package or pointing to something else than libGL.so.1.2, it gets removed * if a diverted libGL.so.1.2 exists and a diverted libGL.so.1 is missing, the diverted link is recreated That should cover the majority of cases. > One approach would be to make libgl1-nvidia-alternatives depend on > libgl1-mesa-glx to ensure that it exists on the system (and likewise have Would not fix the problem if libGL.so.1 was overwritten by the nvidia installer at some point. > libglx-nvidia-alternatives depend on xserver-xorg-core). Have you tested I don't think we'll run into similar problems with libglx.so, there are much less symlinks involved. > what happens when the other package isn't installed? There is no problem if the other packages are not installed, problems only occur if there are files (especially symlinks) not shipped by a Debian package (or symlinks pointing to something else than they do in Debian packages). I successfully tested upgrading from all old Debian versions that were in sid since lenny (OK, not all, there were some versions inbetween requiring the ia32-apt-get mess, these I couldn't test). I tested without and with xorg/mesa installed as well as these packages being installed/removed after installing the old version and before upgrading to current. Testing "broken" systems with content not reproducible from Debian package is much harder. > Hm, I could have sworn I'd tested this earlier and it worked properly, but > maybe it depends on what version of dpkg one has.... Or you just didn't reproduce the correct "broken" system. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
