Differences between revisions 28 and 29
Revision 28 as of 2014-10-27 14:10:40
Size: 4470
Editor: TobiasFrost
Comment: split link
Revision 29 as of 2015-12-23 16:31:42
Size: 4267
Editor: ?AGWA
Comment: Remove remark that source-only uploads are not allowed, since the archive supports source-only uploads now.
Deletions are marked like this. Additions are marked like this.
Line 38: Line 38:
 * No source-only uploads: probably you are used to source-only uploads since the days you were using debian mentors, but as a DM, if you are uploading to Debian's FTP site, it must be a binary upload.

New Debian Maintainer Tutorial

Key Changes

The debian-maintainers keyring is updated with a new version of the debian-keyring package. Its keys are not kept in sync with the keyservers. All changes to the debian-maintainers keyring are done by the Debian keyring maintainers in their git tree. Simple updates to keys (new UIDs, updated expiry dates) should be sent via HKP to keyring.debian.org:

gpg --keyserver keyring.debian.org --send-key <mykeyid>

The update will then be folded into the active DM keyring on the next keyring promote (usually at least once a month).

Note that the keyring maintainers are not the appropriate people to contact about getting your initial key into the DM keyring. The DM team make the decisions about adding new keys and will then request the addition by the keyring maintainers.

Annual ping

Debian Maintainers must reconfirm their interest annually to keep their keys in the debian-maintainers keyring by filing a signed bug report against the debian-maintainers pseudo package.

Key replacement/removal

Follow the instructions on keyring.debian.org - email keyring@rt.debian.org with "Debian RT" as part of the subject (plus something descriptive). You will need to inline sign your email; RT unfortunately mangles PGP/MIME signatures.

For key replacement please read (and follow!) the rules for key replacement in the Debian keyring. In particular your new key will need signed by at least 2 DDs and the request either needs to be signed by one of those keys or your old key (assuming the request for replacement isn't due to compromise).

Uploading packages

Once you have your key in the debian-maintainers keyring, you will be able to upload packages, where the following conditions hold:

This tutorial explains how a DebianMaintainer (DM) would upload to Debian, it assumes that one is already familiar with tools like debsign & dput.

  • Can you upload yet ? Once dak has your key, it will send a mail to debian-project for announcing the keyring update and you will be allowed to upload.

  • When you build the package in a chroot environment, for example using sbuild, remember to use the -s option (--source) in order to include the source; if you use dpkg-buildpackage, make sure not to use -B option. Once the <foo>.changes is created, sign it with debsign -k<yourUIDkey> <foo>.changes and check its contents: it should refer to the .dsc, the .diff.gz or .debian.tar.gz., the .deb, and the .orig.tar.{bz2,gz} (for a -1 version).

  • Upload to either ftp-master or ftp-eu: the default dput configuration in /etc/dput.cf would upload to ftp-master. The configuration sections for ftp-master and ftp-eu are included here for convenience:

fqdn                    = ftp.upload.debian.org
incoming                = /pub/UploadQueue/
login                   = anonymous
allow_dcut              = 1
method                  = ftp

# http://lists.debian.org/debian-project/2009/05/msg00036.html
fqdn                    = ftp.eu.upload.debian.org
method                  = ftp
incoming                = /pub/UploadQueue/
login                   = anonymous
allow_dcut              = 1

Access to Porter Machines

Sometimes you would like to investigate something on one of the DebianMachines. For instance, a build failure on a specific hardware architecture (i.e. sparc, ia64, etc). To request access to a porter machine, please refer to http://dsa.debian.org/doc/guest-account/.