Fork from debian's dak
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Mark Hindley df67fa1739 Merge remote-tracking branch 'origin/master' into wip/test_merge 5 months ago
alembic silence warning "E305 expected 2 blank lines after class or function definition" 2 years ago
config config/debian/weekly.*: drop `gitcleanup` task 6 months ago
dak Merge remote-tracking branch 'origin/master' into wip/test_merge 5 months ago
daklib Merge remote-tracking branch 'origin/master' into wip/test_merge 5 months ago
dakweb dakweb: use imports compatible with Python3 7 months ago
debian CI: Skip intermediate coverage totals 6 months ago
docs docs: remove special NEW processing for security archive 7 months ago
integration-tests tests: Fix a section_end 6 months ago
scripts Revert " temporarily disable sync from ftp-master" 1 year ago
setup dak-setup: Cope with RUN_COVERAGE being unset 6 months ago
templates Include __MAINTAINER_FROM__ as a psuedoheader. Closes #950132 1 year ago
tests Add support for merged pdiffs 6 months ago
tools Merge remote-tracking branch 'origin/master' into wip/test_merge 5 months ago
.coveragerc .coveragerc: fix exclude pattern 6 months ago
.gitignore Update .gitignore to exclude more artifacts 2 years ago
.gitlab-ci.yml CI: Skip intermediate coverage totals 6 months ago
.nobackup .nobackup file to avoid the git getting a not-needed backup 3 years ago
COPYING Imported sources. 20 years ago Grammar: noun vs. verb 1 year ago
alembic.ini Add initial Alembic config 2 years ago
setup.cfg flake8: we want line breaks before binary operators 7 months ago

dak - Debian Archive Kit

dak is the collection of programs used to maintain the Debian project’s archives. It is highly optimized for the Debian project, though can be used by others too.

More reading

There are some manual pages and READMEs in the docs sub-directory. The TODO file is an incomplete list of things needing to be done.

There’s a mailing list for discussion, development of and help with dak. See:

for archives and details on how to subscribe.


We love to get patches for dak. Enhancements, bugfixes, make-code-nicer/easier, anything.

Merge requests

With dak being available at the Salsa Service, we now prefer receiving merge requests there. They allow simple reviews using the webinterface and also allow discussing (parts of) the code within the Salsa UI. They also allow much easier tracking the state of different requests than a mail on a list ever allows.

To create merge requests that, simply go to the Salsa project page, select Fork followed by the namespace you want to put it in (usually your private one). Then simply clone this fork and work it in, preferably in a branch named after whatever-you-are-doing.

When you are happy with what you coded, use the UI on Salsa to create a merge request from your feature branch, either using the web interface or by using e-mail, see the Gitlab MR documentation for details on this process.

Alternative to using Salsa

While we do prefer merge requests as described above, we also accept patches send by mail to our mailing list, see above for details on the list.

Set Up DAK

You can find more info about setting dak up inside the setup Folder and its README.


dak is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, a copy of which is provided under the name COPYING, or (at your option) any later version.