1
schroot (1.4.15-1) unstable; urgency=low
1
schroot (1.4.16-1) unstable; urgency=low
3
3
Users upgrading from lenny should take note of the following
4
4
potentially incompatible changes which may require configuration
7
* In schroot 1.4.0, the naming of chroot configuration files under
8
/etc/schroot/chroot.d has been made stricter, in order to prevent
9
reading of editor backup files and dpkg conffile backups. It uses
10
the same naming rules as specified in run-parts(8) for the
11
--lsbsysinit option. Configuration files not matching the naming
12
rules will be ignored. If some of your chroots are not available
13
after upgrading to 1.4.0, this may be the reason. Simply rename
14
the files to a conforming name and they will become available.
7
* In schroot 1.4.16, the allowed names of chroot configuration files
8
under /etc/schroot/chroot.d, and also chroot and session names,
9
have been made stricter. This was done to prevent reading of
10
editor backup files and dpkg conffile backups, and also prevent
11
security exploits. The name may not contain a leading period
12
(‘.’). The characters ‘:’ (colon), ‘,’ (comma) and ‘/’ (forward
13
slash) are not permitted anywhere in the name. The name may also
14
not contain a trailing tilde ('~'). Configuration files not
15
matching the naming rules will be ignored. If some of your
16
chroots are not available after upgrading to 1.4.0, this may be
17
the reason. Simply rename the files to a conforming name and they
18
will become available. See schroot.conf(5) for more information.
16
20
* In schroot 1.4.1, the files 'script-defaults', 'mount-defaults',
17
21
'copyfiles-defaults' and 'nssdatabases-defaults' located in
25
29
'script-config' to 'script-defaults' in your chroot definitions,
26
30
this will require updating. If unset, no changes are required.
28
-- Roger Leigh <rleigh@debian.org> Fri, 22 Oct 2010 22:18:34 +0100
32
-- Roger Leigh <rleigh@debian.org> Sun, 05 Dec 2010 21:57:21 +0000
30
34
schroot (1.1.6-1) unstable; urgency=low