2
These are some useful utilities for accessing/maintaining the
5
The <chroot> arg used by most scripts has two forms:
7
· s,stable,-t,testing,-u,unstable
9
- a symlink in the current directory, chroot-{stable,testing,unstable}
10
pointing to the chroot must exist
12
· any other distribution name
14
- in this case the argument is parsed to try and determine
15
the distribution, for those scripts that need it, for example:
17
# checkchroot stable-security
19
- CHROOT=/usr/local/chroot/chroot-stable-security
20
- DIST=stable-security so it can find the ref-stable-security
25
------------------------------------------
28
Aborts the current dpkg-buildpackage process.
31
------------------------------------------
34
Shows how the contents of the chroot differs from a reference.
35
This requires the ref-{stable,testing,unstable} files to be in the
38
# cp /usr/share/doc/sbuild/configs/ref-{stable,testing,unstable} \
41
The chroots should only include essential & build-essential
42
packages and the extra packages that sbuild needs: apt, fakeroot,
43
ssmtp. Please check that the references are accurate for
46
------------------------------------------
47
chr-hold <chroot> pkg [pkg..]
48
chr-unhold <chroot> pkg [pkg..]
50
For changing the hold/install status of packages in the chroots.
52
------------------------------------------
53
chrapt <chroot> apt-get|apt-cache arguments
55
Runs apt-get or apt-cache in the chroot from base.
57
------------------------------------------
62
------------------------------------------
66
Scripts to keep the chroots up to date. Can be run as cron jobs
69
------------------------------------------
70
add_sbuild_user /path/to/chroot <dist> <user>
72
A script to add a new user to a chroot. See
73
/usr/share/doc/sbuild/README-buildd.chroot.
75
------------------------------------------
78
3
A shell script for mutt & vi to handle the build logs that