[Bug 1319790] [NEW] Support HOME != /home in click chroot
Michael Vogt
michael.vogt at canonical.com
Thu May 15 11:42:52 UTC 2014
Public bug reported:
The custom /etc/schroot/click/fstab used by click to drive schroot leads
to problems if the user is using a different HOME than /home. This will
lead e.g. "click chroot -aarmhf create " to fail when it tries to run
"/finish.sh" after the initial debootstrap because the CWD is not
available inside the schroot.
This might be the reason for some of the bugreport around click chroot
(like
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1299732/comments/4).
I'm not quite sure what the best course of action is here, my current approach would be to generate the file on each
click chroot invocation instead of shipping a static file.
** Affects: click (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to click in Ubuntu.
https://bugs.launchpad.net/bugs/1319790
Title:
Support HOME != /home in click chroot
Status in “click” package in Ubuntu:
New
Bug description:
The custom /etc/schroot/click/fstab used by click to drive schroot
leads to problems if the user is using a different HOME than /home.
This will lead e.g. "click chroot -aarmhf create " to fail when it
tries to run "/finish.sh" after the initial debootstrap because the
CWD is not available inside the schroot.
This might be the reason for some of the bugreport around click chroot
(like
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1299732/comments/4).
I'm not quite sure what the best course of action is here, my current approach would be to generate the file on each
click chroot invocation instead of shipping a static file.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1319790/+subscriptions
More information about the foundations-bugs
mailing list