Activity log for bug #1844504

Date Who What changed Old value New value Message
2019-09-18 08:58:31 Colin Watson bug added bug
2019-09-18 08:58:39 Colin Watson nominated for series Ubuntu Xenial
2019-09-18 08:58:39 Colin Watson bug task added livecd-rootfs (Ubuntu Xenial)
2019-09-18 08:58:49 Colin Watson livecd-rootfs (Ubuntu Xenial): status New In Progress
2019-09-18 08:58:51 Colin Watson livecd-rootfs (Ubuntu Xenial): importance Undecided High
2019-09-18 08:58:53 Colin Watson livecd-rootfs (Ubuntu Xenial): assignee Colin Watson (cjwatson)
2019-09-18 08:58:57 Colin Watson bug task deleted livecd-rootfs (Ubuntu)
2019-09-18 08:59:32 Launchpad Janitor merge proposal linked https://code.launchpad.net/~cjwatson/livecd-rootfs/+git/livecd-rootfs/+merge/372869
2019-09-18 09:03:31 Colin Watson livecd-rootfs (Ubuntu Xenial): status In Progress Fix Committed
2019-09-18 09:09:31 Colin Watson 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) I'm fairly sure that this is because the new livecd-rootfs-built xenial buildd images include makedev, which was Priority: required in xenial (but not in later releases) but not in the historical buildd chroots. The best approach is likely to be to just take makedev out again. 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) I'm fairly sure that this is because the new livecd-rootfs-built xenial buildd base images include makedev, which was Priority: required in xenial (but not in later releases) but not in the historical buildd chroots. The best approach is likely to be to just take makedev out again. [Test Case] Run a buildd image build and make sure that makedev is gone from the resulting images. If possible, run a mir build and test that it works now, though this is likely to be arduous; we probably don't need to put too much effort into this given that reverting buildd base image upgrades is now a quick operation. (We can't upgrade the base images until this is in -updates.) [Regression Potential] This is mostly a reversion to a previous known-working state, so I'm not too worried, but we need to make sure that buildd images are still buildable and keep a close eye on builds immediately after upgrading to new images.
2019-09-18 13:48:15 Adam Conrad bug added subscriber Ubuntu Stable Release Updates Team
2019-09-18 13:48:17 Adam Conrad bug added subscriber SRU Verification
2019-09-18 13:48:20 Adam Conrad tags verification-needed verification-needed-xenial
2019-09-20 14:33:29 Eric Desrochers bug added subscriber Eric Desrochers
2019-09-24 13:35:52 Launchpad Janitor merge proposal linked https://code.launchpad.net/~cjwatson/livecd-rootfs/+git/livecd-rootfs/+merge/373141
2019-09-24 15:01:30 Mauricio Faria de Oliveira bug added subscriber Mauricio Faria de Oliveira
2019-09-26 09:51:46 Colin Watson 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) I'm fairly sure that this is because the new livecd-rootfs-built xenial buildd base images include makedev, which was Priority: required in xenial (but not in later releases) but not in the historical buildd chroots. The best approach is likely to be to just take makedev out again. [Test Case] Run a buildd image build and make sure that makedev is gone from the resulting images. If possible, run a mir build and test that it works now, though this is likely to be arduous; we probably don't need to put too much effort into this given that reverting buildd base image upgrades is now a quick operation. (We can't upgrade the base images until this is in -updates.) [Regression Potential] This is mostly a reversion to a previous known-working state, so I'm not too worried, but we need to make sure that buildd images are still buildable and keep a close eye on builds immediately after upgrading to new images. 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.
2019-09-26 09:55:03 Colin Watson summary xenial buildd chroots shouldn't have makedev openpty fails in xenial buildd chroots
2019-09-26 19:20:03 Mauricio Faria de Oliveira tags verification-needed verification-needed-xenial verification-done-xenial verification-needed
2019-09-27 09:40:02 Colin Watson tags verification-done-xenial verification-needed verification-done-xenial
2019-10-01 16:52:57 Brian Murray removed subscriber Ubuntu Stable Release Updates Team
2019-10-01 16:52:53 Launchpad Janitor livecd-rootfs (Ubuntu Xenial): status Fix Committed Fix Released
2019-10-01 16:52:53 Launchpad Janitor bug watch added https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817236