[Bug 1334886] [NEW] /home not mounted, causes schroot errors

[Alex Chiang]

Public bug reported:

achiang at trusty:~$ mk-sbuild --skip-proposed utopic
[...]
Done building utopic-amd64.

 To CHANGE the golden image: sudo schroot -c source:utopic-amd64 -u root
 To ENTER an image snapshot: schroot -c utopic-amd64
 To BUILD within a snapshot: sbuild -A -d utopic-amd64 PACKAGE*.dsc

achiang at trusty:~$ schroot -c utopic-amd64
W: Failed to change to directory ‘/home/achiang’: No such file or directory
I: The directory does not exist inside the chroot.  Use the --directory option to run the command in a different directory.
W: Falling back to directory ‘/’
(utopic-amd64)achiang at trusty:/$ logout

###

achiang at trusty:~$ dpkg -l | grep ubuntu-dev-tools
ii  ubuntu-dev-tools                                      0.153                                               all          useful tools for Ubuntu developers

###

This is due to setting the profile incorrectly:

achiang at trusty:/etc/schroot/chroot.d$ grep profile sbuild-utopic-amd64 
profile=sbuild

achiang at trusty:/etc/schroot$ diff -Nur default/fstab sbuild/fstab 
--- default/fstab	2014-04-01 07:34:06.000000000 -0700
+++ sbuild/fstab	2014-04-01 07:34:06.000000000 -0700
@@ -5,16 +5,8 @@
 # <file system> <mount point>   <type>  <options>       <dump>  <pass>
 /proc           /proc           none    rw,bind         0       0
 /sys            /sys            none    rw,bind         0       0
-/dev            /dev            none    rw,bind         0       0
 /dev/pts        /dev/pts        none    rw,bind         0       0
-/home           /home           none    rw,bind         0       0
-/tmp            /tmp            none    rw,bind         0       0
-
-# It may be desirable to have access to /run, especially if you wish
-# to run additional services in the chroot.  However, note that this
-# may potentially cause undesirable behaviour on upgrades, such as
-# killing services on the host.
-#/run           /run            none    rw,bind         0       0
-#/run/lock      /run/lock       none    rw,bind         0       0
-#/dev/shm       /dev/shm        none    rw,bind         0       0
-#/run/shm       /run/shm        none    rw,bind         0       0
+tmpfs           /dev/shm        tmpfs   defaults        0       0
+# Mount a large scratch space for the build, so we don't use up
+# space on an LVM snapshot of the chroot itself.
+/var/lib/sbuild/build  /build   none    rw,bind         0       0

###

Problem probably introduced here:

ubuntu-dev-tools (0.149) unstable; urgency=low

  [ Marc Deslauriers ]
  * mk-sbuild: allow specifying the schroot profile.
  * ubuntutools/config.py: properly handle name being None.

  [ Loïc Minier ]
  * ubuntutools.config: decode developer names with the current locale's
    encoding and add corresponding test; fixes handling of non-ascii names.

  [ Adam Gandelman ]
  * backportpackage: Fix destination for --dont-sign option. (LP: #1183985)

  [ Evan Broder ]
  * Only conclude that we don't need an orig tarball if we're sent to the
    librarian (as opposed to the login page from a private PPA).
    (LP: #1106429)

 -- Benjamin Drung <bdrung at debian.org>  Tue, 13 Aug 2013 23:12:42 +0200

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-dev-tools 0.153
ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jun 26 15:43:30 2014
InstallationDate: Installed on 2014-04-22 (64 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: ubuntu-dev-tools
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-dev-tools (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug trusty

-- 
You received this bug notification because you are a member of MOTU,
which is subscribed to ubuntu-dev-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1334886

Title:
  /home not mounted, causes schroot errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1334886/+subscriptions