Firstly, subscribe to debian-devel if you haven't already.
Send the word subscribe
in the Subject of a mail to
debian-devel-REQUEST@lists.debian.org. In case of problems
contact the list administrator, Anders Chrigstrom ac@netg.se.
You should to subscribe and lurk for a bit before doing any coding, and you should post about your intentions to work on something to avoid duplicated effort.
If you do not have a PGP key yet generate one. You should probably read the PGP manual, as it has much important information which is critical to its security. Many more security failures are due to human error than to software failure or high-powered spy techniques.
If you live in a country where use of cryptography even for signing is forbidden then please contact us so we can make special arrangements. This does not apply in France, where I believe only encryption and not signing is forbidden.
master.debian.org
, Simon Shapiro
shimon@i-connect.net, the mailing list administrator, Anders
Chrigstrom ac@netg.se and the dpkg maintainer, Ian
Jackson ijackson@gnu.ai.mit.edu.
The message should say what you've done and who you are, and should
ask for an account on master and to be subscribed to
debian-private (the developers-only mailing list). It should
contain your PGP key (extracted using pgp -kxa
) for the database
of keys which is shipped with dpkg.
When you have your personal account on master log in and
transfer the files to
/home/Debian/ftp/private/project/Incoming
. You cannot upload
to Incoming on master using anonymous FTP.
You can also upload files to Incoming via a cron-driven
upload queue in Europe on chiark.chu.cam.ac.uk
. For details
connect to chiark using anonymous FTP and read
/pub/debian/private/project/README.how-to-upload
.
.changes
files
.changes
file which gives directions for its
handling. This is usually generated by dpkg-genchanges.This file is a control file with the following fields:
Format
Date
Source
Binary
Architecture
Version
Distribution
Urgency
Maintainer
Description
Changes
Files
All of them are mandatory for a Debian upload. See the list of control fields in the dpkg programmers' manual for the contents of these fields.
The first time a version is uploaded which corresponds to a particular
upstream version the original source tarfile should be uploaded and
included in the .changes
file; subsequent times the very same
tarfile should be used to build the new diffs and .dsc
files, and
it need not then be uploaded.
By default dpkg-genchanges and dpkg-buildpackage will
include the original source tarfile if and only if the Debian revision
part of the source version number is 0
or 1
, indicating a
new upstream version. This behaviour may be modified by using
-sa
to always include it or -sd
to always leave it out.
If no original source is included in the upload then the original
source tarfile used by dpkg-source when constructing the
.dsc
file and diff to be uploaded must be byte-for-byte
identical with the one already in the archive. If there is some
reason why this is not the case then the new version of the original
source should be uploaded, possibly by using the -sa
flag.
debian-changes
. The announcement should give the (source)
package name and version number, and a very short summary of the
changes, in the Subject field, and should contain the
PGP-signed .changes
file. Some additional explanatory text may
be added before the start of the .changes
file.
If a package is released with Distribution: experimental
the
announcement should be posted to debian-devel
instead.
lists.debian.org
. Mail
debian-
foo-REQUEST@lists.debian.org
[9] with the word
subscribe
in the Subject to subscribe or unsubscribe
to
unsubscribe.
When replying to messages on the mailing list, please do not send a
carbon copy (CC
- this does not mean `courtesy copy') to the
original poster. Anyone who posts to a mailing list should read it to
see the responses.
As ever on the net, please trim down the quoting of articles you're replying to. In general, please adhere to the usual conventions for posting messages.