The Debian Archive Operations Team
Infrastructure
Host: fasolo.debian.org with the aliases ftp-master.debian.org (FIXME) and incoming.debian.org
Website: https://ftp-master.debian.org/ (FIXME)
Code repository: https://salsa.debian.org/ftp-team (FIXME)
Documentation: developers-reference
Wiki: https://ftp-master.debian.org/wiki/ (FIXME)
Unix group: (FIXME: Are these groups helpful in this Wiki at all?)
- Ftpmaster: 802 (debadmin)
- Ftpteam: 1217 (ftpteam)
- Ftptrainees: 1247 (ftptrainee)
- Services handled by the team:
/srv/ftp-master.debian.org/ on ftp-master.debian.org, aka the main copy of the Debian archive as well as its copy on mirror.ftp-master.debian.org (FIXME)
- /srv/ftp.debian.org/ on ftp-master.debian.org (FIXME)
- /srv/incoming.debian.org/ on incoming.debian.org
- Various upload queues on .debian.org hosts, for example ssh.upload.debian.org.
- security.debian.org
- backports.debian.org
Interacting with the team
Email contact: <ftpmaster@debian.org> (FIXME)
Request tracker: https://bugs.debian.org/ftp.debian.org (pseudo package) (FIXME)
Public IRC channel: #debian-ftp on irc.debian.org (OFTC) (FIXME)
Task description
This team, commonly referred to as Archive team, oversees and maintains the well-being of Debian's official package repositories.
Operating the archive
The Archive team (FIXME: Archivars?) are responsible for maintaining the infrastructure required to support the archive. This takes the form of the scripts used for processing uploaded packages, but also the flow of packages between distributions.
One thing that the Archive team is explicitly not responsible for is the maintenance of the mirror network. This is handled by the mirror team.
Supporting the Release Managers
The Archive team does not determine policy for the flow of packages from unstable to testing, nor they run the scripts that control the process. Similarly, the Archive team does not determine which packages should make up stable point releases.
However, they are responsible for ensuring that the packages move into/are available in the various releases correctly (as defined by the Release Managers).
Of course, the Archive team is also responsible for the final movement of packages from testing into stable at the time of release, following the instructions of the release managers.
Accepting and rejecting packages
When a package is uploaded to the unstable or experimental suite, the Archive team is responsible if it falls into these categories:
- If it is a new version of an existing package and adds no new binary packages, it is moved into the package pool automatically.
- Some uploads are not traditional Debian packages (installer images, for example) and are classified as BYHAND to indicate that they require manual processing.
Four times a day (see count-down), the archive is updated to reflect new packages, with the changes then distributed across the mirrors.
Maintaining the state of packages and the archive
The Archive Operations Team members have the opportunity to alter the priority and section of binary packages at any time. This information is stored in the overrides file, which in turn is used to generate the packages file in the archive. Historically, this was required because packages did not contain priority and section information. Nowadays this allows a greater level of consistency in package placement, and is most useful when new sections (and, in theory, new priorities) are created.
Package removal is also important. This falls into two classes - binary packages that are no longer required because the source package no longer builds them, and requests for removals of packages. The archive is regularly scanned for binary packages that are no longer built or which are otherwise unnecessary, and the results are mailed daily to the Archive Team. After checking that this is intended, Archive Team members will then remove the package.
(FIXME_whole_paragraph) The standard way to request removal of a package is to file a bug against ftp.debian.org. This may be because of difficulties with the package license, because the maintainer no longer wishes the package to be in Debian or because there are legal issues associated with the package. In this case, the Archive Team members must manually remove the package.
Maintaining the Debian Archive Kit
Archive Team is the primary maintainer of the Debian Archive Kit (dak). The main git repository is available at https://salsa.debian.org/ftp-team/dak . Since git is a distributed version control system, everybody can contribute easily to dak. The development is coordinated via the debian-dak mailing list.
Summary
Overall, the Archive Team accepts responsibility for removing old packages and ensuring that the archive contains the correct packages in the correct place. While much of this work is automated, it still requires a large amount of vigilance, as well as effort to update the tools as the needs of the project change.
Get involved


If you know python you can also be of great help by contributing with patches to the dak code. The Archive team likes to merge patches! 

Ever wanted to have your pet feature in dak? Go and code it! (Well, write us first, to avoid double work or running in the totally wrong direction. Nobody likes to have to redo everything because the start was wrong). If you want to help out coding, our git repository is at https://salsa.debian.org/ftp-team/dak
Delegation
The Archive Operations Team are DPL delegates (as per Debian Constitution ยง8). The actual delegation text is available.
Previous announcements
2005-02, on debian-project - Roles and responsibilities of the FTPmaster team
2008-05, on debian-devel-announce - Bits from the FTP Master
2009-01, on debian-devel-announce - ftpmaster profils
2009-11, on debian-devel-announce - Bits from the ftp-team
2009-11, on debian-devel-announce - Bits from the FTP Master
2010-03, on debian-devel-announce - Bits from the FTP Master
2010-06, on debian-devel-announce - moving to archive.debian.org
2010-07, on debian-devel-announce - ftp-master/release move
2010-09, on debian-devel-announce - FTPMaster meeting, step1
2010-09, on debian-project - FTPMaster meeting, minutes
2013-07, on FTPTeam changes
2025-10, on The Archive Operations Team
