From: joy Date: Mon, 18 Dec 2000 23:13:19 +0000 (+0000) Subject: updated regarding va->klecker move, and www->people move, changed most X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=commitdiff_plain;h=921736ab9f42d1294884f7741fb7ad5668caf0ad updated regarding va->klecker move, and www->people move, changed most mentions of dinstall to a generic term "archive maintenance software", removed full path to it because it is in PATH now, mentioned "dak" and "katie" (somewhat vaguely), changed week to month regarding FTP archive waiting time since that\'s more often the case, and changed weeks to hours regarding Maintainers file updates since that\'s also more often the case now, updated some URLs to entities, s/debian-doc/doc-debian/ git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@1073 313b444b-1b9f-4f58-a734-7bb04f332e8d --- diff --git a/developers-reference.sgml b/developers-reference.sgml index 132d55d..380a989 100644 --- a/developers-reference.sgml +++ b/developers-reference.sgml @@ -5,7 +5,7 @@ %commondata; - + @@ -486,17 +486,17 @@ an email to &email-ftpmaster;, but also see the procedures in The WWW server

The main web server, www.debian.org, is also known as -va.debian.org. All developers are given accounts on this +klecker.debian.org. All developers are given accounts on this machine.

If you have some Debian-specific information which you want to serve up on the web, you can do this by putting material in the -public_html directory under your home directory. You can -do this on va.debian.org. Any material you put in those areas +public_html directory under your home directory. You should +do this on klecker.debian.org. Any material you put in those areas are accessible via the URL -http://www.debian.org/~user-id/. -If necessary, you can use other Debian machines for this; the procedure -is analogous to the above. Please do not put any material on Debian +http://people.debian.org/~user-id/. +You should only use this particular location because it will be backed up, +whereas on other hosts it won't. Please do not put any material on Debian servers not relating to Debian, unless you have prior permission. Send mail to &email-debian-devel; if you have any questions.

@@ -509,7 +509,7 @@ else has already reported the problem on the The CVS server

-cvs.debian.org is also known as va.debian.org, +cvs.debian.org is also known as klecker.debian.org, discussed above. If you need to use a publically accessible CVS server, for instance, to help coordinate work on a package between many different developers, you can request a CVS area on the server. @@ -521,8 +521,7 @@ be accessed read-only via the Web at .

To request a CVS area, send a request via email to &email-debian-admin;. Include the name of the requested CVS area, -what va.debian.org user account should own the CVS root area, -and why you need it. +Debian account should own the CVS root area, and why you need it. Mirrors of Debian servers @@ -799,11 +798,11 @@ area, so that testers can get early access.

However, using experimental as a personal staging area is not always the best idea. You can't replace or upgrade the files in there -on your own (dinstall and the Debian archive maintainers -do that). Additionally, you'll have to remember to ask the archive +on your own (it is done with Debian archive maintenance software). +Additionally, you'll have to remember to ask the archive maintainers to delete the package once you have uploaded it to unstable. Using your personal web space on -va.debian.org is generally a better idea, so that you put +klecker.debian.org is generally a better idea, so that you put less strain on the Debian archive maintainers. @@ -1060,9 +1059,9 @@ defaults for uploading via ftp to ftp-master, use ssh or rsync. See and for more information.

-After uploading your package, you can check how dinstall will -process it by running dinstall on your changes file: -/org/ftp.debian.org/scripts/dinstall/dinstall -n foo.changes +After uploading your package, you can check how the archive maintenance +software will process it by running dinstall on your changes +file: dinstall -n foo.changes Uploading to non-us (pandora)

@@ -1076,11 +1075,9 @@ The program dupload comes with support for uploading to non-us; please refer to the documentation that comes with the program for details.

-Similar to the way it's done on ftp-master, you can check your -upload with: - -/org/non-us.debian.org/scripts/dinstall/dinstall -n foo.changes - +You can check your upload the same way it's done on ftp-master, +with: +dinstall -n foo.changes Uploads via chiark

