Bug#851640: --debbuildopts not propagated anymore to cowbuilder

[Vincent Bernat]

 ❦ 17 janvier 2017 16:12 +0100, Mattia Rizzolo <mattia at debian.org> :

> On Tue, Jan 17, 2017 at 01:41:58PM +0100, Vincent Bernat wrote:
>> Cannot test right now, but at the end of the build, cowbuilder complain
>> about not being able to unmount /dev/shm because it's busy. I assumed
>> this was because the use of a more recent pbuilder turned into a symlink
>> or the reverse.
>
> umh, though that's still not supposed to happen.  From what I could see
> mount and umount follow symlinks without any problem:

Here is what I get at the end:

I: Copying back the cached apt archive contents
I: unmounting /etc/pbuilder/deps filesystem
I: unmounting dev/pts filesystem
I: unmounting run/shm filesystem
W: Could not unmount run/shm: umount: /var/lib/systems/pbuilder/build/cow.24417/run/shm: target is busy
        (In some cases useful info about processes that
         use the device is found by lsof(8) or fuser(1).)
W: Retrying to unmount run/shm in 5s
umount: /var/lib/systems/pbuilder/build/cow.24417/run/shm: target is busy
        (In some cases useful info about processes that
         use the device is found by lsof(8) or fuser(1).)

  Could not unmount run/shm, some programs might
  still be using files in /proc (klogd?).
  Please check and kill these processes manually
  so that I can unmount run/shm.  Last umount error was:
umount: /var/lib/systems/pbuilder/build/cow.24417/run/shm: target is busy
        (In some cases useful info about processes that
         use the device is found by lsof(8) or fuser(1).)

In mount, I have:

/proc on /var/lib/systems/pbuilder/build/cow.24417/proc type proc (rw,relatime)
sysfs on /var/lib/systems/pbuilder/build/cow.24417/sys type sysfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,relatime)

/var/lib/systems/pbuilder/build/cow.24417/dev/shm is a real directory,
but not a mount point (same device as
/var/lib/systems/pbuilder/build/cow.24417/dev).

  File: /var/lib/systems/pbuilder/build/cow.24417/dev/shm
  Size: 4096            Blocks: 8          IO Block: 4096   directory
Device: fd07h/64775d    Inode: 3802032     Links: 2
Access: (0777/drwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2017-01-17 07:14:17.547683772 +0100
Modify: 2017-01-17 07:14:17.547683772 +0100
Change: 2017-01-17 20:26:16.047469684 +0100
 Birth: -

/var/lib/systems/pbuilder/build/cow.24417/run/shm is a symlink to
/dev/shm, so that explains the problem:

  File: /var/lib/systems/pbuilder/build/cow.24417/run/shm -> /dev/shm
  Size: 8               Blocks: 0          IO Block: 4096   symbolic link
Device: fd07h/64775d    Inode: 2492773     Links: 3
Access: (0777/lrwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2017-01-17 07:14:17.551683739 +0100
Modify: 2017-01-17 07:14:17.551683739 +0100
Change: 2017-01-17 20:26:16.043469722 +0100
 Birth: -

After upgrading pbuilder to 0.228, tmpfs is mounted over .../dev/shm, so
the symlink is fine.

The chroot is a jessie-backports chroot BTW.
-- 
Indent to show the logical structure of a program.
            - The Elements of Programming Style (Kernighan & Plauger)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pbuilder-maint/attachments/20170117/e1fd4a55/attachment-0001.sig>