Bug#646704: Bug severity is too high

2012-12-29 Thread Christian PERRIER
Quoting Christian PERRIER (bubu...@debian.org): > release and that it's not planned to happen in 2012, I'll be fine with s/2012/2014 signature.asc Description: Digital signature

Bug#646704: Bug severity is too high

2012-12-29 Thread Christian PERRIER
Quoting Daniel Baumann (daniel.baum...@progress-technologies.net): > since you put yourself into uploaders of live-installer some time ago, > maybe you want to look at it yourself too? You know the reasons for this: be able to do l10n upload when needed without them to be considered NMUs. That's

Re: Bug#695328: [testing/wheezy] UEFI installed system fails to boot

2012-12-29 Thread Kenyon Ralph
On 2012-12-29T19:25:59-0800, Kenyon Ralph wrote: > I have a feeling that using grub2 2.00 (like Ubuntu uses) would work. > I'll try to build an installer including that if I can figure it out. Instead of building a new installer, I just installed grub2 2.00-8 from experimental in rescue mode. Sys

Re: Bug#695328: [testing/wheezy] UEFI installed system fails to boot

2012-12-29 Thread Kenyon Ralph
On 2012-12-29T16:28:59-0800, Kenyon Ralph wrote: > This is probably part of the problem: on the installed system, > /boot/efi is empty. Rerunning grub-install doesn't change that. Actually, /boot/efi contains EFI/debian/grubx64.efi. For some reason, rescue mode was showing that /boot/efi was moun

Re: Re: building and testing d-i with jenkins

2012-12-29 Thread Steven Chamberlain
Hi Holger, On 5 Dec 2012 21:19:00, Holger Levsen wrote: > there is now > http://jenkins.debian.net/view/cd-tests/job/cd-test_wheezy_lxde/ > doing a g-i installation of lxde desktop and producing a nice video This is great! But what happened to that link, it is a 404 already? I see that wheezy d

Processed: Re: Bug#696968: rootskel-gtk: theme=dark results in ever-looping X

2012-12-29 Thread Debian Bug Tracking System
Processing control commands: > clone -1 -2 Bug #696968 [rootskel-gtk] rootskel-gtk: theme=dark results in ever-looping X Bug 696968 cloned as bug 696972 > retitle -2 brltty wants to be able to terminate Xorg while theme=dark wants > not to terminate it Bug #696972 [rootskel-gtk] rootskel-gtk: the

Bug#696968: rootskel-gtk: theme=dark results in ever-looping X

2012-12-29 Thread Samuel Thibault
Control: clone -1 -2 Control: retitle -2 brltty wants to be able to terminate Xorg while theme=dark wants not to terminate it Control: tags -1 + pending Hello, Cyril Brulebois, le Sun 30 Dec 2012 01:26:25 +0100, a écrit : > adding theme=dark to the command line for accessibility purposes leads >

Bug#696969: rootskel-gtk: Improve theme=dark, especially the banner

2012-12-29 Thread Cyril Brulebois
Samuel Thibault (30/12/2012): > Maybe just use the same solid background color as the rest of the > screen, to make the output as simple as possible. The diamond-shaped > dot can probably remain pink indeed. ACK; Paul ↑ ;) > I'm not sure why you consider the rest of the screen as nasty. I > gues

Bug#696969: rootskel-gtk: Improve theme=dark, especially the banner

2012-12-29 Thread Samuel Thibault
Cyril Brulebois, le Sun 30 Dec 2012 01:26:27 +0100, a écrit : > Nonetheless, I'd be happy to see an improved banner soonish; I'd suggest > something like a solid background color, and just a white debian > text+swirl there (maybe keep a pink, diamond-shaped dot on the 'i'). Maybe just use the same

Bug#696970: cdebconf-gtk-udeb: Add support for an alternate logo in the banner

2012-12-29 Thread Cyril Brulebois
Package: cdebconf-gtk-udeb Version: 0.181 Severity: normal Tags: d-i Hi, currently we have a logo defined by: | #define LOGO_IMAGE_PATH \ | BASE_IMAGE_PATH "/logo_installer.png" In a bug report against rootskel-gtk (bug number is pending), I suggested we improve support for theme=dark, espec

Bug#696969: rootskel-gtk: Improve theme=dark, especially the banner

2012-12-29 Thread Cyril Brulebois
Package: rootskel-gtk Version: 1.26 Severity: normal Tags: d-i Hi -boot@/-accessibility@/Paul, as mentioned on IRC, when enabling accessibility through theme=dark (warning, it’s been broken for a while, see the other rootskel-gtk bug report on that topic), one gets a quite nasty screen, see attac

Bug#696968: rootskel-gtk: theme=dark results in ever-looping X

