[buildd-tools-devel] Bug#626826: sbuild: /var/lock being absolute symlink -> "Another sbuild process (...) is currently using the build chroot"

[Jakub Wilk]

Package: sbuild
Version: 0.62.2-1

Due to the advent of /run, I manually changed layout of my chroots, so 
that they look like this:

$ ls -ld /srv/chroots/unstable-i386/{var,run}/lock
drwxrwxrwt 2 root root 4096 May 15 01:19 /srv/chroots/unstable-i386/run/lock
lrwxrwxrwx 1 root root    9 May 15 14:59 /srv/chroots/unstable-i386/var/lock -> /run/lock

Unfortunately, sbuild is not happy with such a layout, and I cannot 
build more than one package in parallel (even though I use cloned 
chroots, so it should be possible). I get this message instead:

Another sbuild process (job zlib_1.2.3.4.dfsg-3, pid 5534 by user sbuild) is currently using the build chroot; waiting...

It looks like sbuild uses /run/lock from the outside of the chroot. When 
I changed the symlink to a relative one, the problem disappeared.


-- System Information:
Debian Release: wheezy/sid
   APT prefers unstable
   APT policy: (990, 'unstable'), (500, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages sbuild depends on:
ii  adduser                       3.112+nmu2 add and remove users and groups
ii  libc6                         2.13-4     Embedded GNU C Library: Shared lib
ii  libgcc1                       1:4.6.0-7  GCC support library
ii  libsbuild-perl                0.62.2-1   Tool for building Debian binary pa
ii  libstdc++6                    4.6.0-7    The GNU Standard C++ Library v3
ii  perl                          5.12.3-6   Larry Wall's Practical Extraction 
ii  perl-modules                  5.12.3-6   Core Perl modules

-- 
Jakub Wilk