Bug#894076: Can't include GL and GLES headers simultaneously on non-64 bit architectures

2018-04-04 Thread Sebastian Dröge
On Thu, 2018-03-29 at 12:45 +0300, Sebastian Dröge wrote: > On Thu, 2018-03-29 at 10:54 +0200, Julien Cristau wrote: > > > > I expect we'll get a fix from upstream when that happens. > > What would you suggest for the time being? This sounds like it's > going

Bug#894076: Can't include GL and GLES headers simultaneously on non-64 bit architectures

2018-03-29 Thread Sebastian Dröge
On Thu, 2018-03-29 at 10:54 +0200, Julien Cristau wrote: > > I expect we'll get a fix from upstream when that happens. What would you suggest for the time being? This sounds like it's going to take a while. The simplest workaround on my side would probably be to just not build the Qt/QML GStream

Bug#894076: Can't include GL and GLES headers simultaneously on non-64 bit architectures

2018-03-29 Thread Sebastian Dröge
On Mon, 2018-03-26 at 20:37 +0300, Sebastian Dröge wrote: > On Mon, 2018-03-26 at 19:03 +0200, Julien Cristau wrote: > > Control: severity -1 normal > > Control: tag -1 upstream > > > > On 03/26/2018 10:01 AM, Sebastian Dröge wrote: > > > Package: mesa &g

Bug#894076: Can't include GL and GLES headers simultaneously on non-64 bit architectures

2018-03-26 Thread Sebastian Dröge
On Mon, 2018-03-26 at 19:03 +0200, Julien Cristau wrote: > Control: severity -1 normal > Control: tag -1 upstream > > On 03/26/2018 10:01 AM, Sebastian Dröge wrote: > > Package: mesa > > Version: 17.3.7-1 > > Severity: serious > > Forwarded: https://bugs.fr

Bug#894076: Can't include GL and GLES headers simultaneously on non-64 bit architectures

2018-03-26 Thread Sebastian Dröge
Package: mesa Version: 17.3.7-1 Severity: serious Forwarded: https://bugs.freedesktop.org/show_bug.cgi?id=105328 Hi, Currently it's impossible to include the GL and GLES headers simultaneously on non-64 bit architectures, see e.g. https://buildd.debian.org/status/fetch.php?pkg=gst-plugins-good

Bug#666564: Incorrect version reported.

2012-04-01 Thread Sebastian Dröge
forwarded 666564 https://bugs.freedesktop.org/show_bug.cgi?id=47266 reassign 666564 xorg-server 2:1.11.4-1 severity 666564 grave forcemerge 666468 666564 thanks On Sa, 2012-03-31 at 17:16 -0400, Douglas Calvert wrote: > I filed this bug against the wrong version. The bug exists in 1.12.0-2. > > 1

Bug#666538: libcairo2: text rendering broken with cairo 1.12

2012-04-01 Thread Sebastian Dröge
forwarded 666538 https://bugs.freedesktop.org/show_bug.cgi?id=47266 reassign 666538 xorg-server 2:1.11.4-1 severity 666538 grave forcemerge 666468 666538 thanks On So, 2012-04-01 at 12:36 +0930, Arthur Marsh wrote: > Package: libcairo2:amd64 > Followup-For: Bug #666538 > > Hi, I also observed the

Bug#548846: Crashes at startup after upgrade from 1.6.3.901 to 1.6.4

2009-09-28 Thread Sebastian Dröge
Package: xserver-xorg-core Version: 1.6.4 Hi, after upgrade of xserver-xorg-core to 1.6.4 from 1.6.3.901 I get crashes on startup. Log file with stacktrace is attached. An upgrade of the intel driver from 2:2.8.1-2 to 2:2.8.99.902-1 (the experimental version) fixed it. X.Org X Server 1.6.4 Relea

Bug#546849: New upstream version 0.16.0

2009-09-15 Thread Sebastian Dröge
Package: pixman Severity: wishlist Hi, it would be nice if you could package pixman 0.16.0 for experimental :) signature.asc Description: Dies ist ein digital signierter Nachrichtenteil

Bug#465554: Please package 7.1 snapshot for experimental

2008-02-14 Thread Sebastian Dröge
Am Mittwoch, den 13.02.2008, 10:31 + schrieb Michel Dänzer: > On Wed, 2008-02-13 at 08:48 +0100, Sebastian Dröge wrote: > > Package: mesa > > Severity: wishlist > > > > Hi, > > it would be nice if you could package a mesa 7.1 snapshot for > > experimen

Bug#465554: Please package 7.1 snapshot for experimental

2008-02-13 Thread Sebastian Dröge
Package: mesa Severity: wishlist Hi, it would be nice if you could package a mesa 7.1 snapshot for experimental. This version is needed for the new GStreamer opengl plugins. Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTE