[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#187365: xlibmesa3-glu bug #187365



On Wed, Sep 24, 2003 at 12:58:01PM -0500, Steve Doerr wrote:
> Hi Branden.  I found it, but I'm still getting conflict with a libutah 
> package.
>
> Get:1 http://ftp.egr.msu.edu ../project/experimental/main xlibmesa-glu
> 4.3.0-0pre1v1 [227kB]
> Fetched 227kB in 1s (122kB/s)
> Selecting previously deselected package xlibmesa-glu.
> (Reading database ... 69260 files and directories currently installed.)
> Unpacking xlibmesa-glu (from .../xlibmesa-glu_4.3.0-0pre1v1_i386.deb) ...
> dpkg: error processing
> /var/cache/apt/archives/xlibmesa-glu_4.3.0-0pre1v1_i386.deb (--unpack):
> trying to overwrite `/usr/lib/libGLU.so.1', which is also in package
> libutahglx1
> Errors were encountered while processing:
> /var/cache/apt/archives/xlibmesa-glu_4.3.0-0pre1v1_i386.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> Are these different versions of libGLU.so.1?  How can I check?

I'm not an expert on libGLU issues, so I suggest asking debian-user or
maybe debian-x.

libutahglx1 doesn't appear to be maintained anymore, it has seen several
NMUs in a row:

branden@auric:~$ madison libutahglx1
W: Archive maintenance is in progress; database inconsistencies are possible.
libutahglx1 | 0.0-cvs-20010702-3 |        stable | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc
libutahglx1 | 0.0-cvs-20010702-4.2 |       testing | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc
libutahglx1 | 0.0-cvs-20010702-4.2 |      unstable | m68k
libutahglx1 | 0.0-cvs-20010702-4.3 |      unstable | alpha, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc

> I was going to zap libutahglx1, but my libraries seem to be fairly
> wrecked (this system started as deb 2.1 a couple of years ago and I've
> just been apt'ing for security, etc. since then).  Got any resources or
> references to straighten out something like this?  Apt can't seem to get
> past this error, but if it would, would a dist-upgrade get things in sync?

A better tool for identifying library packages you don't need anymore is
"deborphan".  That's both the package name and the command name.

-- 
G. Branden Robinson                |    To Republicans, limited government
Debian GNU/Linux                   |    means not assisting people they
branden@debian.org                 |    would sooner see shoveled into mass
http://people.debian.org/~branden/ |    graves.          -- Kenneth R. Kahn

Attachment: signature.asc
Description: Digital signature


Reply to: