Bug#771158: /etc/kernel/postinst.d/initramfs-tools: please support CONFIG_MODULE_COMPRESS=y

2014-11-27 Thread Uwe Kleine-König
Package: initramfs-tools Version: 0.116 Severity: wishlist File: /etc/kernel/postinst.d/initramfs-tools Hello, I installed a custom kernel (created by make deb-pkg on 3.18-rc6) with CONFIG_MODULE_COMPRESS=y. The resulting initramfs image didn't contain any modules resulting in an unbootable

Processed: retitle 766920 to produces unbootable initramfs with lilo hexadecimal syntax (root=803)

2014-11-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: retitle 766920 produces unbootable initramfs with lilo hexadecimal syntax (root=803) Bug #766920 [initramfs-tools] initramfs-tools: update-initramfs makes system unbootable due to missing rootfs Changed Bug title to 'produces unbootable

Bug#767832: Initramfs provided in initramfs-tools_0.118_all won’t automount luks partitions at boot

2014-11-27 Thread Simon McVittie
On Sun, 02 Nov 2014 at 22:21:16 +0100, zer0 divide wrote: I chose during installation luks partitioning (not lvm), and separated /boot (on an usb pendrive) partition from /root partition (on another drive with the other one). That isn't a full description of what you did; I can tell because

Bug#767832: Initramfs provided in initramfs-tools_0.118_all won’t automount luks partitions at boot

2014-11-27 Thread Simon McVittie
On Thu, 27 Nov 2014 at 10:02:34 +, Simon McVittie wrote: On Sun, 02 Nov 2014 at 22:21:16 +0100, zer0 divide wrote: My system does not start automatically after I enter the password for unlocking the root partition. I have to unlock manually /usr (from initramfs ), and then do CTRL + D.

Bug#767832: Initramfs provided in initramfs-tools_0.118_all won’t automount luks partitions at boot

2014-11-27 Thread Simon McVittie
Control: retitle 767832 cryptsetup: does not decrypt a split /usr as required by initramfs-tools = 0.118 Control: reassign 767832 cryptsetup Control: found 767832 cryptsetup/2:1.6.6-3 Control: affects 767832 initramfs-tools Control: tags 767832 + patch I think this is a cryptsetup bug. The

Processed: Re: Bug#767832: Initramfs provided in initramfs-tools_0.118_all won’t automount luks partitions at boot

2014-11-27 Thread Debian Bug Tracking System
Processing control commands: retitle 767832 cryptsetup: does not decrypt a split /usr as required by initramfs-tools = 0.118 Bug #767832 [initramfs-tools] Initramfs provided in initramfs-tools_0.118_all won’t automount luks partitions at boot Changed Bug title to 'cryptsetup: does not decrypt

Bug#767589: systemd: cryptdisks other than root/swap fail cryptsetup

2014-11-27 Thread Simon McVittie
On Sat, 01 Nov 2014 at 11:50:40 +0100, Arnaud Installe wrote: After successfully unlocking and mounting root and swap devices, the system hangs a while, then drops to a rescue shell, with /usr, /var and /home not unlocked by cryptsetup. After manually running cryptsetup for the underlying

Bug#762984: Alert! /dev/vg0/usr does not exist

2014-11-27 Thread Simon McVittie
On Wed, 01 Oct 2014 at 22:18:53 +0100, Ben Hutchings wrote: I suspect this is essentially the same bug as #616689 and #678696, except that now it may affect mounting /usr as well as /. I think this bug report is actually describing more than one bug in more than one package that have similar

Processed: [bts-link] source package src:linux

2014-11-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package src:linux # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org

Bug#771224: linux-image-3.16.0-4-amd64: Recurring traces from tcp_fragment+0x2b1/0x2c0 (linux-3.16.7/net/ipv4/tcp_output.c:1085)

2014-11-27 Thread Lebedev Roman
Package: src:linux Version: 3.16.7-2 Severity: normal Dear Maintainer, When there is some network activity, following trace is reliably recurring in dmesg: [34221.894283] [ cut here ] [34221.894286] WARNING: CPU: 6 PID: 0 at

Processed: Re: linux: Btrfs goes forced readonly when qgroup already exists

2014-11-27 Thread Debian Bug Tracking System
Processing control commands: found -1 3.16.7-2 Bug #769576 [src:linux] linux: Btrfs goes forced readonly when qgroup already exists Marked as found in versions linux/3.16.7-2. -- 769576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769576 Debian Bug Tracking System Contact

Bug#769576: linux: Btrfs goes forced readonly when qgroup already exists

2014-11-27 Thread Sebastiaan L. Zoutendijk
Control: found -1 3.16.7-2 On Wed 26 Nov 2014 at 15:12:59 +0100, Bas Zoutendijk wrote: Subsequently, I applied the patch to the Debian sources of this kernel and rebuilt it. I could not reproduce the bug on this patched kernel, so the patch seems to work. Maybe I can try this with an

Bug#762984: Alert! /dev/vg0/usr does not exist

2014-11-27 Thread Elimar Riesebieter
* Simon McVittie s...@debian.org [2014-11-27 11:51 +]: On Wed, 01 Oct 2014 at 22:18:53 +0100, Ben Hutchings wrote: I suspect this is essentially the same bug as #616689 and #678696, except that now it may affect mounting /usr as well as /. I think this bug report is actually

Bug#762984: Alert! /dev/vg0/usr does not exist

2014-11-27 Thread Simon McVittie
On 27/11/14 20:09, Elimar Riesebieter wrote: Right, adding root and usr raid partitions to INITRDSTART like INITRDSTART='/dev/md3 /dev/md5' or just 'all' does the job. There is no need to involve initramfs to mount /usr before init. If your init is systemd, initramfs-tools = 0.117 *does*

Bug#762984: Alert! /dev/vg0/usr does not exist

2014-11-27 Thread Elimar Riesebieter
* Simon McVittie s...@debian.org [2014-11-27 21:19 +]: On 27/11/14 20:09, Elimar Riesebieter wrote: Right, adding root and usr raid partitions to INITRDSTART like INITRDSTART='/dev/md3 /dev/md5' or just 'all' does the job. There is no need to involve initramfs to mount /usr before

linux-headers lying about kernel version is breaking other module packages

2014-11-27 Thread Lennart Sorensen
I was trying to compile loop-aes-source, but it keeps failing. For some reason it kept thinking the kernel version was 2.6, when it is in fact 3.16. The problem is that it looks at the VERSION and PATCHLEVEL in the Makefile of the headers, which for some reason is being modified to read 2 and 6

Bug#762984: Alert! /dev/vg0/usr does not exist

2014-11-27 Thread Javier Barroso
Hello Simon, (I'm dropping CCs, I'm not sure if all body is ok with maintaining such CC list, sorry if somebody have would like to be in CC) On Thu, Nov 27, 2014 at 12:51 PM, Simon McVittie s...@debian.org wrote: On Wed, 01 Oct 2014 at 22:18:53 +0100, Ben Hutchings wrote: I suspect this is

Processed: Re: Bug#771129: Acknowledgement ([lxc] Cpusets don't work)

2014-11-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: reassign 771129 linux Bug #771129 [lxc] [lxc] Cpusets don't work Bug reassigned from package 'lxc' to 'linux'. No longer marked as found in versions lxc/1:1.0.6-4. Ignoring request to alter fixed versions of bug #771129 to the same values