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

[Russ Allbery]

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.

> When I try to purge it, it says:

> Removing nvidia-glx-legacy-173xx ...
> Purging configuration files for nvidia-glx-legacy-173xx ...
> rm: cannot remove `/usr/lib/libGL.so': No such file or directory
> 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.

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

> A new version of nvidia-glx-legacy-173xx will not help me,

I'm not sure that's true.

> how do I purge the package? Should I manually edit the postrm script?

That's what I'd do.

-- 
Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>