On Sun, Apr 16, 2006 at 07:31:30PM -0700, Steve Langasek wrote:
On Mon, Apr 17, 2006 at 03:25:55AM +0100, Stephen Gran wrote:
Did discover change behavior recently?
Nope -- but xserver-xorg did, by just changing to accept discover as an
(apparently untested) alternative to discover1.
Well,
On Mon, Apr 17, 2006 at 10:55:27AM +0200, Daniele Venzano wrote:
On Sun, Apr 16, 2006 at 07:31:30PM -0700, Steve Langasek wrote:
On Mon, Apr 17, 2006 at 03:25:55AM +0100, Stephen Gran wrote:
Did discover change behavior recently?
Nope -- but xserver-xorg did, by just changing to accept
Package: xserver-xorg
Version: 1:7.0.12
Severity: grave
Justification: renders package unusable
Package xserver-xorg fails to install on my system with the following
messages:
Setting up xserver-xorg (7.0.12) ...
dpkg: error processing xserver-xorg (--configure):
subprocess post-installation
On Sun, Apr 16, 2006 at 11:26:40AM +0200, Daniele Venzano wrote:
Package xserver-xorg fails to install on my system with the following
messages:
Setting up xserver-xorg (7.0.12) ...
dpkg: error processing xserver-xorg (--configure):
subprocess post-installation script returned error exit
This one time, at band camp, Steve Langasek said:
On Sun, Apr 16, 2006 at 11:26:40AM +0200, Daniele Venzano wrote:
Package xserver-xorg fails to install on my system with the following
messages:
Setting up xserver-xorg (7.0.12) ...
dpkg: error processing xserver-xorg (--configure):
On Mon, Apr 17, 2006 at 01:15:03AM +0100, Stephen Gran wrote:
This one time, at band camp, Steve Langasek said:
On Sun, Apr 16, 2006 at 11:26:40AM +0200, Daniele Venzano wrote:
Package xserver-xorg fails to install on my system with the following
messages:
Setting up xserver-xorg
This one time, at band camp, Steve Langasek said:
On Mon, Apr 17, 2006 at 01:15:03AM +0100, Stephen Gran wrote:
I just ran across this and tried that - it dies right after sourcing the
debconf confmodule - debconf's exec line to restart the scripts exit's
64.
Thanks, that's pretty much
This one time, at band camp, Steve Langasek said:
- (to the maintainers) is there anything new in the templates that could
cause a parse failure?
Here is what I see after much beating to get sensible sh -x output:
+ which discover
++ discover_video
++ which discover
+++ discover
On Mon, Apr 17, 2006 at 03:25:55AM +0100, Stephen Gran wrote:
[EMAIL PROTECTED]:~$ sudo discover --disable-all --enable=pci --format=%V
%M\t%S\t%D\n video
discover: unrecognized option `--disable-all'
usage: discover [--bus-summary] [OPTIONS] [BUS [...]]
discover --type-summary
9 matches
Mail list logo