touch-packages team mailing list archive

[Launchpad Bug Tracker <1319790@xxxxxxxxxxxxxxxxxx>]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: click (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Confirmed

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