On Thu, Jan 06, 2000 at 09:34:48PM -0800, Ben Gertzfield wrote: > Joseph> I'm sorry but not letting Mesa 3.1 get into potato now > Joseph> REALLY steps on my toes and I will be very unhappy if my > Joseph> free quake packages get pulled for unresolvable > Joseph> dependencies. > > Joseph, I'm not trying to step on your toes here! I agree that Mesa > 3.1 should get into the archives -- but I'm just trying (like you) to > say that it should NOT replace Mesa 3.0. Actually, I think it should.. Probably not as the package stands right now though. For backwards compatibility ot needs to have a libMesaGL.so.3 symlink... As for the problem you outlined, I'll try to fix it if you can provide me with a fairly simple piece of code which will seg under 3.1 but works under 3.0... If it's been fixed in 3.2 I'll be happy to backport a fix or at the very least try to isolate the problem with it. Everybody knows by now QuakeForge in general has certainly been doing enough code merging and by now we ALL have plenty of experience tracking down random segaults. =p -- Joseph Carter <email@example.com> Debian Linux developer http://tank.debian.net GnuPG key pub 1024D/DCF9DAB3 sub 2048g/3F9C2A43 http://www.debian.org 20F6 2261 F185 7A3E 79FC 44F9 8FF7 D7A3 DCF9 DAB3 Red Hat has recently released a Security Advisory (RHSA-1999:030-01) covering a buffer overflow in the vixie cron package. Debian has discovered this bug two years ago and fixed it. Therefore versions in both, the stable and the unstable, distributions of Debian are not vulnerable to this problem..
Description: PGP signature