Re: mesa: Changes to 'debian-unstable'
On 27.10.2014 04:07, Sven Joachim wrote: debian/changelog |1 + 1 file changed, 1 insertion(+) New commits: commit aad35283edff3f7a7ea9c341e60607f78dd20211 Author: Sven Joachim svenj...@gmx.de Date: Sun Oct 26 20:05:45 2014 +0100 Close bug #766058 Commit 724f71ef3905289eee7b45955243fdc7dc5f1251 fixes the corresponding freedesktop.org bug. My fix only addressed one out of several issues pointed out by #766058, and apparently it's not the cause of the crash. -- Earthling Michel Dänzer| http://www.amd.com Libre software enthusiast |Mesa and X developer -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/544eeabe.4070...@daenzer.net
Re: README.source and documentation updates (was: Re: mesa: Changes to 'debian-unstable')
On Mon, Oct 17, 2011 at 12:17:42 +0200, Andreas Beckmann wrote: commit aee32cbeae3e76bab261fc02fa5e608b71360439 Author: Cyril Brulebois k...@debian.org Date: Sat Sep 24 20:32:27 2011 +0200 Document the symlink dance in README.source. Thanks! This was giving me a headache previously. Eventually this can be extended by an example how to set up .git/gbp.conf so that it does export the git tree and run the symlink dance automatically? This works for me: I personally don't use git-buildpackage or export the tree, so I wouldn't maintain something like that. [git-buildpackage] prebuild = find -type l | while read dest; do src=$(readlink -f $dest); rm $dest; cp $src $dest; done export-dir = ../build-area/ tarball-dir = ../tarballs/ Also it would be nice if README.source would have a link to http://pkg-xorg.alioth.debian.org/ (and eventually other places with XSF packaging related information) - this probably applies to all packages managed by XSF. Makes it easier for non-XSF people to start hacking X properly :-) Yeah that's probably a good idea. Something I didn't find so far are instructions how you would like to get patches submitted. Preferrably, git-formatted patches either directly with git send-email to debian-x or through the bts (the latter is probably easier to keep track of). Some minor updates for http://wiki.debian.org/Xorg: * wheezy has xserver-xorg-core 1.11 * In the Video Drivers section, can you add a link to http://wiki.debian.org/NvidiaGraphicsDrivers? (This page mainly talks about the non-free driver). Feel free to make those changes to the wiki directly. Cheers, Julien -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111017182631.gm28...@radis.liafa.jussieu.fr
README.source and documentation updates (was: Re: mesa: Changes to 'debian-unstable')
commit aee32cbeae3e76bab261fc02fa5e608b71360439 Author: Cyril Brulebois k...@debian.org Date: Sat Sep 24 20:32:27 2011 +0200 Document the symlink dance in README.source. Thanks! This was giving me a headache previously. Eventually this can be extended by an example how to set up .git/gbp.conf so that it does export the git tree and run the symlink dance automatically? This works for me: [git-buildpackage] prebuild = find -type l | while read dest; do src=$(readlink -f $dest); rm $dest; cp $src $dest; done export-dir = ../build-area/ tarball-dir = ../tarballs/ Also it would be nice if README.source would have a link to http://pkg-xorg.alioth.debian.org/ (and eventually other places with XSF packaging related information) - this probably applies to all packages managed by XSF. Makes it easier for non-XSF people to start hacking X properly :-) Something I didn't find so far are instructions how you would like to get patches submitted. Some minor updates for http://wiki.debian.org/Xorg: * wheezy has xserver-xorg-core 1.11 * In the Video Drivers section, can you add a link to http://wiki.debian.org/NvidiaGraphicsDrivers? (This page mainly talks about the non-free driver). Andreas -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e9c00c6.6030...@abeckmann.de
Re: mesa: Changes to 'debian-unstable'
On Son, 2011-06-12 at 15:52 +, Julien Cristau wrote:
commit 3a2adc77d98d96f0144429f4a61a0209bd776a1c
Author: Julien Cristau jcris...@debian.org
Date: Sun Jun 12 17:51:59 2011 +0200
Update Breaks now that multiarch is merged; restore ${ORIGIN}/dri search
path
diff --git a/debian/control b/debian/control
index e440081..0c15837 100644
--- a/debian/control
+++ b/debian/control
@@ -454,7 +454,7 @@ Depends:
Suggests: libglide3
Conflicts: xlibmesa-dri ( 1:7.0.0)
Replaces: xlibmesa-dri ( 1:7.0.0)
-Breaks: xserver-xorg-core ( 2:1.9.99.903-3), libgl1-mesa-glx ( 7.10-6)
+Breaks: xserver-xorg-core ( 2:1.10.2-2), libgl1-mesa-glx ( 7.10.2-4)
Multi-Arch: same
Description: free implementation of the OpenGL API -- DRI modules
This version of Mesa provides GLX and DRI capabilities: it is capable of
@@ -496,7 +496,7 @@ Architecture: linux-any
Depends:
${shlibs:Depends},
${misc:Depends},
-Breaks: xserver-xorg-core ( 2:1.9.99.903-3), libgl1-mesa-glx ( 7.10-6)
+Breaks: xserver-xorg-core ( 2:1.10.2-2), libgl1-mesa-glx ( 7.10.2-4)
Technically, libgl1-mesa-glx 7.10.1-1 should be sufficient, as the
${ORIGIN}/dri search path was introduced there?
--
Earthling Michel Dänzer |http://www.vmware.com
Libre software enthusiast | Debian, X and DRI developer
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1308126533.6619.289.camel@thor.local
Re: mesa: Changes to 'debian-unstable'
On Mit, 2011-06-15 at 10:31 +0200, Julien Cristau wrote:
On Wed, Jun 15, 2011 at 10:28:52 +0200, Michel Dänzer wrote:
On Son, 2011-06-12 at 15:52 +, Julien Cristau wrote:
commit 3a2adc77d98d96f0144429f4a61a0209bd776a1c
Author: Julien Cristau jcris...@debian.org
Date: Sun Jun 12 17:51:59 2011 +0200
Update Breaks now that multiarch is merged; restore ${ORIGIN}/dri
search path
diff --git a/debian/control b/debian/control
index e440081..0c15837 100644
--- a/debian/control
+++ b/debian/control
@@ -454,7 +454,7 @@ Depends:
Suggests: libglide3
Conflicts: xlibmesa-dri ( 1:7.0.0)
Replaces: xlibmesa-dri ( 1:7.0.0)
-Breaks: xserver-xorg-core ( 2:1.9.99.903-3), libgl1-mesa-glx (
7.10-6)
+Breaks: xserver-xorg-core ( 2:1.10.2-2), libgl1-mesa-glx ( 7.10.2-4)
Multi-Arch: same
Description: free implementation of the OpenGL API -- DRI modules
This version of Mesa provides GLX and DRI capabilities: it is capable of
@@ -496,7 +496,7 @@ Architecture: linux-any
Depends:
${shlibs:Depends},
${misc:Depends},
-Breaks: xserver-xorg-core ( 2:1.9.99.903-3), libgl1-mesa-glx (
7.10-6)
+Breaks: xserver-xorg-core ( 2:1.10.2-2), libgl1-mesa-glx ( 7.10.2-4)
Technically, libgl1-mesa-glx 7.10.1-1 should be sufficient, as the
${ORIGIN}/dri search path was introduced there?
libGL 7.10.1-1 is in /usr/lib, so will look for the dri drivers in
/usr/lib/dri, not in the multiarch paths, I think?
Hmm, guess you're right. Sorry for the noise. :}
--
Earthling Michel Dänzer |http://www.vmware.com
Libre software enthusiast | Debian, X and DRI developer
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1308126929.6619.291.camel@thor.local
Re: mesa: Changes to 'debian-unstable'
On Wed, Jun 15, 2011 at 10:28:52 +0200, Michel Dänzer wrote:
On Son, 2011-06-12 at 15:52 +, Julien Cristau wrote:
commit 3a2adc77d98d96f0144429f4a61a0209bd776a1c
Author: Julien Cristau jcris...@debian.org
Date: Sun Jun 12 17:51:59 2011 +0200
Update Breaks now that multiarch is merged; restore ${ORIGIN}/dri
search path
diff --git a/debian/control b/debian/control
index e440081..0c15837 100644
--- a/debian/control
+++ b/debian/control
@@ -454,7 +454,7 @@ Depends:
Suggests: libglide3
Conflicts: xlibmesa-dri ( 1:7.0.0)
Replaces: xlibmesa-dri ( 1:7.0.0)
-Breaks: xserver-xorg-core ( 2:1.9.99.903-3), libgl1-mesa-glx ( 7.10-6)
+Breaks: xserver-xorg-core ( 2:1.10.2-2), libgl1-mesa-glx ( 7.10.2-4)
Multi-Arch: same
Description: free implementation of the OpenGL API -- DRI modules
This version of Mesa provides GLX and DRI capabilities: it is capable of
@@ -496,7 +496,7 @@ Architecture: linux-any
Depends:
${shlibs:Depends},
${misc:Depends},
-Breaks: xserver-xorg-core ( 2:1.9.99.903-3), libgl1-mesa-glx ( 7.10-6)
+Breaks: xserver-xorg-core ( 2:1.10.2-2), libgl1-mesa-glx ( 7.10.2-4)
Technically, libgl1-mesa-glx 7.10.1-1 should be sufficient, as the
${ORIGIN}/dri search path was introduced there?
libGL 7.10.1-1 is in /usr/lib, so will look for the dri drivers in
/usr/lib/dri, not in the multiarch paths, I think?
Cheers,
Julien
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110615083121.ga17...@coloquinte.cristau.org
Re: mesa: Changes to 'debian-unstable'
On Tue, 9 Dec 2008, Timo Aaltonen wrote: Rebased ref, commits from common ancestor: this was a horrible mistake due to the needed '-f' to get upstream-experimental pushed. I missed the line which said that 'debian-unstable' was rejected.. Julien hopefully has a tree which has the couple of commits on top of this.. t -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mesa: Changes to 'debian-unstable'
On Tue, 2008-06-10 at 23:25 +0200, Brice Goglin wrote: diff --git a/debian/changelog b/debian/changelog --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +mesa (7.0.3-2) UNRELEASED; urgency=low + + * Pull from mesa_7_0_branch (6f4c8b5b). + * Set right cliprects for the current draw region on Intel, closes: #467319. + * Use BRW_TEXCOORDMODE_CLAMP instead of BRW_TEXCOORDMODE_CLAMP_BORDER +to implement GL_CLAMP on i965, closes: #478880. + + -- Brice Goglin [EMAIL PROTECTED] Tue, 10 Jun 2008 23:15:21 +0200 I will upload this by the end of the week so that it can easily enter testing before the libs get frozen. Michel, since this will be the Mesa for Lenny, do you think we should cherry-pick r300: disable the lowimpact fallbacks by default? Yeah, I just cherry-picked it upstream. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mesa: Changes to 'debian-unstable'
diff --git a/debian/changelog b/debian/changelog --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +mesa (7.0.3-2) UNRELEASED; urgency=low + + * Pull from mesa_7_0_branch (6f4c8b5b). + * Set right cliprects for the current draw region on Intel, closes: #467319. + * Use BRW_TEXCOORDMODE_CLAMP instead of BRW_TEXCOORDMODE_CLAMP_BORDER +to implement GL_CLAMP on i965, closes: #478880. + + -- Brice Goglin [EMAIL PROTECTED] Tue, 10 Jun 2008 23:15:21 +0200 I will upload this by the end of the week so that it can easily enter testing before the libs get frozen. Michel, since this will be the Mesa for Lenny, do you think we should cherry-pick r300: disable the lowimpact fallbacks by default? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mesa: Changes to 'debian-unstable'
On Fri, 2007-10-05 at 18:30 -0400, David Nusinow wrote: On Fri, Oct 05, 2007 at 08:45:04AM +0200, Michel Dänzer wrote: On Fri, 2007-10-05 at 03:10 +, David Nusinow wrote: commit 76556f82646d4a0db15a06e1392e24a6457b1642 Author: David Nusinow [EMAIL PROTECTED] Date: Thu Oct 4 22:49:27 2007 -0400 * Disable building i915tex. It was previously only built on x86 and amd64. Because the hardware only physically works with those. It was never production-ready and relies on a kernel interface that never went upstream. Define 'production ready' - several customers of ours have it in production. It just requires a suitable drm snapshot. Production-ready may or may not be true (I was told it wasn't really a shippable driver by krh) but what I was told is that the kernel interface never went in upstream, which means we're not shipping it in Debian, The same is true for a couple of other drivers in libgl1-mesa-dri. and that airlied is planning to break that interface fairly soon with (I believe) superioctl. I don't understand the details, but my impression from listening to the discussion was that i915tex would be broken very soon and probably not fixed, and that it wasn't really working for us anyway. Again, it's just a matter of a suitable drm snapshot. Please re-enable i915tex or disable the other drivers with similar or worse issues as well. Thanks, -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Re: mesa: Changes to 'debian-unstable'
On Sat, Oct 06, 2007 at 12:05:19PM +0200, Michel Dänzer wrote: On Fri, 2007-10-05 at 18:30 -0400, David Nusinow wrote: On Fri, Oct 05, 2007 at 08:45:04AM +0200, Michel Dänzer wrote: On Fri, 2007-10-05 at 03:10 +, David Nusinow wrote: commit 76556f82646d4a0db15a06e1392e24a6457b1642 Author: David Nusinow [EMAIL PROTECTED] Date: Thu Oct 4 22:49:27 2007 -0400 * Disable building i915tex. It was previously only built on x86 and amd64. Because the hardware only physically works with those. It was never production-ready and relies on a kernel interface that never went upstream. Define 'production ready' - several customers of ours have it in production. It just requires a suitable drm snapshot. Production-ready may or may not be true (I was told it wasn't really a shippable driver by krh) but what I was told is that the kernel interface never went in upstream, which means we're not shipping it in Debian, The same is true for a couple of other drivers in libgl1-mesa-dri. and that airlied is planning to break that interface fairly soon with (I believe) superioctl. I don't understand the details, but my impression from listening to the discussion was that i915tex would be broken very soon and probably not fixed, and that it wasn't really working for us anyway. Again, it's just a matter of a suitable drm snapshot. Please re-enable i915tex or disable the other drivers with similar or worse issues as well. Ok, done. I didn't realize it was useful to you or anyone else at this point. Sorry about that. - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mesa: Changes to 'debian-unstable'
On Fri, 2007-10-05 at 03:10 +, David Nusinow wrote: commit 76556f82646d4a0db15a06e1392e24a6457b1642 Author: David Nusinow [EMAIL PROTECTED] Date: Thu Oct 4 22:49:27 2007 -0400 * Disable building i915tex. It was previously only built on x86 and amd64. Because the hardware only physically works with those. It was never production-ready and relies on a kernel interface that never went upstream. Define 'production ready' - several customers of ours have it in production. It just requires a suitable drm snapshot. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Re: mesa: Changes to 'debian-unstable'
On Fri, Oct 05, 2007 at 08:45:04AM +0200, Michel Dänzer wrote: On Fri, 2007-10-05 at 03:10 +, David Nusinow wrote: commit 76556f82646d4a0db15a06e1392e24a6457b1642 Author: David Nusinow [EMAIL PROTECTED] Date: Thu Oct 4 22:49:27 2007 -0400 * Disable building i915tex. It was previously only built on x86 and amd64. Because the hardware only physically works with those. It was never production-ready and relies on a kernel interface that never went upstream. Define 'production ready' - several customers of ours have it in production. It just requires a suitable drm snapshot. Production-ready may or may not be true (I was told it wasn't really a shippable driver by krh) but what I was told is that the kernel interface never went in upstream, which means we're not shipping it in Debian, and that airlied is planning to break that interface fairly soon with (I believe) superioctl. I don't understand the details, but my impression from listening to the discussion was that i915tex would be broken very soon and probably not fixed, and that it wasn't really working for us anyway. - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
