severity 400129 normal tag 400129 + unreproducible thanks On Friday 24 November 2006 11:10, Randall Donald wrote: > > $ sudo dpkg --purge nvidia-glx > > (Reading database ... 291706 files and directories currently > > installed.) Removing nvidia-glx ... > > dpkg-divert: rename involves overwriting `/usr/lib/libGL.so' with > > different file `/usr/lib/nvidia/libGL.so.xlibmesa', not allowed > > dpkg: error processing nvidia-glx (--purge): > > subprocess post-removal script returned error exit status 2 > > Errors were encountered while processing: > > nvidia-glx > > > > > > nvidia-glx does purge if I remove libgl1-mesa-dev first. > > Hmm, I wonder if this has to do with the file created by the init > script. I'll try to reproduce this tonight.
Hi Randall I thought that this might also be present in the -legacy packages, since the packaging is similar. When I couldn't reproduce it there, your comments about the init script caused me to try to reproduce it again. I can't reproduce this now. I'm guessing that the root cause was probably somewhere in the mixture of semi-current and obsolete nvidia-* packages on the system at boot time. When I booted i had the following packages installed: nvidia-glx 1.0.8776-1 nvidia-kernel-2.6.18-1-486 1.0.8776+2 nvidia-kernel-legacy-source 1.0.7184-1 nvidia-kernel-source 1.0.8774-2 nvidia-kernel-2.6.17-2-486 1.0.8774-2+2.6.17-8 (built locally IIRC) nvidia-kernel-2.6.17-2-686 1.0.8774-2+2.6.17-8 (built locally IIRC) Before filing the bug report at severity:serious I removed the obsolete nvidia packages, upgraded to the latest nvidia-glx, purged nvidia-glx (by first removing libgl1-mesa-dev), reinstalled both packages and confirmed that I could still reproduce the bug. However at no stage did I actually reboot. Most (all?) output in the bug report came from the last round of tests. Unless you or someone else can reproduce it, or the above gives you some new clue, I suggest closing. (I should be able to restore a backup from earlier this week if anyone really wants to pursue this). HTH Andrew V. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
