mount-chroot doesn't cope with swapped /dev/shm and /run/shm
Bug #1236722 reported by
Adam Conrad
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
launchpad-buildd |
Triaged
|
High
|
Unassigned |
Bug Description
Somewhere in the last cycle or two, /dev/shm and /run/shm were swapped, as was the symlink. This wasn't noticed on lp-buildd as all my old chroots were upgraded and didn't inherit the swap, but my new arm64 chroot was built with the inverse order and mount-chroot's mounting bits failed to setup a shm environment.
For now, I've made the arm64 chroot look like the others, but we need to fix this to test /dev/shm and /run/shm for linkiness versus directoryness and mount the one that's a directory, so we can support both old and new style setups.
Changed in launchpad-buildd: | |
status: | New → Triaged |
importance: | Undecided → High |
To post a comment you must log in.