3. How we could fix it?
Well, given the data I posted above, my *guess* is that we could safely
ignore the udevadm non-zero exit status in the udisks2 postinst script
with something like this:
if [ "$1" = "configure" ]; then
# we ship udev rules, so trigger an update
udevadm trigger --subsystem-match=block --action=change || true
fi
Note the final "|| true". In case the conjecture I just made above is correct,
I prepared a modified udisks2 package in a PPA which doesn't fail to install:
https://launchpad.net/~panfaust/+archive/ubuntu/udisks2
If the conjecture I made and/or proposed fix are wrong, I hope at least
the data I provided leads to the correct solution.
Regards.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1845314
Title:
udisks2 fails to install in a container with systemd 243
Status in systemd package in Ubuntu:
Confirmed
Bug description:
santa_ | rbalint: hey while systemd 243 was available in eoan I still
got one of "my" issues (udisks2 fails to install in a container)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1845314/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
