Bug#944860: udevadm trigger fails in chroot

2019-11-16 Thread Michael Biebl
Control: retitle -1 udevadm trigger fails in containers with ro /sys Am 17.11.19 um 02:43 schrieb Michael Biebl: > Am 17.11.19 um 01:57 schrieb Jonah Brüchert: >> After slightly looking into the debos source code it seems also possible >> that it uses a systemd-spawn container in some cases >> (ht

Bug#944860: udevadm trigger fails in chroot

2019-11-16 Thread Michael Biebl
Am 17.11.19 um 01:57 schrieb Jonah Brüchert: > After slightly looking into the debos source code it seems also possible > that it uses a systemd-spawn container in some cases > (https://github.com/go-debos/debos/blob/2764eed783b1b0ffb5d09f796338f09a4e2594b6/commands.go#L15) Can you please verify,

Bug#944860: udevadm trigger fails in chroot

2019-11-16 Thread Michael Biebl
Am 17.11.19 um 01:57 schrieb Jonah Brüchert: > Thanks for looking into the issue. > >> Can you be more specific how you setup your chroot so we have a chance >> to reproduce the problem? [..] I guess you'll need to break that down to a more minimal test case for me being able to reproduce the is

Bug#944860: udevadm trigger fails in chroot

2019-11-16 Thread Jonah Brüchert
Thanks for looking into the issue. Can you be more specific how you setup your chroot so we have a chance to reproduce the problem? The exact setup is a little more complicated. The chroot is created using debos, which if I remember correctly uses a chroot inside qemu if that's relevent. The

Bug#944860: udevadm trigger fails in chroot

2019-11-16 Thread Michael Biebl
Control: tags -1 moreinfo unreproducible Am 16.11.19 um 16:05 schrieb Jonah Brüchert: > Package: udev > Version: 243-5 > Severity: normal > > Dear Maintainer, > > When running udevadm trigger in a chroot, in this case using debos, it fails > to write changes to /sys and exits with an error code