Bug#966816: /lib/systemd/system/blk-availability.service:10: Neither a valid executable name nor an absolute path: ${exec_prefix}/bin/true

2020-08-13 Thread Tom Overlund
I know Debian is a volunteer project, but it seems like bad form when a package-breaking bug is reported on the same day it is introduced, a trivial fix is availble, and 11 days later the package is still broken. One maintainer can trivially fix this, but in the meantime an untold number of

Bug#966816: /lib/systemd/system/blk-availability.service:10: Neither a valid executable name nor an absolute path: ${exec_prefix}/bin/true

2020-08-13 Thread Jonathan Marsaud
Package: lvm2 Version: 2.03.09-2 Followup-For: Bug #966816 X-Debbugs-Cc: jonathanmars...@gmail.com Dear Maintainer, I can confirm this bug too. The solution to simply remove the "ExecStart" line as this unit is type "oneshot" seems to be the best according to the version of systemd (in old

Bug#966816: /lib/systemd/system/blk-availability.service:10: Neither a valid executable name nor an absolute path: ${exec_prefix}/bin/true

2020-08-06 Thread Awtul
Package: lvm2 Version: 2.03.09-2 Followup-For: Bug #966816 I confirm the bug.

Bug#966816: /lib/systemd/system/blk-availability.service:10: Neither a valid executable name nor an absolute path: ${exec_prefix}/bin/true

2020-08-02 Thread Michael Biebl
Package: lvm2 Version: 2.03.09-2 Severity: important File: /lib/systemd/system/blk-availability.service $ systemctl cat blk-availability.service # /lib/systemd/system/blk-availability.service [Unit] Description=Availability of block devices Before=shutdown.target After=lvm2-activation.service