Dear X devs,

would it be possible to somehow bind libgl1-mesa-glx more strongly to
recent versions of libgl1-mesa-dri in order to avoid the problems that
such partial upgrades cause, e.g. as described in #676942 (see below)?

Currently, libgl1-mesa-dri has "Recommends: libgl1-mesa-dri (>= 7.2)"
and "Conflicts: libgl1, libgl1-mesa-dri (<< 6.4.0)". Since versioned
Recommends are moot, maybe this should get replaced with "Recommends:
libgl1-mesa-dri" and "Conflicts: libgl1, libgl1-mesa-dri (<< 8.0.0)".

Cheers,
Fabian

Am 14.06.2012 11:37, schrieb Toni Mueller:

Not unless I understand what the problem there is.  It's not clear to me
from the bug log.

Cheers,
Julien

I don't think #676942 was actually a partial upgrade. Toni's initial
report said that libgl1-mesa-glx 7.11.2-1 was installed, and the message
about it being fixed by upgrading Mesa said "after upgrading
libgl1-mesa-dri from 7.11.2-1 to 8.0.3-1". So when the bug was visible
(ioquake3 having "GL_RENDERER: Software Rasterizer" and a low framerate
as a result), both were in sync, at 7.11.2-1?

Perhaps I should make ioquake3 redundantly Recommend libgl1-mesa-dri,
instead of having it installed via libgl1-mesa-glx's recommendation -
then we'd get the -dri version in ioquake3 and openarena bug reports. I
suspect ioquake3 is basically unplayable in software rendering anyway.

    S

Hi,

yes. Now they are out of sync, with libgl1-mesa-dri being at 8.0.3-1,
while libgl1-mesa-glx is still at 7.11.2-1. I wondered whether I should
upgrade that lib as well.

Maybe - I have 6027.00 BogoMIPS, and it is unplayable.


Kind regards,
--Toni++

Am 14.06.2012 12:36, schrieb Simon McVittie:
libgl1-mesa-dri" to debian/ioquake3{,-server}.bug-control.

  - Fabian