1 Chroot Install Request Guidelines
2 =================================
4 <small>(stored here for reference,
5 [original announcement is available](http://lists.debian.org/debian-devel-announce/2010/05/msg00002.html))</small>
7 In order to make dealing with install requests easier for us please
8 observe the following guidelines:
10 1. Install requests should be directed to `debian-admin@lists.debian.org` (and
11 only there) and the subject should be formed as following:
13 Subject: [b-d][$arch|$machine] foobar ($chroot)
15 Please start all mails concerning porting chroots with the [b-d] (short for
18 Either choose [$arch] (eg. hppa) or a specific [$machine] (eg. paer) and tell
19 us which package's build dependencies should be installed.
21 If you omit $chroot we will assume you meant sid/unstable.
23 So build-deps for openoffice.org on smetana in the lenny chroot would look
26 Subject: [b-d][smetana] openoffice.org (lenny)
28 This kind of subject tagging will make it easier for us to quickly classify
29 mail in the admin mailbox, allowing us to sort it into heaps that DSA has to
30 handle and into requests that our helpers can most likely deal with.
32 2. Please refrain giving us a long list of packages to install if possible.
33 That is, if a simple `apt-get build-dep $foo` will satisfy your request then
34 all we require is the value of $foo.
36 If however the source package isn't yet listed in the chroot's SourcesĀ· file
37 (because it's new or in experimental for instance) that won't be possible. In
38 that case you will have to provide a list of packages for us to install.
39 Please cut it down so that it is copy/pastable to an apt-get install command
40 line, i.e. do not include any `foo | bar` constructs or version constraints