1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
|
Source: schroot
Section: admin
Priority: optional
Maintainer: Debian buildd-tools Developers <buildd-tools-devel@lists.alioth.debian.org>
Uploaders: Roger Leigh <rleigh@debian.org>
Build-Depends: debhelper (>= 7.0.0), autotools-dev, pkg-config, libpam0g-dev, uuid-dev [!kfreebsd-any], liblockdev1-dev, libboost-dev (>= 1.46.0), libboost-program-options-dev (>= 1.46.0), libboost-regex-dev (>= 1.46.0), libboost-filesystem-dev (>= 1.46.0), gettext, libcppunit-dev
Build-Depends-Indep: doxygen, graphviz
Standards-Version: 3.9.1
Vcs-Browser: http://git.debian.org/?p=buildd-tools/schroot.git
Vcs-Git: git://git.debian.org/git/buildd-tools/schroot
Package: schroot-common
Architecture: all
Depends: ${misc:Depends}
Replaces: schroot (<< 1.1.1)
Description: common files for schroot
schroot allows users to execute commands or interactive shells in
different chroots. Any number of named chroots may be created, and
access permissions given to each, including root access for normal
users, on a per-user or per-group basis. Additionally, schroot can
switch to a different user in the chroot, using PAM for
authentication and authorisation. All operations are logged for
security.
.
This package provides translations for localisation of schroot
programs.
Package: libsbuild-dev
Architecture: any
Section: libdevel
Depends: ${misc:Depends}, pkg-config (>= 0.14.0)
Suggests: schroot-dbg, libsbuild-doc
Description: development files for the Debian source builder
sbuild provides facilities to manage and access chroots, as part of
schroot.
.
schroot allows users to execute commands or interactive shells in
different chroots. Any number of named chroots may be created, and
access permissions given to each, including root access for normal
users, on a per-user or per-group basis. Additionally, schroot can
switch to a different user in the chroot, using PAM for
authentication and authorisation. All operations are logged for
security.
.
This package contains the header files and static library needed to
develop applications which make use of sbuild. Once the API and ABI
are stable, a shared library will replace the static library.
Package: schroot-dbg
Architecture: any
Section: debug
Priority: extra
Depends: ${misc:Depends}, schroot (= ${binary:Version}) | dchroot (= ${binary:Version})
| dchroot-dsa (= ${binary:Version})
Conflicts: schroot (<< ${binary:Version}), schroot (>> ${binary:Version}),
dchroot (<< ${binary:Version}), dchroot (>>${binary:Version}),
dchroot-dsa (<< ${binary:Version}), dchroot-dsa (>>${binary:Version})
Description: schroot, dchroot and dchroot-dsa debuggging symbols
sbuild provides facilities to manage and access chroots, as part of
schroot.
.
schroot allows users to execute commands or interactive shells in
different chroots. Any number of named chroots may be created, and
access permissions given to each, including root access for normal
users, on a per-user or per-group basis. Additionally, schroot can
switch to a different user in the chroot, using PAM for
authentication and authorisation. All operations are logged for
security.
.
This package contains debugging symbols for the schroot, dchroot
and dchroot-dsa packages.
Package: libsbuild-doc
Architecture: all
Section: doc
Depends: ${misc:Depends}
Suggests: libsbuild-dev
Description: development documentation for the Debian source builder
sbuild provides facilities to manage and access chroots, as part of
schroot.
.
schroot allows users to execute commands or interactive shells in
different chroots. Any number of named chroots may be created, and
access permissions given to each, including root access for normal
users, on a per-user or per-group basis. Additionally, schroot can
switch to a different user in the chroot, using PAM for
authentication and authorisation. All operations are logged for
security.
.
This package contains the API documentation needed to develop
applications which make use of sbuild.
Package: schroot
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, schroot-common (=${source:Version})
Conflicts: dchroot (<< 0.13)
Enhances: sbuild
Suggests: debootstrap, lvm2, btrfs-tools, unzip, aufs-modules | unionfs-modules
Description: Execute commands in a chroot environment
schroot allows users to execute commands or interactive shells in
different chroots. Any number of named chroots may be created, and
access permissions given to each, including root access for normal
users, on a per-user or per-group basis. Additionally, schroot can
switch to a different user in the chroot, using PAM for
authentication and authorisation. All operations are logged for
security.
.
Several different types of chroot are supported, including normal
directories in the filesystem, and also block devices. Sessions,
persistent chroots created on the fly from files (tar with optional
compression and zip) and LVM snapshots are also supported.
.
schroot supports kernel personalities, allowing the programs run
inside the chroot to have a different personality. For example,
running 32-bit chroots on 64-bit systems, or even running binaries
from alternative operating systems such as SVR4 or Xenix.
.
schroot also integrates with sbuild, to allow building packages with
all supported chroot types, including session-managed chroot types
such as LVM snapshots.
.
schroot shares most of its options with dchroot, but offers vastly
more functionality.
Package: dchroot
Architecture: any
Suggests: debootstrap
Depends: ${misc:Depends}, schroot (= ${binary:Version}), ${shlibs:Depends}, schroot-common (=${source:Version})
Description: Execute commands in a chroot environment
dchroot allows users to execute commands or interactive shells in
different chroots. A typical installation might provide 'stable',
'testing' and 'unstable' chroots. Users can move between chroots as
necessary.
.
NOTE: the schroot package provides a better implementation of
dchroot. In particular:
* dchroot quoting issues are not present. dchroot runs commands in
the chroot with -c option of the user's default shell; when
multiple command options are used, the options are concatenated
together, separated by spaces. This concatenation breaks shell
quoting.
* schroot implements fine-grained access controls based on users
and groups, either of which may be granted the ability to gain
root access to the chroot if required.
Using schroot will avoid these issues, as well as provide additional
functionality dchroot does not possess.
Package: dchroot-dsa
Architecture: any
Suggests: debootstrap
Depends: ${misc:Depends}, schroot (= ${binary:Version}), ${shlibs:Depends}, schroot-common (=${source:Version})
Description: Execute commands in a chroot environment
dchroot allows users to execute commands or interactive shells in
different chroots. A typical installation might provide 'stable',
'testing' and 'unstable' chroots. Users can move between chroots as
necessary.
.
This package provides a dchroot-dsa binary which is compatible with
the command-line options and configuration file format used by the
dchroot-dsa dchroot maintained by the Debian System Administrators
used on machines administered for the Debian Project.
.
NOTE: the schroot package provides a better implementation of
dchroot-dsa. In particular:
* dchroot-dsa only allows the specification of a single command with
an absolute path, and no options may be used with the command;
schroot allows the use of relative and absolute paths with no
limit on the number of options.
* dchroot-dsa only allows one chroot to be used at once; schroot will
allow the use of as many chroots as desired.
* dchroot-dsa allows access to be restricted to named users; schroot
implements finer-grained access controls based on users and groups,
either of which may be granted the ability to gain root access to
the chroot if required.
Using schroot will avoid these issues, as well as provide significant
additional functionality dchroot-dsa does not possess.
|