@@ -1145,10 +1142,10 @@ anonymous FTP to . Announcing package uploads

When a package is uploaded, an announcement should be posted to one of -the ``debian-changes'' lists. This is now done automatically by -dinstall when it runs (usually once a day). You just need to -use a recent dpkg-dev (>= 1.4.1.2). The mail -generated by dinstall will contain the PGP/GPG signed +the ``debian-changes'' lists. This is now done automatically by the archive +maintenance software when it runs (usually once a day). You just need to use +a recent dpkg-dev (>= 1.4.1.2). The mail generated by +the archive maintenance software will contain the PGP/GPG signed .changes files that you uploaded with your package. Previously, dupload used to send those announcements, so please make sure that you configured your dupload not to @@ -1176,12 +1173,13 @@ announcement to the right list. See .

The Debian archive maintainers are responsible for handling package uploads. For the most part, uploads are automatically handled on a -daily basis by an archive maintenance tool called -dinstall. Specifically, updates to existing packages to +daily basis by archive maintenance tools `dak' +(also referred to as katie or dinstall). +Specifically, updates to existing packages to the `unstable' distribution are handled automatically. In other cases, notably new packages, placing the uploaded package into the distribution is handled manually. When uploads are handled manually, -the change to the archive may take up to a week to occur. Please be +the change to the archive may take up to a month to occur. Please be patient.

In any case, you will receive email notification indicating that the @@ -1500,10 +1498,8 @@ of things you should check or be aware of. Don't set architecture to a value other than ``all'' or ``any'' unless you really mean it. In too many cases, maintainers don't follow the -instructions in the . Setting your architecture to ``i386'' -is usually incorrect. +instructions in the . Setting your architecture to ``i386'' is usually incorrect. Make sure your source package is correct. Do dpkg-source -x package.dsc to make sure your source package unpacks @@ -1697,13 +1693,13 @@ installation log sent to you when the package is installed into the archive. If for some reason the old location of the package remains, file a bug against ftp.debian.org asking that the old location be removed. Give details on what you did, since it might be -a dinstall bug. +a bug in the archive maintenance software.

If, on the other hand, you need to change the subsection of one of your packages (e.g., ``devel'', ``admin''), the procedure is slightly different. Correct the subsection as found in the control -file of the package, and reupload that. Also, you'll need to update -the override file, as described in . +file of the package, and reupload that. Also, you'll need to get the +override file updated, as described in . Removing packages @@ -1776,9 +1772,10 @@ without leave), post a query to &email-debian-private;. If you take over an old package, you probably want to be listed as the package's official maintainer in the bug system. This will happen automatically once you upload a new version with an updated -Maintainer: field, although it can take a couple of weeks. If -you do not expect to upload a new version for a while, send an email -to &email-override; so that bug reports will go to you right away. +Maintainer: field, although it can take a few hours after the +upload is done. If you do not expect to upload a new version for a while, +send an email to &email-override; so that bug reports will go to you +right away. @@ -1793,9 +1790,9 @@ packages. The BTS contains all the open bugs against your packages.

Maintainers interact with the BTS via email addresses at bugs.debian.org. Documentation on available commands can be -found at , or, if you have -installed the debian-doc package, you can look at -the local files /usr/doc/debian/bug-*. +found at , or, if you have installed the +doc-debian package, you can look at the local files +/usr/doc/debian/bug-*.

Some find it useful to get periodic reports on open bugs. You can add a cron job such as the following if you want to get a weekly email @@ -1846,10 +1843,10 @@ been accepted into the Debian archive. Therefore, once you get notification that your updated package has been installed into the archive, you can and should close the bug in the BTS.

-If you are using a new version of dpkg-dev and you -do your changelog entry properly, dinstall will close the -bugs automatically. All you have to do is follow a certain syntax -in your debian/changelog file: +If you are using a new version of dpkg-dev and you do +your changelog entry properly, the archive maintenance software will close +the bugs automatically. All you have to do is follow a certain syntax in +your debian/changelog file: acme-cannon (3.1415) unstable; urgency=low