Bug#915261: SysV init regression thanks to broken "container detection" logic

2018-12-06 Thread GSR
Package: udev Version: 239-14 Followup-For: Bug #915261 I tried to set severity to serious but it was reverted. An unbootable system is not nice, I had to look around for a rescue disk (luckly I still had one around) to change the script (it was obvious by message, and also I roughly remembered

Bug#915261: SysV init regression thanks to broken "container detection" logic

2018-12-06 Thread GSR
Package: udev Version: 239-14 Followup-For: Bug #915261 Severity: serious Severity should be at least serious, for two reasons. First so it gets listed with apt-listbugs default levels and people can decide what to do. And second, it does not affect every user, but those affected have to handle a

Bug#915261: SysV init regression thanks to broken "container detection" logic

2018-12-02 Thread Felipe Sateler
Control: tags -1 pending On Sun, Dec 2, 2018 at 10:51 AM Lorenz wrote: > I confirm the bug. This prevent me to start/restart udev, and i'm not in a > container. > > On Sun, 2 Dec 2018 09:00:07 + Jamie Heilman < > ja...@audible.transient.net> wrote: > > The logic change in the init script to

Bug#915261: SysV init regression thanks to broken "container detection" logic

2018-12-02 Thread Lorenz
I confirm the bug. This prevent me to start/restart udev, and i'm not in a container. On Sun, 2 Dec 2018 09:00:07 + Jamie Heilman wrote: > The logic change in the init script to check for a writable /sys is > backwards; udev *should* start if /sys if writable. I don't have experience with

Bug#915261: SysV init regression thanks to broken "container detection" logic

2018-12-02 Thread Jamie Heilman
Package: udev Version: 239-14 Severity: important The logic change in the init script to check for a writable /sys is backwards; udev *should* start if /sys if writable. -- Jamie Heilman http://audible.transient.net/~jamie/