Bug#917633: udisk2 post-installation fails in chrooted environments
Control: affects 917633 src:ltsp Also blocking migration for ltsp: https://piuparts.debian.org/sid/fail/ltsp-server-standalone_5.18.12-1.log live well, vagrant signature.asc Description: PGP signature
Bug#917633: [Pkg-utopia-maintainers] Bug#917633: Bug#917633: udisk2 post-installation fails in chrooted environments
Control: affects -1 src:gvfs src:gnome-disk-utility Control: tags -1 +patch This issue was detected by piuparts and is blocking migration to Testing for gnome-disk-utility and gvfs. I see that there is a MR now: https://salsa.debian.org/utopia-team/udisks2/merge_requests/2 References https://piuparts.debian.org/sid/source/g/gnome-disk-utility.html https://piuparts.debian.org/sid/source/g/gvfs.html Thanks, Jeremy Bicha
Bug#917633: [Pkg-utopia-maintainers] Bug#917633: Bug#917633: udisk2 post-installation fails in chrooted environments
Am 29.12.18 um 18:59 schrieb Alf Gaida: > On 29.12.18 18:54, Michael Biebl wrote: >> I guess you meant "||" here. >> >> That seems like a reasonable change. Do you want to file a MR for that? >> > > Yes - otherwise it would be cool to know the reason for the change in > behaviour. Quickly glancing at the systemd v240 changelog I don't see any mention of a changed udevadm behaviour. So I'm not sure if it's deliberate or not (fwiw I actually haven't tested if v239 behaves differently) -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Bug#917633: [Pkg-utopia-maintainers] Bug#917633: Bug#917633: udisk2 post-installation fails in chrooted environments
On 29.12.18 18:54, Michael Biebl wrote: > I guess you meant "||" here. > > That seems like a reasonable change. Do you want to file a MR for that? > Yes - otherwise it would be cool to know the reason for the change in behaviour. signature.asc Description: OpenPGP digital signature
Bug#917633: [Pkg-utopia-maintainers] Bug#917633: udisk2 post-installation fails in chrooted environments
Additional: «Installing in a chroot should not fail because udevadm trigger in postinst». https://bugs.debian.org/917642 Changed behaviour of udevadm?
Bug#917633: [Pkg-utopia-maintainers] Bug#917633: Bug#917633: udisk2 post-installation fails in chrooted environments
Am 29.12.18 um 17:05 schrieb Alf Gaida: > 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 I guess you meant "||" here. That seems like a reasonable change. Do you want to file a MR for that? signature.asc Description: OpenPGP digital signature
Bug#917633: [Pkg-utopia-maintainers] Bug#917633: udisk2 post-installation fails in chrooted environments
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
Bug#917633: [Pkg-utopia-maintainers] Bug#917633: udisk2 post-installation fails in chrooted environments
Am 29.12.18 um 16:28 schrieb Alf Gaida: > Package: udisks2 > Version: 2.8.1-3 > Severity: important > > Dear Maintainer, > > tried to install udisks2 in a chroot: > > 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 > Noticed the chroot check for udev and wonder about if a check would be > helpful here too. 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. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Bug#917633: udisk2 post-installation fails in chrooted environments
Package: udisks2 Version: 2.8.1-3 Severity: important Dear Maintainer, tried to install udisks2 in a chroot: 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 Noticed the chroot check for udev and wonder about if a check would be helpful here too. Cheers Alf -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.20.0-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages udisks2 depends on: ii dbus 1.12.12-1 ii libacl12.2.52-3+b1 ii libatasmart4 0.19-5 ii libblockdev-fs22.20-6 ii libblockdev-loop2 2.20-6 ii libblockdev-part2 2.20-6 ii libblockdev-swap2 2.20-6 ii libblockdev-utils2 2.20-6 ii libblockdev2 2.20-6 ii libc6 2.28-4 ii libglib2.0-0 2.58.1-2 ii libgudev-1.0-0 232-2 ii libmount1 2.33-0.2 ii libpam-systemd 240-2 ii libpolkit-agent-1-00.105-23 ii libpolkit-gobject-1-0 0.105-23 ii libsystemd0240-2 ii libudisks2-0 2.8.1-3 ii parted 3.2-23 ii udev 240-2 Versions of packages udisks2 recommends: ii dosfstools 4.1-2 ii e2fsprogs1.44.5-1 ii eject2.1.5+deb1+cvs20081104-13.2 ii exfat-utils 1.3.0-1 ii libblockdev-crypto2 2.20-6 ii ntfs-3g 1:2017.3.23AR.3-2 ii policykit-1 0.105-23 Versions of packages udisks2 suggests: ii btrfs-progs 4.19.1-1 pn f2fs-tools ii libblockdev-mdraid2 2.20-6 ii mdadm4.1~rc1-4 pn nilfs-tools ii reiserfsprogs1:3.6.27-3 pn udftools pn udisks2-bcache ii udisks2-btrfs2.8.1-3 ii udisks2-lvm2 2.8.1-3 pn udisks2-vdo pn udisks2-zram ii xfsprogs 4.15.1-1 -- no debconf information
