Re: xorg-x11_6.8.2.dfsg.1-2_i386.changes ACCEPTED

2005-07-13 Thread Norbert Tretkowski
* Debian Installer wrote: [...] I also updated the backport for sarge, it's now based on 6.8.2.dfsg.1-2: deb http://people.debian.org/~nobse/xorg-x11/ sarge main As usual, please don't file bugreports against these packages to the Debian BTS. Norbert -- To UNSUBSCRIBE, email to [EMAIL PROTECT

Re: xorg-x11_6.8.2.dfsg.1-2_i386.changes ACCEPTED

2005-07-13 Thread Norbert Tretkowski
* Eugene Konev wrote: > On Wed, 13 Jul 2005 12:43:29 +0200 you wrote: > > I also updated the backport for sarge, it's now based on > > 6.8.2.dfsg.1-2: > > > deb http://people.debian.org/~nobse/xorg-x11/ sarge main > > > As usual, please don't file bugreports against these packages to > > the Debi

Re: xorg-x11_6.8.2.dfsg.1-2_i386.changes ACCEPTED

2005-07-14 Thread Norbert Tretkowski
* Norbert Tretkowski wrote: > * Eugene Konev wrote: > > The problem with this packages is that they don't provide > > xlibmesa-glu anymore and that will cause major breakage on a sarge > > system. > > At least not on my system... but you're right, I'll

Re: XFree86 4.3.0 for woody

2004-03-22 Thread Norbert Tretkowski
* J M Cerqueira Esteves wrote: > On Fri, 2004-01-30 at 20:29, Norbert Tretkowski wrote: > > after a discussion with Branden on IRC last week, I decided to > > take up the woody part of our XFree86 4.3 packages. I have working > > backports (working as in "works

XFree86 4.3.0 woody backport updated

2004-05-11 Thread Norbert Tretkowski
I updated the XFree86 4.3.0 woody backport to 4.3.0.dfsg.1-1. | deb http://people.debian.org/~nobse/xfree86 woody main As usual, please to not file bugreports against this version to the Debian BTS. Regards, Norbert

Re: xfree86_4.3.0.dfsg.1-2 is too long a filename

2004-05-11 Thread Norbert Tretkowski
* Peter Constantinidis wrote: > Hi, I was poking around at: > > http://www.distrowatch.com/debian > > I see that due to the length, it trunctuates after the '1' meaning > Distrowatch will never be able to report the SID revision unless the > name is shortened, or distrowatch's columns are widened

XFree86 4.3.0 for woody

2004-01-30 Thread Norbert Tretkowski
Hi, after a discussion with Branden on IRC last week, I decided to take up the woody part of our XFree86 4.3 packages. I have working backports (working as in "works for me"), but I need some feedback. I uploaded the packages to . Yes, there's mor

Bug#231268: xbase-clients: Probably should depend on cpp, not cpp-3.2

2004-02-05 Thread Norbert Tretkowski
* Jan Hudec wrote: > The package depends on cpp-3.2. Since default compiler is gcc-3.3 and > thus default preprocessor is cpp-3.3, it keeps extra version installed > on most systems. Check the changelog: , | - Build-Depend on cpp-3.2; xbase-clients and xdm now Depend on cpp-3.2 | instead of

Re: XFree86 4.3.0 for woody

2004-02-06 Thread Norbert Tretkowski
* Tobias Hain wrote: > > Maybe there's a problem with the backward compatibility of > > freetype. > > Unfortunately there is. The KDE 3.2.0 woody backport of Ralph Nolden > conflicts here. Supporting a mixture of backports from different repositories is impossible. Norbert

XFree86 4.3.0 backports

2004-02-19 Thread Norbert Tretkowski
Hi, I updated my woody backport[0] to 4.3.0-2. Actually not worth a mail, but there was some comfusion about the versioning. The backport of 4.3.0-2 is versioned 4.3.0-1.woody.1. Q: Why not 4.3.0-2.woody.1 (so the first number in the Debian version is identical with the one from woody's packag

Re: XFree86 4.3.0 backports

2004-02-19 Thread Norbert Tretkowski
* Norbert Tretkowski wrote: > A: Because 4.3.0-2.woody.1 > 4.3.0-1.woody.1 Stupid me. That should be "4.3.0-2.woody.1 > 4.3.0-2". Norbert

Re: XFree86 4.3 in unstable

2004-02-21 Thread Norbert Tretkowski
* Antony Gelberg wrote: > Preparing to replace xserver-xfree86 4.3.0-0ds2.0.0woody2 (using > .../xserver-xfree86_4.3.0-2_i386.deb) ... > Unpacking replacement xserver-xfree86 ... > dpkg: error processing > /var/cache/apt/archives/xserver-xfree86_4.3.0-2_i386.deb (--unpack): > trying to overwrite `

Bug#304108: xserver-xfree86: Fatal server error: Caught signal 11. Server aborting

2005-04-11 Thread Norbert Tretkowski
* Kingsley G. Morse Jr. wrote: > X can be made to crash by doing the following: [...] No crash when I tried that on my sarge box. Norbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Can't compile mplayer after upgrading from xfree86 to x.org

2005-06-25 Thread Norbert Tretkowski
* Xiaoyang Gu wrote: [...] > But when using xfree86, there wasn't any errors during the > compiling. I think this is caused by the new xorg package. Install libxinerama-dev and try building mplayer again. Norbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Tr

X.org backport for sarge

2005-06-25 Thread Norbert Tretkowski
Hi, after David Nusinow's announcement of experimental X.org packages, I couldn't resist building a backport for sarge. If you want to give it a try, add this line to your sources.list: deb http://people.debian.org/~nobse/xorg-x11/ sarge main If you have problems, please don't file bugreports ag

Re: x.org experimental packages testing

2005-06-26 Thread Norbert Tretkowski
* Lionel Elie Mamane wrote: > Setting up xfree86-common (6.8.2.dfsg.1-0pre1v1) ... > update-rc.d: /etc/init.d/xfree86-common exists during rc.d purge (use -f to > force) > dpkg: error processing xfree86-common (--configure): > subprocess post-installation script returned error exit status 1