openpty fails in xenial buildd chroots
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
livecd-rootfs (Ubuntu) | ||||||
Xenial |
Fix Released
|
High
|
Colin Watson |
Bug Description
xenial mir builds recently started failing as follows:
ERROR:
util-linux fails similarly.
This is because the new livecd-rootfs-built xenial buildd base images have the bug described in https:/
[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.
Related branches
- Adam Conrad (community): Approve
-
Diff: 44 lines (+15/-4)3 files modifieddebian/changelog (+8/-0)
live-build/auto/config (+0/-4)
live-build/buildd/hooks/00-no-makedev.chroot_early (+7/-0)
- Adam Conrad (community): Approve
-
Diff: 30 lines (+11/-0)2 files modifieddebian/changelog (+7/-0)
live-build/auto/config (+4/-0)
Changed in livecd-rootfs (Ubuntu Xenial): | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Colin Watson (cjwatson) |
no longer affects: | livecd-rootfs (Ubuntu) |
Changed in livecd-rootfs (Ubuntu Xenial): | |
status: | In Progress → Fix Committed |
description: | updated |
Hello Colin, or anyone else affected,
Accepted livecd-rootfs into xenial-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ livecd- rootfs/ 2.408.52 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification- needed- xenial to verification- done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- xenial. In either case, without details of your testing we will not be able to proceed.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance for helping!
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.