Bug#658089: cracklib2: Please add a udeb for early password quality checking in d-i

Package: cracklib2 Severity: wishlist Hi, it would be nice if there was a cracklib udeb which could be integrated into d-i to allow for password quality checking for the root and first user password entered during installation. It wouldn't necessarily block installation if the chosen password is

Bug#657830: win32-loader: Please make pxe.target depend on the ipxe package

tags 657830 +patch thanks Le 29.01.2012 11:00, Alkis Georgopoulos a écrit : An ipxe package is available in Debian wheezy and sid: $ rmadison ipxe ipxe | 1.0.0+git-2.149b50-1 | wheezy | source, all ipxe | 1.0.0+git-2.149b50-1 | sid| source, all It would be awesome if people could get

Processed: Re: Bug#657830: win32-loader: Please make pxe.target depend on the ipxe package

Processing commands for cont...@bugs.debian.org: tags 657830 +patch Bug #657830 [win32-loader] win32-loader: Please make pxe.target depend on the ipxe package Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 657830:

Bug#658103: netcfg: Detect invalid MAC address

Package: netcfg Severity: wishlist Tags: d-i When installing on an Openpeak Joggler, the wired ethernet interface doesn't work because the manufacturer programmed an invalid (and constant) MAC address into each device. It would be very nice if netcfg could detect this (possibly by the error you

Bug#657830: win32-loader: Please make pxe.target depend on the ipxe package

Στις 31/01/2012 12:26 μμ, ο/η Didier 'OdyX' Raboud έγραψε: I propose the attached patch that would do even better, by providing a win32-loader-pxe.exe from the Debian mirrors, available on http://ftp.debian.org/debian/tools/win32-loader/unstable/win32-loader-pxe.exe ... What do you (and

Re: Nach autom. Upgrade auf 6.04, boot failed

On Mon, Jan 30, 2012 at 03:38:43PM +0100, Martin Stahl wrote: Ich habe vor ein paar Tagen Debian 6.03 neu aufgesetzt. Nun wurden mir 64 updates im Panel angezeigt als verfügbar. (Scheint sich wohl um das upgrade auf 6.04 zu handeln) Nun bleibt der Bootvorgang stehen, keine screenanzeige mehr,

Continuing to use old kernels for installation after point releases

I have a setup at work which, amongst other things, regularly autoinstalls Debian. Because I don't want it to break unexpectedly, I prefer to keep using old installation kernels - for example, new kernels may have different requirements for non-free firmware etc., so I think it's not trivial to

Processed: reassign 658037 to installation-reports

Processing commands for cont...@bugs.debian.org: reassign 658037 installation-reports Bug #658037 [debian-installer] D-I tries to install Debian on my cellphone instead of loading the firmware Bug reassigned from package 'debian-installer' to 'installation-reports'. thanks Stopping processing

Bug#658037: D-I tries to install Debian on my cellphone instead of loading the firmware

On Tue, Jan 31, 2012 at 02:43:26AM +0100, Michelle Konzack wrote: Yes, they are all 335-8676 Strange that they wouldn't work the same then. Same BIOS/raid controller firmware versions on them all? It shouldn't ask since the firmware is built in so that you can boot from it. Not like the

Processed: tagging 656772

Processing commands for cont...@bugs.debian.org: tags 656772 + patch pending Bug #656772 [win32-loader] Update Simplified Chinese translation of win32-loader Added tag(s) pending and patch. thanks Stopping processing here. Please contact me if you need assistance. -- 656772:

Processed: tagging 657268

Processing commands for cont...@bugs.debian.org: tags 657268 + pending Bug #657268 [win32-loader] win32-loader: [INTL:pl] Updated Polish translation Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 657268:

Bug#656906: win32-loader: [INTL:sr@latin] Serbian Latin templates translation

Hi Karolina and Christian, Le 24.01.2012 00:39, Karolina Kalic a écrit : Serbian.nlf to SerbianLatin.nlf, I checked, Serbian Latin is supported by Nsis installer. Great, thanks. I'm just not sure about this: #. translate: #. This must be a valid string recognised by Nsis. If your #.

