This bug was fixed in the package livecd-rootfs - 2.408.54 --------------- livecd-rootfs (2.408.54) xenial; urgency=medium
* Revert exclusion of makedev from buildd chroots, as it turned out not to be the problem. Instead, fix up /dev/ptmx to be a character device node rather than a symlink to /dev/pts/ptmx, in line with the discussion in https://bugs.debian.org/817236; I think this is safer than cherry-picking the fix to debootstrap at this point in a stable release cycle (LP: #1844504). livecd-rootfs (2.408.53) xenial; urgency=medium * Fix exclusion of makedev from buildd chroots; debootstrap doesn't respect --exclude for "Priority: required" packages, so we have to purge makedev later (LP: #1844504). livecd-rootfs (2.408.52) xenial; urgency=medium * Exclude makedev from buildd chroots, since it was historically excluded and apparently breaks some builds (e.g. mir; LP: #1844504). livecd-rootfs (2.408.51) xenial; urgency=medium * ubuntu-cpc: Only produce explicitly specified artifacts (LP: #1837254) -- Colin Watson <cjwat...@ubuntu.com> Thu, 26 Sep 2019 10:53:23 +0100 ** Changed in: livecd-rootfs (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Bug watch added: Debian Bug tracker #817236 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817236 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1844504 Title: openpty fails in xenial buildd chroots Status in livecd-rootfs source package in Xenial: Fix Released Bug description: xenial mir builds recently started failing as follows: https://launchpadlibrarian.net/442878565/buildlog_ubuntu-xenial- amd64.mir_1.4.0+dev83-g939ca20348-0ubuntu16.04_BUILDING.txt.gz ERROR:src/umockdev.c:4991:umockdev_testbed_create_node_for_device: assertion failed: (Linux.openpty (out ptym, out ptys, ptyname_array, null, null) == 0) util-linux fails similarly. This is because the new livecd-rootfs-built xenial buildd base images have the bug described in https://bugs.debian.org/817236: /dev/ptmx is a symlink to /dev/pts/ptmx, and sbuild doesn't use the mount options necessary to make that usable. The simplest solution appears to be to fix up /dev/ptmx in buildd images to be a character device node rather than a symlink (newer versions of debootstrap do that too, but that's a riskier change). [Test Case] Run a buildd image build and make sure that the resulting images have /dev/ptmx as a mode 666 character device node rather than a symlink. Run a util-linux build with the resulting image and test that it works now. [Regression Potential] We need to make sure that buildd images are still buildable and keep a close eye on builds immediately after upgrading to new images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/xenial/+source/livecd-rootfs/+bug/1844504/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp