Bug#910770: dash: systemd-detect-virt fails to detect virtualized environment when run under dash

2018-10-15 Thread Andy Sparrow
On Wed, Oct 10, 2018 at 7:50 PM Michael Biebl wrote: > Am 11.10.18 um 03:53 schrieb Jonathan Nieder: > Fwiw, I can't reproduce > > ... > > This is on stretch. > Works as expected on stretch. Both moving parts - both systemd (215 -> 232) & dash (0.5.7 -> 0.5.8) - are at different versions on

Bug#910770: dash: systemd-detect-virt fails to detect virtualized environment when run under dash

2018-10-10 Thread Andy Sparrow
Hi, > Do you have more details? > What test does systemd-detect-virt use, and why is it failing on dash? Good question(s); not looked at this in more detail. > What version of systemd are you using? In the guest, systemd 215; which corresponds to whats in Jessie up to 8.11. In the host,

Bug#910770: dash: systemd-detect-virt fails to detect virtualized environment when run under dash

2018-10-10 Thread Michael Biebl
Am 11.10.18 um 03:53 schrieb Jonathan Nieder: > Hi, > > spuggy...@gmail.com wrote: > >> When run under dash, systemd-detect-virt returns "none" in a systemd-nspawn >> chroot'd environment when it should not; same command under bash works >> as expected. > > Do you have more details? What test

Bug#910770: dash: systemd-detect-virt fails to detect virtualized environment when run under dash

2018-10-10 Thread Jonathan Nieder
Hi, spuggy...@gmail.com wrote: > When run under dash, systemd-detect-virt returns "none" in a systemd-nspawn > chroot'd environment when it should not; same command under bash works > as expected. Do you have more details? What test does systemd-detect-virt use, and why is it failing on dash?

Bug#910770: dash: systemd-detect-virt fails to detect virtualized environment when run under dash

2018-10-10 Thread spuggy...@gmail.com
Package: dash Version: 0.5.7-4+b1 Severity: important Dear Maintainer, When run under dash, systemd-detect-virt returns "none" in a systemd-nspawn chroot'd environment when it should not; same command under bash works as expected. Because /bin/sh is linked to /bin/dash, this causes the MAKEDEV