Bug#658129: marked as done (debian-installer: installer puts cdrom in fstab on machines without cdrom drive)

Your message dated Tue, 31 Jan 2012 19:15:35 +0100 with message-id 20120131181535.GB10744@candra and subject line Re: Bug#658129: debian-installer: installer puts cdrom in fstab on machines without cdrom drive has caused the Debian Bug report #658129, regarding debian-installer: installer puts

Bug#658037: D-I tries to install Debian on my cellphone instead of loading the firmware

severity 658037 normal thanks Quoting Michelle Konzack (linux4miche...@tamay-dogan.net): 2) If I mount the USB-Stick (cellphone or SD card) manualy, D-I detect it as an install medium and does not bother installing Debian on it. WTF? So, D-I detects it as the only disk an considers

Processed: Re: Bug#658037: D-I tries to install Debian on my cellphone instead of loading the firmware

Processing commands for cont...@bugs.debian.org: severity 658037 normal Bug #658037 [installation-reports] D-I tries to install Debian on my cellphone instead of loading the firmware Severity set to 'normal' from 'important' thanks Stopping processing here. Please contact me if you need

Bug#649146: debootstrap-1.0.38 also affected

This isn't fixed in 1.0.38. I'm seeing the same error and segfault trying to debootstrap lucid in a fakechroot. Big Fish Games, Inc. A New Game Every Day! (R) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

My cdebconf is escaped !

Hi guys, So, after weeks of fighting and turning the problem around (while moving to Italy and starting a new job), I believe I have now finally implemented the escape CAPB (might not be optimal, but I believe it works). There is still some way to go before cdebconf can replace debconf 100%,

The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module.

Good day. Few days ago found all our preseed-based installation stated failing with message The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module. 1) Preseed was untouched 2) We didn't download newer initrd/vmlinuz and using saved images to your

Re: The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module.

Hi all. Few days ago found all our preseed-based installation stated failing with message The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module. 1) Preseed was untouched 2) We didn't download newer initrd/vmlinuz and using saved images to your

Re: The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module.

On 01.02.2012 00:53, Marcus Moeller wrote: Few days ago found all our preseed-based installation stated failing with message The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module. 1) Preseed was untouched 2) We didn't download newer

Re: The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module.

Am 31.01.2012 21:59, schrieb George Shuklin: On 01.02.2012 00:53, Marcus Moeller wrote: Few days ago found all our preseed-based installation stated failing with message The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module. 1) Preseed was

Re: The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module.

Hi again. The most strage thing: Wheezy and Squeezy (!) installers both was broken. I feel somehow lost due 'stable' regression. Are you using the kernel.org mirror? This one seems to be out of sync atm. I had the same problem, which has been solved by downloading the images form an up2date

Re: The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module.

On Tue, Jan 31, 2012 at 11:50:48PM +0300, George Shuklin wrote: 2) We didn't download newer initrd/vmlinuz and using saved images to your servers (some days before they works fine for long time, now stops) You should probably install one of the debian-installer-6.0-netboot-amd64 packages on

Re: The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module.

On Tue, Jan 31, 2012 at 09:46:50PM +, Ian Jackson wrote: Would you agree that this is a bug ? Can you tell me what's broken? Kind regards, Philipp Kern -- .''`. Philipp KernDebian Developer : :' : http://philkern.de Stable Release Manager

Re: The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module.

Philipp Kern writes (Re: The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module.): On Tue, Jan 31, 2012 at 11:50:48PM +0300, George Shuklin wrote: 2) We didn't download newer initrd/vmlinuz and using saved images to your servers (some days

Debian installer build: failed or old builds

Debian installer build overview --- Failed or old builds: * FAILED BUILD: armel Jan 31 06:07 buildd@ancina build_iop32x_netboot http://d-i.debian.org/daily-images/armel/daily/build_iop32x_netboot.log * FAILED BUILD: armel Jan 31 06:07 buildd@ancina