kubuntu upgrade error

Here is what is causing the error:

Selecting previously deselected package nvidia-glx-177.
dpkg: considering removing nvidia-glx-new in favour of nvidia-glx-177 ...
nvidia-glx-new is not properly installed - ignoring any dependencies on it.
dpkg: yes, will remove nvidia-glx-new in favour of nvidia-glx-177.
Unpacking nvidia-glx-177 (from .../nvidia-glx-177_177.80-0ubuntu2_amd64.deb) ...
dpkg-divert: error checking `/usr/lib32/libGL.so.1': No such file or directory
dpkg-divert: mismatch on divert-to
  when removing `diversion of /usr/lib32/libGL.so.1.2 to /usr/lib32/nvidia/libGL.so.1.2.xserver-xorg-core by nvidia-glx-new'
  found `diversion of /usr/lib32/libGL.so.1.2 to /usr/lib32/nvidia/libGL.so.1.2.xlibmesa by nvidia-glx-new'
dpkg-divert: `diversion of /usr/lib32/libGL.so.1 to /usr/lib32/nvidia/libGL.so.1.xlibmesa by nvidia-glx-177' clashes with `diversion of /usr/lib32/libGL.so.1 to /usr/lib32/nvidia/libGL.so.1.xlibmesa by nvidia-glx-new'
dpkg: error processing /var/cache/apt/archives/nvidia-glx-177_177.80-0ubuntu2_amd64.deb (--unpack):
 subprocess pre-installation script returned error exit status 2

(Reading database ... 103994 files and directories currently installed.)
Removing xserver-xorg-video-via ...
Removing nvidia-glx-new ...
dpkg-divert: error checking `/usr/lib32/libGL.so.1': No such file or directory
dpkg: error processing nvidia-glx-new (--remove):
 subprocess post-removal script returned error exit status 2
Processing triggers for libc6 ...
ldconfig deferred processing now taking place
Errors were encountered while processing:
 nvidia-glx-new

and from this point on dpkg-divert is rather unhappy each time it is called.

davmor2: did you install the driver from NVIDIA's website too?

No, I did not install the driver from NVidia's website and I'm seeing this too.

nvidia-glx-180 has this problem too. Please fix it.

[This is an automated message]

In Jaunty (9.04), we are dropping the nvidia-graphics-drivers-177 package, which
is now superseded by then nvidia-graphics-drivers-180 package.

  http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180

To transition your bug into the new package, we need your help. Please do the following:

 a. Verify the bug occurs in Jaunty with the -180 driver
     (ISOs: http://cdimage.ubuntu.com/releases/jaunty/)
 b. If you haven't already, please include in the bug:
     * Your /var/log/Xorg.0.log
     * Your /etc/X11/xorg.conf
     * The output of `lspci -vvnn`
     * Steps to reproduce the issue
 c. Under Affects, click the down arrow to the left of 'nvidia-graphics-drivers-177'
 d. Edit the Package to change 'nvidia-graphics-drivers-177' to 'nvidia-graphics-drivers-180'
 e. Click Save Changes

Thank you!

[We'll expire the remaining -177 bugs in a month or so.]

Confirmed in 180.29 in jaunty.

Confirmed in 180.35 in jaunty.

+ Package archive is corrupted. Archiver shows an error.

>+ Package archive is corrupted. Archiver shows an error.
Sorry. Redownload is fix it...

Divert error present.

[This is an automated message]

In Jaunty (9.04), we have just updated to the latest
nvidia-graphics-drivers-180 package from nVidia, version 180.44.

This package provides fixes for a large number of bugs, and we need your
assistance in testing if it fixes the issue you reported.

To do this, please do the following:

 a. Update to the 180.44 version of -nvidia using your favorite update
     method

 b. Attempt to reproduce your bug

 c. If your bug still remains, please simply reply to this email
     indicating so.

 d. If your bug is now solved, you can help us by setting your bug
     report to Fix Released:
     * In launchpad, go to your bug report
     * Click on the downward pointing arrow under Status
     * Set the Status field to 'Fix Released'
     * Comment on the change, such as, 'Verified fixed in 180.44'
     * Click 'Save Changes'

 e. If the original problem is solved but there are now other problems,
     please close the original bug and open new ones for those issues.

Thank you!

For details on the changes in this version of -nvidia, please see:

   http://www.nvidia.com/object/linux_display_ia32_180.44.html

The alternatives system have made this kind of failure between legacy nvidia drivers unlikely to occur anymore, at least not in this way.