suspicious activity, or whatever, send an email to
<email>debian-admin@debian.org</email>. Problems with the Debian FTP
archive generally need to be reported as bugs against the
-<package>ftp.debian.org</package> pseudo-package, but also see the
-procedures in <ref id="archive-manip">.
+<package>ftp.debian.org</package> pseudo-package or an email to
+<email>ftpmaster@debian.org</email>, but also see the procedures in
+<ref id="archive-manip">.
<sect1 id="servers-www">The WWW servers
<p>
<p>
If you have a slow network connection to <tt/master/, there are
alternatives. One is to upload files to <tt/Incoming/ via a
-cron-driven upload queue in Europe on <tt/chiark/. For details connect
+upload queue in Europe on <tt/chiark/. For details connect
to <ftpsite>ftp.chiark.greenend.org.uk</ftpsite> using anonymous FTP
and read
<ftppath>/pub/debian/private/project/README.how-to-upload</ftppath>.
<sect1>Uploads via <tt/erlangen/
<p>
-Another cron-driven upload queue is available in Germany: just upload
+Another upload queue is available in Germany: just upload
the files via anonymous FTP to <url
id="ftp://ftp.uni-erlangen.de/pub/Linux/debian/UploadQueue">.
<p>
properly. Then, in there, try building your package from scratch with
<tt>dpkg-buildpackage</tt>.
<item>
-Make sure you don't ship your binary package with the
+Make sure you don't ship your source package with the
<file>debian/files</file> or <file>debian/substvars</file> files.
They should be removed by the `clean' target of
<file>debian/rules</file>.
<item>
Don't rely on <prgn>egcc</prgn> being available; don't rely on
<prgn>gcc</prgn> being a certain version.
+ <item>
+Make sure your debian/rules contains separate ``binary-arch'' and
+``binary-indep'' targets, as the Debian Packaging Manual requires.
+Make sure that both targets work independently, that is, that you can
+call the target without having called the other before. To test this,
+try to run <tt>dpkg-buildpackage -b</tt>.
</enumlist>
<sect1 id="buildd">
<heading><package>buildd</package>
<p>
-<package/buildd/ is not yet available! However, it collects a number
-of as yet unpackaged components which are currently in production
-(such as <prgn/debbuild/ and <prgn/wanna-build/.
- <p>
The <package/buildd/ system is used as a distributed, client-server
build distribution system. It is usually used in conjunction with
<em/auto-builders/, which are ``slave'' hosts which simply check out
out'' a source package (usually one which cannot yet be autobuilt) and
work on it.
<p>
+<package/buildd/ is not yet available as a package; however, most
+porting efforts are either using it currently or planning to use it in
+the near future. It collects a number of as yet unpackaged components
+which are currently very useful and in use continually, such as
+<prgn/sbuild/ and <prgn/wanna-build/.
+ <p>
We are very excited about this system, since it potentially has so
many uses. Independent development groups can use the system for
different sub-flavors of Debian, which may or may not really be of