[buildd-tools-devel] Bug#567409: Bug#567409: /etc/schroot/chroot.d no longer used for configuration?

[Andreas Beckmann]

Hi Roger,

Roger Leigh wrote:
> % ls -l /etc/schroot/chroot.d
> total 9
> -rw------- 1 root root 158 Dec 12 13:12 etch-amd64-sbuild
> -rw------- 1 root root 205 Dec 12 13:12 lenny-amd64-sbuild
> -rw------- 1 root root 288 Jan 27 09:07 sid-amd64-sbuild
> -rw------- 1 root root 203 Jan 26 10:15 sid-amd64-sbuild.4zMkRO
> -rw-r--r-- 1 root root 217 Dec 12 13:12 sid-block
> -rw-r--r-- 1 root root 150 Dec 12 13:12 sid-file
> -rw------- 1 root root 151 Dec 12 13:12 sid-loop
> -rw------- 1 root root 261 Dec 12 13:12 sid-snap
> -rw------- 1 root root 196 Dec 12 13:13 squeeze-amd64-sbuild

Ah, different naming scheme. No .conf suffix.

> Could you run "schroot -l -v --debug=notice" and let me know what you

$ schroot -l -v --debug=notice
D(1): Loading config file: /etc/schroot/schroot.conf
D(1): Loading data file: /etc/schroot/schroot.conf
D(1): Loading config directory: /etc/schroot/chroot.d
W: No chroots are defined in '/etc/schroot/schroot.conf'

If I rename my config from sid-i386.conf to sid-i386 everything works
again. Reading chroot(1) again describes run-parts --lsbsysinit as the
naming pattern scanned in /etc/schroot/chroot.d ... Probably introduced
in 1.3.0-1 (I had 1.2.3-1+b1 installed previously):

  * schroot now ignores backup files (including dpkg conffile backups)
    in /etc/schroot/chroot.d (Closes: #513307, #496629).


Andreas