[Pkg-utopia-maintainers] Bug#917633: Bug#917633: udisk2 post-installation fails in chrooted environments

[Alf Gaida]

On 29.12.18 16:42, Michael Biebl wrote:
> Keep in mind that deb-systemd-invoke respects policy-rc.d and a build
> chroot should normally have setup policy-rc.d to not start any services.
> 
> And if you try to run systemctl directly inside a chroot you should get
> something like this
> # systemctl start udisks2
> Running in chroot, ignoring request: start
> 
> So I'm not quite sure why it fails for you.
> 

Maybe i wasn't clear enough - i didn't try anything in that regard, i
only tried to install the package within an iso build. With the
unmodified udisk2 package the result in the log was:

Setting up libhttp-daemon-perl (6.01-1) ...
Setting up udisks2 (2.8.1-3) ...
Failed to scan devices: No such file or directory
dpkg: error processing package udisks2 (--configure):
 installed udisks2 package post-installation script subprocess returned
error exit status 1
Setting up aptitude (0.8.11-6) ...

after a quick and really dirty modification:

diff --git a/debian/udisks2.postinst b/debian/udisks2.postinst
index 0dcf95b..381cd96 100644
--- a/debian/udisks2.postinst
+++ b/debian/udisks2.postinst
@@ -4,7 +4,7 @@ set -e

 if [ "$1" = "configure" ]; then
     # we ship udev rules, so trigger an update
-    udevadm trigger --subsystem-match=block --action=change
+    udevadm trigger --subsystem-match=block --action=change | true

 fi

the installation result looks like this:

Setting up libhttp-daemon-perl (6.01-1) ...
Setting up udisks2 (2.8.1-3.1) ...
Failed to scan devices: No such file or directory
Created symlink
/etc/systemd/system/graphical.target.wants/udisks2.service ->
/lib/systemd/system/udisks2.service.
Setting up aptitude (0.8.11-6) ...

So it seems that the udevadm trigger is the culprit

Cheers Alf