Setting up udev (219-4ubuntu3) ...
A chroot environment has been detected, udev not started.
/var/lib/dpkg/info/udev.postinst: 35: /var/lib/dpkg/info/udev.postinst: update-initramfs: not found
dpkg: error processing package udev (--configure):
subprocess installed post-installation script returned error exit status 127
Errors were encountered while processing:
udev
E: Sub-process /usr/bin/dpkg returned an error code (1)
But back to the test failure... this test has been running successfully on all platforms for a long time (3+ years). It's possible that the test itself is racy and that a recent change in a different package has exposed that. Do we know when this test first started failing (and ideally what changes triggered it (kernel/libc))?
mk-sbuild now fails with a different error:
Setting up udev (219-4ubuntu3) ... dpkg/info/ udev.postinst: 35: /var/lib/ dpkg/info/ udev.postinst: update-initramfs: not found
A chroot environment has been detected, udev not started.
/var/lib/
dpkg: error processing package udev (--configure):
subprocess installed post-installation script returned error exit status 127
Errors were encountered while processing:
udev
E: Sub-process /usr/bin/dpkg returned an error code (1)
But back to the test failure... this test has been running successfully on all platforms for a long time (3+ years). It's possible that the test itself is racy and that a recent change in a different package has exposed that. Do we know when this test first started failing (and ideally what changes triggered it (kernel/libc))?