Processed: [bts-link] source package systemd

2017-09-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package systemd > # 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.o

[bts-link] source package systemd

2017-09-07 Thread bts-link-upstream
# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #852534 (http://bugs.debian.org/852534) # Bug title: systemd: cryptsetup-generator doe

Re: Bug#872999: qemu image built by vmdebootstrap is unbootable due to bad root=/dev/mapper/loop0p1 kernel parameter

2017-09-07 Thread Raphael Hertzog
On Thu, 07 Sep 2017, Ben Hutchings wrote: > On Thu, 2017-09-07 at 12:53 +0200, Raphael Hertzog wrote: > > On Thu, 07 Sep 2017, Raphael Hertzog wrote: > > > What informs udev about the new filesystem? > > > > Somehow, it's the kernel apparently. > > > > > Or is this a bug in the kernel really? > >

Re: Bug#872999: qemu image built by vmdebootstrap is unbootable due to bad root=/dev/mapper/loop0p1 kernel parameter

2017-09-07 Thread Ben Hutchings
On Thu, 2017-09-07 at 12:53 +0200, Raphael Hertzog wrote: > On Thu, 07 Sep 2017, Raphael Hertzog wrote: > > What informs udev about the new filesystem? > > Somehow, it's the kernel apparently. > > > Or is this a bug in the kernel really? > > At least "udevadm monitor" shows that the kernel is se

Re: Bug#872999: qemu image built by vmdebootstrap is unbootable due to bad root=/dev/mapper/loop0p1 kernel parameter

2017-09-07 Thread Raphael Hertzog
On Thu, 07 Sep 2017, Raphael Hertzog wrote: > Is there anything that can be done by vmdebootstrap to force-trigger the > creation of that entry even when chrooted? Yes, "udevadm trigger" or "udevadm trigger /dev/mapper/loop0p1" works well for that. So we have a work-around at least (thanks to Feli

Re: Bug#872999: qemu image built by vmdebootstrap is unbootable due to bad root=/dev/mapper/loop0p1 kernel parameter

2017-09-07 Thread Raphael Hertzog
On Thu, 07 Sep 2017, Raphael Hertzog wrote: > What informs udev about the new filesystem? Somehow, it's the kernel apparently. > Or is this a bug in the kernel really? At least "udevadm monitor" shows that the kernel is sending less uevents when I run the command in the chroot. I attach two logs

Re: Bug#872999: qemu image built by vmdebootstrap is unbootable due to bad root=/dev/mapper/loop0p1 kernel parameter

2017-09-07 Thread Raphael Hertzog
[ Ccing grub, udev, linux maintainers for the questions at the end, I want to understand why some /dev/disk/by-uuid/ entries are not properly created ] Hello, On Wed, 23 Aug 2017, Raphaël Hertzog wrote: > Hello, I'm trying to update my qemu image used for autopkgtest, so I > followed the inst

★★★★★≤澳門銀河116948點com精準資料＜一碼中特＞註冊即送38｜釦釦：330081906｜≥qerw

2017-09-07 Thread 袁若翠
___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers