Title: u9KZIx7i
without any Debian-x VKo and when it oJgVA
CCgw I wish E Debian-x ok deal wubOR
On Wed, Aug 27, 2003 at 08:13:45PM +0200, Eduard Bloch wrote:
> if /proc mounted:
> if /proc/fb exists:
> if(driver-listed-there matches choosen video card):
> preset use_fbdev to true
> preset priority to low
> else
> preset use_fbdev to false
> preset priority to
Package: xserver-xfree86
Version: 4.2.1-10
Aside from all the 4.2.1-10 nonsense with the XF86Config-4 changes (ugg,
what a pain) now I'm getting this:
Fatal server error:
Cannot open log file "/var/log/XFree86.0.log"
When reporting blah blah blah
Yes, I've tried 'touch'
/var is not full
the fi
retitle 207537 xserver-xfree86: want way to override configured debconf values
with autodetected ones
severity 207537 wishlist
thanks
On Wed, Aug 27, 2003 at 08:37:08PM +0200, Goswin Brederlow wrote:
> despite what you told me on irc before ignoring me none of the
> autodetection works. The reaso
Author: branden
Date: 2003-08-27 21:31:07 -0500 (Wed, 27 Aug 2003)
New Revision: 450
Modified:
trunk/debian/changelog
Log:
debian/changelog: add more justification for release urgency
Modified: trunk/debian/changelog
===
--- trun
I have bad news regarding this bug.
LaMont and I have worked on this (LaMont did the hard part; I just
diagnosed the failures), and determined that it is not possible to
straightforwardly binary-NMU xfree86 4.2.1-6 to fix this problem on
HPPA.
The reason is that at the time 4.2.1-6 was released,
Processing commands for [EMAIL PROTECTED]:
> retitle 207537 xserver-xfree86: want way to override configured debconf
> values with autodetected ones
Bug#207537: xserver-xfree86: autodetection is not used
Changed Bug title.
> severity 207537 wishlist
Bug#207537: xserver-xfree86: want way to overr
Your message dated Wed, 27 Aug 2003 21:12:12 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#207539: Bug report
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibil
Author: branden
Date: 2003-08-27 22:19:37 -0500 (Wed, 27 Aug 2003)
New Revision: 451
Modified:
trunk/debian/changelog
trunk/debian/xserver-common.postrm.in
trunk/debian/xserver-xfree86.postrm.in
Log:
debian/xserver-{common,xfree86}.postrm.in: further robustify purge procedure;
don't fai
Processing commands for [EMAIL PROTECTED]:
> retitle 207575 xserver-xfree86: X server cannot open log file
Bug#207575: xserver-xfree86 4.2.1-10 XF86Config-4 and XFree86.0.log error
Changed Bug title.
> tag 207575 + moreinfo
Bug#207575: xserver-xfree86: X server cannot open log file
There were no
Your message dated Wed, 27 Aug 2003 21:52:12 -0500
with message-id <[EMAIL PROTECTED]>
and subject line [xdm]: 4.1.x makes ia64 go boom
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your re
On Wed, Aug 27, 2003 at 09:57:20PM +0200, Andreas Schuldei wrote:
> this patch makes it possibel to select which busid the xserver
> should operate on. this is handy if two or more graphic cards in
> a box run independent xservers and need to reset the card
> independently from the other xserver. t
On Wed, Aug 27, 2003 at 09:27:45PM -0500, Branden Robinson wrote:
...
> My feeling is that our efforts are best spent on getting a newer 4.2.1
> package into testing at this point.
Agreed.
I've placed a full set of "hand crafted" 4.2.1-9 hppa debs on:
http://gsyprf11.external.hp.com/hppa/
101 - 113 of 113 matches
Mail list logo
