Bug#470266: pciaccess check should use >= 0.10 instead of 0.10.0 - patch
tags 470266 patch
thanks
I've made a patch that fixes the version number in the configure and
the configure.ac file.
Package now builds correctly with pbuilder.
Bye,
Emilio
--- xserver-xorg-video-i810.orig/configure.ac2008-03-14 14:09:35.0 +0100
+++ xserver-xorg-video-i810/configure.ac2008-03-14 14:10:00.0 +0100
@@ -115,9 +115,9 @@
CFLAGS="$save_CFLAGS"
if test x$XSERVER_LIBPCIACCESS = xyes; then
- PKG_CHECK_MODULES([PCIACCESS], [pciaccess >= 0.10.0])
+ PKG_CHECK_MODULES([PCIACCESS], [pciaccess >= 0.10])
else
- PKG_CHECK_MODULES([PCIACCESS], [pciaccess >= 0.10.0],
+ PKG_CHECK_MODULES([PCIACCESS], [pciaccess >= 0.10],
have_libpciaccess=yes,
have_libpciaccess=no)
fi
--- xserver-xorg-video-i810.orig/configure 2008-03-14 14:42:51.0 +0100
+++ xserver-xorg-video-i810/configure 2008-03-14 14:50:05.0 +0100
@@ -21807,12 +21807,12 @@
pkg_cv_PCIACCESS_CFLAGS="$PCIACCESS_CFLAGS"
else
if test -n "$PKG_CONFIG" && \
-{ (echo "$as_me:$LINENO: \$PKG_CONFIG --exists --print-errors \"pciaccess >= 0.10.0\"") >&5
- ($PKG_CONFIG --exists --print-errors "pciaccess >= 0.10.0") 2>&5
+{ (echo "$as_me:$LINENO: \$PKG_CONFIG --exists --print-errors \"pciaccess >= 0.10\"") >&5
+ ($PKG_CONFIG --exists --print-errors "pciaccess >= 0.10") 2>&5
ac_status=$?
echo "$as_me:$LINENO: \$? = $ac_status" >&5
(exit $ac_status); }; then
- pkg_cv_PCIACCESS_CFLAGS=`$PKG_CONFIG --cflags "pciaccess >= 0.10.0" 2>/dev/null`
+ pkg_cv_PCIACCESS_CFLAGS=`$PKG_CONFIG --cflags "pciaccess >= 0.10" 2>/dev/null`
else
pkg_failed=yes
fi
@@ -21825,12 +21825,12 @@
pkg_cv_PCIACCESS_LIBS="$PCIACCESS_LIBS"
else
if test -n "$PKG_CONFIG" && \
-{ (echo "$as_me:$LINENO: \$PKG_CONFIG --exists --print-errors \"pciaccess >= 0.10.0\"") >&5
- ($PKG_CONFIG --exists --print-errors "pciaccess >= 0.10.0") 2>&5
+{ (echo "$as_me:$LINENO: \$PKG_CONFIG --exists --print-errors \"pciaccess >= 0.10\"") >&5
+ ($PKG_CONFIG --exists --print-errors "pciaccess >= 0.10") 2>&5
ac_status=$?
echo "$as_me:$LINENO: \$? = $ac_status" >&5
(exit $ac_status); }; then
- pkg_cv_PCIACCESS_LIBS=`$PKG_CONFIG --libs "pciaccess >= 0.10.0" 2>/dev/null`
+ pkg_cv_PCIACCESS_LIBS=`$PKG_CONFIG --libs "pciaccess >= 0.10" 2>/dev/null`
else
pkg_failed=yes
fi
@@ -21849,14 +21849,14 @@
_pkg_short_errors_supported=no
fi
if test $_pkg_short_errors_supported = yes; then
- PCIACCESS_PKG_ERRORS=`$PKG_CONFIG --short-errors --errors-to-stdout --print-errors "pciaccess >= 0.10.0"`
+ PCIACCESS_PKG_ERRORS=`$PKG_CONFIG --short-errors --errors-to-stdout --print-errors "pciaccess >= 0.10"`
else
- PCIACCESS_PKG_ERRORS=`$PKG_CONFIG --errors-to-stdout --print-errors "pciaccess >= 0.10.0"`
+ PCIACCESS_PKG_ERRORS=`$PKG_CONFIG --errors-to-stdout --print-errors "pciaccess >= 0.10"`
fi
# Put the nasty error message in config.log where it belongs
echo "$PCIACCESS_PKG_ERRORS" >&5
- { { echo "$as_me:$LINENO: error: Package requirements (pciaccess >= 0.10.0) were not met:
+ { { echo "$as_me:$LINENO: error: Package requirements (pciaccess >= 0.10) were not met:
$PCIACCESS_PKG_ERRORS
@@ -21867,7 +21867,7 @@
and PCIACCESS_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
" >&5
-echo "$as_me: error: Package requirements (pciaccess >= 0.10.0) were not met:
+echo "$as_me: error: Package requirements (pciaccess >= 0.10) were not met:
$PCIACCESS_PKG_ERRORS
@@ -21919,12 +21919,12 @@
pkg_cv_PCIACCESS_CFLAGS="$PCIACCESS_CFLAGS"
else
if test -n "$PKG_CONFIG" && \
-{ (echo "$as_me:$LINENO: \$PKG_CONFIG --exists --print-errors \"pciaccess >= 0.10.0\"") >&5
- ($PKG_CONFIG --exists --print-errors "pciaccess >= 0.10.0") 2>&5
+{ (echo "$as_me:$LINENO: \$PKG_CONFIG --exists --print-errors \"pciaccess >= 0.10\"") >&5
+ ($PKG_CONFIG --exists --print-errors "pciaccess >= 0.10") 2>&5
ac_status=$?
echo "$as_me:$LINENO: \$? = $ac_status" >&5
(exit $ac_status); }; then
- pkg_cv_PCIACCESS_CFLAGS=`$PKG_CONFIG --cflags "pciaccess >= 0.10.0" 2>/dev/null`
+ pkg_cv_PCIACCESS_CFLAGS=`$PKG_CONFIG --cflags "pciaccess >= 0.10" 2>/dev/null`
else
pkg_failed=yes
fi
@@ -21937,12 +21937,12 @@
pkg_cv_PCIACCESS_LIBS="$PCIACCESS_LIBS"
else
if test -n "$PKG_CONFIG" && \
-{ (echo "$as_me:$LINENO: \$PKG_CONFIG --exists --print-errors \"pciaccess >= 0.10.0\"") >&5
- ($PKG_CONFIG --exists --print-errors "pciaccess >= 0.10.0") 2>&5
+{ (echo "$as_me:$LINENO: \$PKG_CONFIG --exists --print-errors \"pciaccess >= 0.10\"") >&5
+ ($PKG_CONFIG --exists --print-errors "pciaccess >= 0.10") 2>&5
ac_status=$?
echo "$as_me:$LINENO: \$? = $ac_status" >&5
(exit $ac_status); }; then
- pkg_cv_PCIACCESS_LIBS=`$PKG_CONFIG --libs "pciaccess >= 0.10.0" 2>/dev/null`
+ pkg_cv_PCIACCESS_LIBS=`$PKG_CONFIG --libs "pciaccess >= 0.10"
Re: compiz 0.7.0, kde4-windows-decorator
So what we can do about this? Any advice? 2008/2/11, Sune Vuorela <[EMAIL PROTECTED]>: > On 2008-02-11, emisca <[EMAIL PROTECTED]> wrote: > > I'm trying to update the compiz package, and it now includes in > > addition to the kde-windows-decorator (kde3..) a new > > kde4-windows-decorator. > > > > Now I have problems adding the build deps necessary. If I install > > kdebase-dev, I cannot install kdelibs5-dev, and kdebase5-dev. > > > > How I can manage to have both kde3 and kde4 build deps? > > you can't, as both packages contains among others /usr/lib/libkdecore.so > > /Sune > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
compiz 0.7.0, kde4-windows-decorator
I'm trying to update the compiz package, and it now includes in addition to the kde-windows-decorator (kde3..) a new kde4-windows-decorator. Now I have problems adding the build deps necessary. If I install kdebase-dev, I cannot install kdelibs5-dev, and kdebase5-dev. How I can manage to have both kde3 and kde4 build deps? Do I have to split the package, and maybe release (as kwin4 is also only in experimental) the kde4-windows-decorator on experimental? Thanks, Emilio -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: next steps for compiz -- source package reorganization
Hi Sean, here is what I think about compiz packages reorganization: Pros: - small number of packages - single uploads and queues Cons: - versioning not aligned to upstream, they often release modifications to each of these packages in a separate way. - compiz-fusion-plugins: those plugins are classified by upstream support. It would be a pain for us, supporting the "unsupported" or "extra" plugins without the upstream support... - technical issues: it's more difficult to create a packages from more than one source tree. - fusion icon, ccsm, simple-ccsm are from different upstream teams... Perhaps there is the need of metapackages to ease the installation process to final users. Emilio 2008/2/9, sean finney <[EMAIL PROTECTED]>: > hello debian-x peeps, > > i'm once again finding myself with some time to spend/kill on playing with > compiz foo in debian. > > I've summarized the next steps that i'd like to do here: > > http://wiki.debian.org/XStrikeForce/Compiz#head-26e1b15f16e4dcc647c6eb4e5752cad60c4a9ae1 > > questions/comments/feedback/etc welcome. > > (please cc me in responses, i'm not on the list) > > sean > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
upgrading compiz 0.7.0 package
As compiz 0.7.0 is out, I'm trying to update the package and help you to get it quickly... This is my first attempt: http://download.tuxfamily.org/emiscabpo/tmp/compiz_0.7.0-0~emiscabpo%2b1.diff.gz http://download.tuxfamily.org/emiscabpo/tmp/compiz_0.7.0-0~emiscabpo%2b1.dsc I tried to produce a new compiz-kde4 package, and added kdelibs5-dev build dep. I still have to try to build it... This email is mostly to notify that I'm working on it ;-) Emilio -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: fusion-icon
Hi Sean, Antonio De Luci worked on a fusion icon package. I'm ccing him so he could pass you what he did, so you can use it as a starting point. He already asked me to find a sponsor for this package, and I think he would be happy to contribute. Bye, Emilio 2008/2/7, sean finney <[EMAIL PROTECTED]>: > forcemerge 464040 461769 > thanks > > hi siegfried, > > i see you've started work on fusion-icon in the python-apps group. any reason > not to do so with the debian-x folks, where we're managing all the other > compiz/compiz-fusion stuff? > > i have plans in the pipes for fusion-icon (and other things wrt > compiz-fusion), and it would be really good if we could work together on > this. actually i seem to recall someone else already packaging fusion-icon > and needing a sponsor, but i can't seem to find it now. i'm cc'ing debian-x > just in case someone there remembers off the top of their head. > > regardless, if you have a source package needing sponsorship Right Now, i'd be > happy to do it, just point me at a .dsc for review. however, i have some > evil master plans for better management of the entire compiz-fusion forest of > git trees using git submodules, and i'd like to include fusion-icon in that > as soon as i can get this together (current timeline suggests maybe a couple > weeks to get a proposal to debian-x, and work out the kinks). > > > sean > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
compiz-manager script in compiz package
Do you have considered inclusion of the compiz-manager (http://releases.compiz-fusion.org/0.6.0/compiz-manager-0.6.0.tar.gz) in the compiz package, or as a new separate package? Emilio -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Compiz Fusion 0.6.0 and compiz 0.6.2 packages, call for review
In order to push compiz fusion 0.6.0 and compiz 0.6.2 in the official debian repository I would like if someone could review the packages I made in order to improve them. I used ubuntu's packages for compiz fusion packages and Shame (shame.tuxfamily.org) for compiz as starting point. On my blog there are instruction on how to install them: http://emiscabpo.wordpress.com/2007/10/22/compiz-fusion-060-compiz-062-for-etch/ Source packages are here: http://download.tuxfamily.org/emiscabpo/compiz-0.6.0/sources/ I've compiled, for now, these packages only against Etch using pbuilder on i386. Regards, Emilio -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xserver master branch
I've found on X mailing list, the needed patches... http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages?view=rev&revision=22174 the post is called "problem with xorg-server 1.3 and mesa 6.5.3". I'll try to patch the deb sources, and I'll tell you if it works... 2007/5/29, emisca <[EMAIL PROTECTED]>: Can you please explain me what is the situation..? I'm trying to backport to etch xorg 1.3.0-5 compiling it against mesa 6.5.3 using pbuilder. The build stops saying that it cannot found the mesa tree. Compiling it against mesa 6.5.2 works. If I install and compile mesa 6.5.3 later than xserver-xorg, will I have problems? Thanks, Emilio 2007/5/26, Michel Dänzer <[EMAIL PROTECTED]>: > On Sat, 2007-05-26 at 17:32 +1000, Drew Parsons wrote: > > Julien à ecrit: > > > I've merged our packaging in the master branch of the server, so if > > > anyone wants to get a look at it before I push it to the main repo, I've > > > made it available at > > > ssh://git.debian.org/var/lib/gforge/chroot/home/users/jcristau/xorg-server > > > > > > I've had to disable xprint to get it to build, and I've not tested > > > anything other than "it builds" with tip of the mesa master branch at > > > the time (d062b6cd2672f42fdfe20f6d932aacef9895aebc) and of pixman. > > > > Excellent, thanks for this Julien! I've been waiting for the chance to > > get at master so I can get xprint working again. > > > > What's the best way to manage mesa now? Will we just skip 6.5.3 > > entirely and jump straight to mesa head? (I understand xserver head > > does not work with mesa 6.5.3) > > Until the fine day when libGLcore can be built from the Mesa tree, I > suspect it may be better to split mesa-swx11-source off the other Mesa > packages - maybe just move it into xorg-server? > > > -- > Earthling Michel Dänzer | http://tungstengraphics.com > Libre software enthusiast | Debian, X and DRI developer > >
Re: xserver master branch
Can you please explain me what is the situation..? I'm trying to backport to etch xorg 1.3.0-5 compiling it against mesa 6.5.3 using pbuilder. The build stops saying that it cannot found the mesa tree. Compiling it against mesa 6.5.2 works. If I install and compile mesa 6.5.3 later than xserver-xorg, will I have problems? Thanks, Emilio 2007/5/26, Michel Dänzer <[EMAIL PROTECTED]>: On Sat, 2007-05-26 at 17:32 +1000, Drew Parsons wrote: > Julien à ecrit: > > I've merged our packaging in the master branch of the server, so if > > anyone wants to get a look at it before I push it to the main repo, I've > > made it available at > > ssh://git.debian.org/var/lib/gforge/chroot/home/users/jcristau/xorg-server > > > > I've had to disable xprint to get it to build, and I've not tested > > anything other than "it builds" with tip of the mesa master branch at > > the time (d062b6cd2672f42fdfe20f6d932aacef9895aebc) and of pixman. > > Excellent, thanks for this Julien! I've been waiting for the chance to > get at master so I can get xprint working again. > > What's the best way to manage mesa now? Will we just skip 6.5.3 > entirely and jump straight to mesa head? (I understand xserver head > does not work with mesa 6.5.3) Until the fine day when libGLcore can be built from the Mesa tree, I suspect it may be better to split mesa-swx11-source off the other Mesa packages - maybe just move it into xorg-server? -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Re: compiz: Changes to 'debian-experimental'
So there are no plans to build the 0.4 branch? 2007/4/21, Brice Goglin <[EMAIL PROTECTED]>: emisca wrote: > Where is it? > Do the compiz 0.4 (stable) version will be built? I would like to > backport it to debian Etch... Right now, compiz is in our git repo, with 0.3.6 in the debian-unstable branch and 0.5.0 in the debian-experimental branch. So if you want 0.5.0, just do: git clone git://git.debian.org/git/pkg-xorg/app/compiz.git cd compiz git-checkout -b debian-experimental origin/debian-experimental and pass -i.git to dpkg-buildpackage when building Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: compiz: Changes to 'debian-experimental'
Where is it? Do the compiz 0.4 (stable) version will be built? I would like to backport it to debian Etch... Thanks 2007/4/19, Thierry Reding <[EMAIL PROTECTED]>: debian/changelog|6 -- debian/compiz.links |1 + 2 files changed, 5 insertions(+), 2 deletions(-) New commits: commit ead4d366bc6fdf7064a8163e42835953aa7807e3 Author: Thierry Reding <[EMAIL PROTECTED]> Date: Thu Apr 19 18:22:29 2007 +0200 Add symlink to the compiz-core README.Debian to the compiz package. diff --git a/debian/changelog b/debian/changelog index ec53c67..44e70c0 100644 --- a/debian/changelog +++ b/debian/changelog @@ -18,8 +18,10 @@ compiz (0.5.0-1) UNRELEASED; urgency=low * Add build-dependency on libfuse-dev needed by the fuse plugin. * No longer conflict with metacity >= 2.15.21, now that metacity 2.18 is in unstable. (Closes: #411012) + * Add symlink to the compiz-core README to the compiz package. +(Closes: #408605) - -- Thierry Reding <[EMAIL PROTECTED]> Thu, 19 Apr 2007 17:33:10 +0200 + -- Thierry Reding <[EMAIL PROTECTED]> Thu, 19 Apr 2007 17:44:56 +0200 compiz (0.3.6-1) experimental; urgency=low diff --git a/debian/compiz.links b/debian/compiz.links new file mode 100644 index 000..0353d95 --- /dev/null +++ b/debian/compiz.links @@ -0,0 +1 @@ +/usr/share/doc/compiz-core/README.Debian /usr/share/doc/compiz/README.Debian commit 35e885efd05e869c4f868a6edd70dff2764f1fd0 Author: Thierry Reding <[EMAIL PROTECTED]> Date: Thu Apr 19 17:34:55 2007 +0200 Add closer for bug #411012. Thanks Brice. diff --git a/debian/changelog b/debian/changelog index 90aea8f..ec53c67 100644 --- a/debian/changelog +++ b/debian/changelog @@ -17,9 +17,9 @@ compiz (0.5.0-1) UNRELEASED; urgency=low * Use compiz' default set of plugins. * Add build-dependency on libfuse-dev needed by the fuse plugin. * No longer conflict with metacity >= 2.15.21, now that metacity 2.18 is in -unstable. +unstable. (Closes: #411012) - -- Thierry Reding <[EMAIL PROTECTED]> Thu, 05 Apr 2007 18:22:10 +0200 + -- Thierry Reding <[EMAIL PROTECTED]> Thu, 19 Apr 2007 17:33:10 +0200 compiz (0.3.6-1) experimental; urgency=low -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
debian-x@lists.debian.org
You should only run: sudo /usr/share/bug/xserver-xorg-core/script or instead: sudo /usr/share/bug/xserver-xorg-core/script > nomefile if you want to save the output on a file... 2007/4/21, Joshua Dunamis - <[EMAIL PROTECTED]>: Excuse me, I don't know how to run it. If I try with sh this is the output: [EMAIL PROTECTED]:~$ sudo /usr/share/bug/xserver-xorg-core/script 3>&1 /usr/share/bug/xserver-xorg-core/script: line 16: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 17: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 22: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 31: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 37: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 38: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 39: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 40: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 53: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 56: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 57: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 62: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 65: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 66: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 67: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 72: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 80: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 86: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 87: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 88: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 89: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 90: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 91: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 92: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 97: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 102: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 103: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 104: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 107: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 108: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 109: 3: Descrittore di file non valido /usr/share/bug/xserver-xorg-core/script: line 118: 3: Descrittore di file non valido On Friday 20 April 2007, alle 20:26, Julien Cristau wrote: > Subject: Re: Bug#420177: libdrm2: the output of my /usr/share/bug/xserver-xorg-core/script 3>&1 > From: Julien Cristau <[EMAIL PROTECTED]> > Date: Fri, 20 Apr 2007 20:26:23 +0200 > To: Joshua Dunamis <[EMAIL PROTECTED]>, [EMAIL PROTECTED] > X-Operating-System: Linux 2.6.18-4-686 i686 > User-Agent: Mutt/1.5.13 (2006-08-11) > > On Fri, Apr 20, 2007 at 20:15:39 +0200, Joshua Dunamis wrote: > > > Package: libdrm2 > > Version: 2.3.0-4 > > Followup-For: Bug #420177 > > > > > > As requested I put the output of my > > /usr/share/bug/xserver-xorg-core/script 3>&1 > > > What you sent is actually the *contents* of this file. You need to run > this script, and it will output your X config and log, which is the > information we need. > > Thanks, > Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: backporting xserver-xorg-video-intel 1.9.94 + xorg 1.3rc5, usage report
I still have to test well xrandr 1.2 and gnome. For now I tested only KDE 3.5.6, and I noticed crashes, strange window movements, mad panels, when I activated a second screen on the fly. I've seen the soc ideas pages for both gnome and xorg, there is a lot of work to do. I can confirm that the monitor doesn't power on when it's powered off by dpms, like with 1.7.2 driver version, and that's good! 2007/4/10, Brice Goglin <[EMAIL PROTECTED]>: emisca wrote: > xrandr 1.2 is really a dream that become true... but perhaps there is > no application support by gnome and kde. The geometry of X changes but > the window manager doesn't read the changes or it's not notified. Do > you know if there are workarounds for this? I have been running Gnome 2.14 (the one in Etch) on top of the Xorg packages from Debian/experimental on a i945 chipset for a while. Resizing or rotating XRandR 1.2 works very well and Gnome's behavior is fine. The only problem I remember of is about rotation with XRandR 1.1 (https://bugs.freedesktop.org/show_bug.cgi?id=9973) but I don't think it's related to Gnome. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: backporting xserver-xorg-video-intel 1.9.94 + xorg 1.3rc5, usage report
This is a list of what I've backported and its compilation order: xcb-proto libpthread-stubs0-dev libxcb xtrans x11proto-core x11proto-input x11proto-randr x11proto-damage x11proto-gl libxrandr xbase-clients libdrm mesa xorg-server The packages I've updated are: libdrm2 libgl1-mesa-dev libgl1-mesa-dri libgl1-mesa-glx libglu1-mesa libglu1-mesa-dev libxrandr-dev libxrandr2 mesa-common-dev mesa-utils x11proto-core-dev x11proto-input-dev x11proto-randr-dev xbase-clients xserver-xorg-core xserver-xorg-video-i810 xtrans-dev It works.. these things are relatively new. It seems I have not dpms problems anymore with my lcd screen :-D xrandr 1.2 is really a dream that become true... but perhaps there is no application support by gnome and kde. The geometry of X changes but the window manager doesn't read the changes or it's not notified. Do you know if there are workarounds for this? Opengl performance is the same, using the legacy driver. I've not tried the new i915_tex driver as is still young and unstable and needs newer drm and agpgart kernel modules. I've not seen AIGLX improvements. The overlays (video and gl apps) still don't work well, especially simple glut applications. Is there any work in progress to solve this? Intel EXA acceleration is very slow compared to XAA, and I can often notice some artifacts when windows are resized (using kwin 3.5.6). Using a compositing manager (beryl 0.2.0, compiz 0.3.6) the performance are still slow, compared to XAA. In conclusion I've seen many and many improvements in xorg development in the last year, thanks to everybody who contributed, good job!! Bye, Emilio 2007/4/10, emisca <[EMAIL PROTECTED]>: But if I want to do a complete Xorg 7.3 backport.. is there any compilation order in addition to what we said? 2007/4/10, emisca <[EMAIL PROTECTED]>: > Thanks, I'll try to build it, and I'll report if it works... > > 2007/4/10, Julien Cristau <[EMAIL PROTECTED]>: > > On Tue, Apr 10, 2007 at 00:20:53 +0200, emisca wrote: > > > > > I would like to backport using pbuilder the new 2.0rc intel driver > > > that it's present in the experimental branch of debian. > > > > For what distribution are you trying to backport it? Assuming you mean > > etch for now... > > > > > Could anyone explain me which is the correct chain of dependencies to > > > have a well compiled xorg 1.2.99 server + mesa 6.5.2 + > > > xserver-xorg-video-intel 1.9.94? > > > > > > I think it should be, please correct me if I'm wrong: > > > - libdrm 2.3 > > > - mesa 6.5.2 > > > - xorg-core 1.2.99 > > > - xserver-xorg-video-intel 1.9.94 > > > > > You need x11proto-randr and x11proto-damage somewhere before the server. > > > > > Is there any way to compile it against etch's xorg 7.1? > > > > > I'm not sure. The needed files from the server sources are present in > > the xf86-video-intel tarballs, so it might just work. It's probably not > > very well tested though, so if you run into problems you might want to > > report them on [EMAIL PROTECTED] > > > > > If I want to have the new randr 1.2 support, what libs are needed > > > (perhaps in addition to libxrandr)? > > > > > libXrandr is only needed for the xrandr command-line client (included in > > xbase-clients in Debian), IIRC. > > > > > Is there a list of the correct building order of the complete new > > > modular xorg present in experimental? I've seen that there are many > > > libs, and it's very difficult to manually build a dependency list.. > > > > > Not that I know of. Most of the libs didn't have any big changes > > though, so libdrm+mesa+libXrandr might be sufficient. > > > > Cheers, > > Julien > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: backporting xserver-xorg-video-intel 1.9.94
But if I want to do a complete Xorg 7.3 backport.. is there any compilation order in addition to what we said? 2007/4/10, emisca <[EMAIL PROTECTED]>: Thanks, I'll try to build it, and I'll report if it works... 2007/4/10, Julien Cristau <[EMAIL PROTECTED]>: > On Tue, Apr 10, 2007 at 00:20:53 +0200, emisca wrote: > > > I would like to backport using pbuilder the new 2.0rc intel driver > > that it's present in the experimental branch of debian. > > For what distribution are you trying to backport it? Assuming you mean > etch for now... > > > Could anyone explain me which is the correct chain of dependencies to > > have a well compiled xorg 1.2.99 server + mesa 6.5.2 + > > xserver-xorg-video-intel 1.9.94? > > > > I think it should be, please correct me if I'm wrong: > > - libdrm 2.3 > > - mesa 6.5.2 > > - xorg-core 1.2.99 > > - xserver-xorg-video-intel 1.9.94 > > > You need x11proto-randr and x11proto-damage somewhere before the server. > > > Is there any way to compile it against etch's xorg 7.1? > > > I'm not sure. The needed files from the server sources are present in > the xf86-video-intel tarballs, so it might just work. It's probably not > very well tested though, so if you run into problems you might want to > report them on [EMAIL PROTECTED] > > > If I want to have the new randr 1.2 support, what libs are needed > > (perhaps in addition to libxrandr)? > > > libXrandr is only needed for the xrandr command-line client (included in > xbase-clients in Debian), IIRC. > > > Is there a list of the correct building order of the complete new > > modular xorg present in experimental? I've seen that there are many > > libs, and it's very difficult to manually build a dependency list.. > > > Not that I know of. Most of the libs didn't have any big changes > though, so libdrm+mesa+libXrandr might be sufficient. > > Cheers, > Julien > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: backporting xserver-xorg-video-intel 1.9.94
Thanks, I'll try to build it, and I'll report if it works... 2007/4/10, Julien Cristau <[EMAIL PROTECTED]>: On Tue, Apr 10, 2007 at 00:20:53 +0200, emisca wrote: > I would like to backport using pbuilder the new 2.0rc intel driver > that it's present in the experimental branch of debian. For what distribution are you trying to backport it? Assuming you mean etch for now... > Could anyone explain me which is the correct chain of dependencies to > have a well compiled xorg 1.2.99 server + mesa 6.5.2 + > xserver-xorg-video-intel 1.9.94? > > I think it should be, please correct me if I'm wrong: > - libdrm 2.3 > - mesa 6.5.2 > - xorg-core 1.2.99 > - xserver-xorg-video-intel 1.9.94 > You need x11proto-randr and x11proto-damage somewhere before the server. > Is there any way to compile it against etch's xorg 7.1? > I'm not sure. The needed files from the server sources are present in the xf86-video-intel tarballs, so it might just work. It's probably not very well tested though, so if you run into problems you might want to report them on [EMAIL PROTECTED] > If I want to have the new randr 1.2 support, what libs are needed > (perhaps in addition to libxrandr)? > libXrandr is only needed for the xrandr command-line client (included in xbase-clients in Debian), IIRC. > Is there a list of the correct building order of the complete new > modular xorg present in experimental? I've seen that there are many > libs, and it's very difficult to manually build a dependency list.. > Not that I know of. Most of the libs didn't have any big changes though, so libdrm+mesa+libXrandr might be sufficient. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
backporting xserver-xorg-video-intel 1.9.94
I would like to backport using pbuilder the new 2.0rc intel driver that it's present in the experimental branch of debian. Could anyone explain me which is the correct chain of dependencies to have a well compiled xorg 1.2.99 server + mesa 6.5.2 + xserver-xorg-video-intel 1.9.94? I think it should be, please correct me if I'm wrong: - libdrm 2.3 - mesa 6.5.2 - xorg-core 1.2.99 - xserver-xorg-video-intel 1.9.94 Is there any way to compile it against etch's xorg 7.1? If I want to have the new randr 1.2 support, what libs are needed (perhaps in addition to libxrandr)? Is there a list of the correct building order of the complete new modular xorg present in experimental? I've seen that there are many libs, and it's very difficult to manually build a dependency list.. Thanks, Emilio Scalise -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#390359: xserver-xorg-video-i810: dual head config
This problem is fixed by a simple patch included in version 1.7.4 of the driver. Look at http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-intel.git;a=commit;h=33c0fac6d63d9a509a24c7a5e5a46a0d6ee4dc5d and bug #8536 in freedesktop bugzilla. Please include this and if it's right, merge these bugs. I've attached the patch against debian xserver-xorg-video-i810-1.7.2-3. From: Alan Hourihane <[EMAIL PROTECTED]> Date: Tue, 9 Jan 2007 14:02:47 + (+) Subject: Fix bug #8536, i915 BIOS fails when restarting Xserver. X-Git-Tag: xf86-video-i810-1.7.4 / xf86-video-intel-1.7.4 X-Git-Url: http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-intel.git;a=commitdiff;h=33c0fac6d63d9a509a24c7a5e5a46a0d6ee4dc5d Fix bug #8536, i915 BIOS fails when restarting Xserver. --- --- a/src/i830_driver.c +++ b/src/i830_driver.c @@ -6985,7 +6985,7 @@ IntelEmitInvarientState(ScrnInfoPtr pScr I830Ptr pI830 = I830PTR(pScrn); CARD32 ctx_addr; - if (pI830->noAccel) + if (pI830->noAccel || !I830IsPrimary(pScrn)) return; ctx_addr = pI830->ContextMem.Start;
