touch-packages team mailing list archive

[Serge Hallyn <1427264@xxxxxxxxxxxxxxxxxx>]

Note you use slave and private somewhat interchangeably above.  Which
you want to use will depend on the behavior you want to see if the uesr
tries to umount something under /home. If there might be devices or
remotes which need to be freed, then you'll wan to use slave so that the
chroot can't pin the source.  If you actually want the mount to stick
around in the chroot then you'll want to use private.

-- 
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/1427264

Title:
  using ecryptfs, creating frameworks fail to bind mount issues

Status in click package in Ubuntu:
  Triaged

Bug description:
  Using vivid creating framework fails for ecryptfs users, the issue is
  similar to bug #769595

  The userdir is mounted in a way which makes unmounts fail

  "E: 10mount: umount: /var/lib/schroot/mount/click-ubuntu-sdk-14.10
  -armhf-ec6aaf62-31e0-47e9-b2f8-73f0b038fb4d/home/user: target is busy
  E: 10mount: (In some cases useful info about processes that E:
  10mount: use the device is found by lsof(8) or fuser(1).) "

  changing the fstab line to be "/home/user /home/user      none
  rw,bind        0       0" workarounds the issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1427264/+subscriptions