On Sun, Apr 13, 2003 at 04:41:43PM +0200, Joerg Sommer wrote: > Daniel Stone schrieb am Sun 13. Apr, 10:29 (+1000) : > > xlibmesa3-glu declares a Conflicts: with the libglu1 virtual package. If > > libutahglx1 doesn't provide this, it's a problem with libutahglx1. If > > /usr/lib/libGLU.so.1 is provided by three packages: libglu1-mesa, > xlibmesa3-glu, libutahglx1 > http://packages.debian.org/cgi-bin/search_contents.pl?word=%2Fusr%2Flib%2FlibGLU.so.1&searchmode=searchfiles&case=insensitive&version=unstable&arch=i386&directories=yes > > libglu1-mesa provides libglu1 and conflicts with xlibmesa3, libglu1 > xlibmesa3-glu provides libglu1 and conflicts with libglu1 > libutahglx1 provides libgl1 and conflics with libgl1 > > Maybe there is a naming fault because libglu1 and libgl1 sound very > similar. There is no naming fault. libGL and libGLU are entirely separate libraries. > For example, blender depends on libgl1 and libglu1 which brings this > conflict up. But libglu1 couldn't exclude libgl1, because blender wants > both. > > I don't know what to do at this point. Well, libutahglx1 provides an implementation of GLU. So does xlibmesa3-glu. You just have to pick one. -- Daniel Stone <dstone@trinity.unimelb.edu.au> Developer, Trinity College, University of Melbourne
Attachment:
pgpAMsgb7jNb2.pgp
Description: PGP signature