2012-12-29 Thread Cyril Brulebois
Package: rootskel-gtk Version: 1.26 Severity: important Tags: d-i Hi folks, adding theme=dark to the command line for accessibility purposes leads to an ever-looping X. Basically, options for the X server (see rootskel-gtk's S62Xorg) lead to its termination after a first client exited, and that's

Processed: found 679293 in 4.0.5, found 656586 in 2.4.1-1, found 672372 in 3.2.1-4, found 672160 in 1.89 ...

2012-12-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 679293 4.0.5 Bug #679293 [fai-quickstart] fai-quickstart: fails to purge: fai-quickstart.postrm: 7: .: Can't open /etc/fai/nfsroot.conf Marked as found in versions fai/4.0.5. > found 656586 2.4.1-1 Bug #656586 [routino-www] fails to purge -

Bug#646704: Bug severity is too high

2012-12-29 Thread Daniel Baumann
On 12/29/2012 10:33 PM, Samuel Thibault wrote: > As Christian said, it's not just a bug "in live-installer", but "with > crypted volume", which makes it much less grave. the purpose of live-installer is to be able to use d-i to install live-images. like i said, if that fails (by an original bug in

Bug#646704: Bug severity is too high

2012-12-29 Thread Daniel Baumann
On 12/29/2012 10:10 PM, Christian PERRIER wrote: > Which probably explains why you haven't done anything since > September, I guess. i for my part have clearly said publicly many times when i'm going to work on live-installer parts (when the other live-* parts are done, that is), so that's no surp

Re: d-i manual (Re: building and testing d-i with jenkins)

2012-12-29 Thread Holger Wansing
Hi, today I found the following on http://jenkins.debian.net/view/d-i_manual/job/d-i_manual_pt_pdf/lastBuild/console rmdir: failed to remove `pdf/pt.amd64': Directory not empty rmdir: failed to remove `pdf/pt.armel': Directory not empty rmdir: failed to remove `pdf/pt.armhf': Directory not empty

Bug#646704: Bug severity is too high

2012-12-29 Thread Samuel Thibault
Daniel Baumann, le Sat 29 Dec 2012 20:16:57 +0100, a écrit : > On 12/29/2012 0502 PM, Christian PERRIER wrote: > > This bug doesn't fit the definition of "serious" as it only shows up > > for a precise set of installation types, those not being the most > > common, particularly when people use the

Bug#696952: marked as done (installation-reports: evdev crashed with backtrace - kernel oops)

2012-12-29 Thread Debian Bug Tracking System
Your message dated Sat, 29 Dec 2012 22:14:27 +0100 with message-id <20121229211427.gz6...@mykerinos.kheops.frmug.org> and subject line Re: Bug#696952: installation-reports: evdev crashed with backtrace - kernel oops has caused the Debian Bug report #696952, regarding installation-reports: evdev cr

Bug#646704: Bug severity is too high

2012-12-29 Thread Christian PERRIER
Quoting Daniel Baumann (daniel.baum...@progress-technologies.net): > severity 646704 serious > thanks > > On 12/29/2012 0502 PM, Christian PERRIER wrote: > > This bug doesn't fit the definition of "serious" as it only shows up > > for a precise set of installation types, those not being the most >

Bug#696952: installation-reports: evdev crashed with backtrace - kernel oops

2012-12-29 Thread Sandy Beach
Package: installation-reports Severity: normal Tags: d-i -- Package-specific info: Boot method: CD Image version: debian-wheezy-DI-b4-amd64-i386-netinst.iso Date: 28dec2012 22:00 EST Machine: personal build - intel D845grg 2.2Ghz p4 512Mb pc2100 ddr 8Mb shared vide http://downloadmirror.int

Bug#646704: live-installer: installer doesn't write /etc/crypttab for crypt+LVM

2012-12-29 Thread Daniel Baumann
tag 646704 - confirmed thanks usage of the tag 'confirmed' is reserved for the maintainer to indicate that he could reproduce it, not users (re)reporting it. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet:

Processed: Re: live-installer: installer doesn't write /etc/crypttab for crypt+LVM

2012-12-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 646704 - confirmed Bug #646704 [live-installer] live-installer: installer doesn't write /etc/crypttab for crypt+LVM Removed tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 646704: http://bug

Processed: Re: Bug#646704: Bug severity is too high

2012-12-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 646704 serious Bug #646704 [live-installer] live-installer: installer doesn't write /etc/crypttab for crypt+LVM Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#646704: Bug severity is too high

2012-12-29 Thread Daniel Baumann
severity 646704 serious thanks On 12/29/2012 0502 PM, Christian PERRIER wrote: > This bug doesn't fit the definition of "serious" as it only shows up > for a precise set of installation types, those not being the most > common, particularly when people use the Live CD to install. a bug in live-in

Re: Installing Lenny

2012-12-29 Thread Shawn Willden
NM. I found the "enter information manually" option. Sorry for bugging. On Sat, Dec 29, 2012 at 12:00 PM, Shawn Willden wrote: > I have an LVS which is still running Lenny (I know, I know) and I need to > upgrade it to Squeeze. Before I do, though, I need to first replicate the > system in a

Installing Lenny

2012-12-29 Thread Shawn Willden
I have an LVS which is still running Lenny (I know, I know) and I need to upgrade it to Squeeze. Before I do, though, I need to first replicate the system in a VM, test it, upgrade it and test that. So I'm trying to install Lenny in order to upgrade it to Sqeeze. I'm on a fairly slow Internet conn

Processed: Re: Bug#696903: [1.83->1.84 regression]: GRUB won't install to a character device

2012-12-29 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #696903 [grub-installer] [1.83->1.84 regression]: GRUB won't install to a character device Added tag(s) patch. -- 696903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696903 Debian Bug Tracking System Contact ow...@bugs.debian.org with prob

Bug#696903: [1.83->1.84 regression]: GRUB won't install to a character device

2012-12-29 Thread Steven Chamberlain
Control: tags -1 + patch Allow installing GRUB to a character device, as on GNU/kFreeBSD diff --git a/grub-installer b/grub-installer index 5d9fd77..6e2c7fc 100755 --- a/grub-installer +++ b/grub-installer @@ -651,9 +651,9 @@ if [ -z "$frdisk" ]; then # Install grub on each space separate

Bug#696942: [1.83->1.84 regression]: GRUB won't install to a dummy device

2012-12-29 Thread Steven Chamberlain
Package: grub-installer Version: 1.84 Severity: grave Tags: d-i X-Debbugs-Cc: paj...@gmail.com Control: block 681227 by -1 Hello, On 29/12/12 10:39, alberto fuentes wrote: > Dec 29 00:41:32 grub-installer: info: Installing grub on 'dummy' > Dec 29 00:41:32 grub-installer: error: no boot device fo

Processed: [1.83->1.84 regression]: GRUB won't install to a dummy device

2012-12-29 Thread Debian Bug Tracking System
Processing control commands: > block 681227 by -1 Bug #681227 [grub-installer] installation-reports: grub-install tries to install to a nonsense string 681227 was blocked by: 696903 681227 was not blocking any bugs. Added blocking bug(s) of 681227: 696942 -- 681227: http://bugs.debian.org/cgi-b

Bug#695500: debian-installer-7.0-netboot-kfreebsd-amd64: does not boot from pxe

2012-12-29 Thread Steven Chamberlain
Hi Michael, Michael Tsang (09/12/2012): > I cannot boot the installer from pxe. GRUB says prefix is not set > and dies. It seems to be a configuration bug. I see now that the "prefix is not set" message appears very quickly, before GRUB switches into graphical mode. It seems harmless, because a

Processed: Bug severity is too high

2012-12-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 646704 important Bug #646704 [live-installer] live-installer: installer doesn't write /etc/crypttab for crypt+LVM Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#646704: Bug severity is too high

2012-12-29 Thread Christian PERRIER
severity 646704 important thanks This bug doesn't fit the definition of "serious" as it only shows up for a precise set of installation types, those not being the most common, particularly when people use the Live CD to install. Downgrading to "important" as per the definition of "improtant" seve

Bug#693839: debian-installer: kernel install fails on armel buffalo linkstation pro, missing uboot-mkimage

2012-12-29 Thread Christian PERRIER
Quoting Cyril Brulebois (k...@debian.org): > Hi, and thanks for your report. > > u-boot-tools is only in “Suggests” for flash-kernel, while your > situation suggests it might be better to have it in “Recommends”. > What do others think? Well, I even moved it to Depends in my commit. I'm not sure

Bug#693485: Re[2]: Bug#693485: keyboard-configuration: XKBLAYOUT, XKBOPTIONS values manually set in /etc/default/keyboard lost on upgrade

2012-12-29 Thread Anton Zinoviev
On Fri, Dec 28, 2012 at 01:32:50AM +0400, Bob Bib wrote: > > OK, but the output is a little bit too verbose (see it attached). Good. I think this will be an exciting reading. Anton Zinoviev -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trou

Bug#433568: add vlan support

2012-12-29 Thread Philipp Kern
On Sat, Dec 29, 2012 at 08:34:27AM +0100, Christian PERRIER wrote: > Taking over KiBi's hat, I would say there is no chance this makes it > to wheezy. And taking mine, too, with several addition to localization > bits. The debconf templates need minor edits to compleltely fit with > the writing sty

Re: d-i wheezy rc1 status; and unblock(-udeb)s, round 4

2012-12-29 Thread alberto fuentes
Nice new installer. I tried this and the beta3. Less bugs. The dialogs are more clear and the text that goes with it. The way the questions are separated from the explanations. The borderless window in the gui. Overall I saw a great improvement in the experience. small details i found: - A little