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

Bug#671086: marked as done (libgl1-mesa-glx: Cannot install both libgl1-mesa-swx11 and libgl1-mesa-glx)



Your message dated Tue, 1 May 2012 22:16:00 +0200
with message-id <20120501201600.GV31090@radis.cristau.org>
and subject line Re: Bug#671086: libgl1-mesa-glx: Cannot install both libgl1-mesa-swx11 and libgl1-mesa-glx
has caused the Debian Bug report #671086,
regarding libgl1-mesa-glx: Cannot install both libgl1-mesa-swx11 and libgl1-mesa-glx
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
671086: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671086
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libgl1-mesa-glx
Version: 7.11.2-1
Severity: important

Hi,

I used to install both the software and the DRI implementation of Mesa.

This allows to test an application with the DRI implementation by default,
and switch to software implementation, which is particularly useful when
debugging low-level OpenGL code, using:

  LIBGL_ALWAYS_SOFTWARE=1 ./myapp


Today, both libgl1-mesa-swx11 and libgl1-mesa-glx provide and conflict with
libgl1.  This means I have to remove -glx to install -swx11 and vice-versa.

Can these two libraries be installable in parallel?


Thanks!
Sylvain



--- End Message ---
--- Begin Message ---
On Tue, May  1, 2012 at 21:54:20 +0200, Sylvain wrote:

> reopen 671086
> thanks
> 
> Hi,
> 
> I do not understand the regression.  This was possible last year.
> Plus, what's the point of LIBGL_ALWAYS_SOFTWARE if the software driver
> cannot be installed in parallel?
> 
It's not a regression, and has nothing to do with LIBGL_ALWAYS_SOFTWARE.
Don't reopen this non-bug.

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply to: