[pkg-nvidia-devel] Bug#588590: Bug#588590: Conflicts with nvidia-glx

[Ariel]

On Tue, 7 Sep 2010, Russ Allbery wrote:

> Ariel <asdebian at dsgml.com> writes:
>
>> I have the same trouble with nvidia-glx. I had both nvidia-glx and
>> nvidia-glx-legacy-173xx installed (due to upgrading my video card), and
>> now I can't purge nvidia-glx-legacy-173xx.

>> dpkg-divert: mismatch on package
>>   when removing `diversion of /usr/lib/libGL.so.1 to /usr/lib/nvidia/libGL.so.1.xlibmesa by nvidia-glx-legacy-173xx'
>>   found `diversion of /usr/lib/libGL.so.1 to /usr/lib/nvidia/libGL.so.1.xlibmesa by nvidia-glx'

> So you have old versions of both nvidia-glx and nvidia-glx-legacy-173xx
> installed, both of which predate the reworking of how the diversions are
> handled.  I wonder how you managed to get both packages installed at the
> same time ever.  They've always conflicted in their diversions, and I
> would have expected one or the other to have failed to install.  I don't
> understand how nvidia-glx managed to take over the diversions while
> leaving nvidia-glx-legacy-173xx in a state where it still thought it owned
> the diversions.

nvidia-glx-legacy-173xx doesn't seem to think it owns the diversions - 
they are manually removed in the postrm script.

And no, I don't know how it got installed this way.

> Thankfully, this is one of the problems that will be entirely fixed going
> forward, with the new shared diversion handling packages.

Is this uploaded currently, or planned? And does this mean 
nvidia-glx-legacy-173xx and nvidia-glx can both be installed at the same 
time? (Although, that's probably not useful since the kernel module can't 
be.)

>> A new version of nvidia-glx-legacy-173xx will not help me,
>
> I'm not sure that's true.

I meant, I'm not going to install it because I'm using nvidia-glx now.

>> how do I purge the package? Should I manually edit the postrm script?
>
> That's what I'd do.

OK. Thank you.

 	-Ariel