Maybe this check should eventually be dropped?

debianqueued used to send early warnings about invalid uploads, but
relied on being able to (ab)use the setgid bit on the .changes file to
keep track for which uploads it has already complained. If it was
unable to set the setgid bit, it would send mails every run.

This change removes the early warnings. A mail will only be sent when
debianqueued gives up on the upload.

We only allowed 'unstable' or 'experimental'.
Signed-off-by: NJulien Cristau <jcristau@debian.org>
Signed-off-by: NAnsgar Burchardt <ansgar@debian.org>

Currently /testing is a symlink, but this means the same content is
available under different addresses.

Signed-off-by: NJoerg Jaspert <joerg@debian.org>

Signed-off-by: NJoerg Jaspert <joerg@debian.org>

This tag was removed from Lintian (2.5.33).

It looks like we actually had a week without uploads to the security
archive and the Release file expired.

Add option which makes make-maintainer print the maintainer data to
stdout instead of writing it to files.

This is used in Tanglu to feed it's BTS

* lamby/misc-fixes-796786:
  daklib/utils.py: mandantory -> mandatory spelling error
  daliblib/dak_exceptions: Add trailing comma to avoid future VCS noise
  tests/test_packagelist.py: make executable
  dalkib/dbconn.py: Mention which version is installed in sqlalchemy check
  dak/copy_installer.py: Include which directory doesn't exist in exception

* lamby/improve-parse-changes-tests-796787:
  tests/test_parse_changes.py: Move test to ParseDscTestCase as we call with dsc_file=1
  tests/test_parse_changes.py: Test that an contentless .dsc fails correctly
  tests/test_parse_changes.py: Actually use the blank file test fixture
  tests/test_parse_changes.py: Rewrite loose and difficult-to-use-correctly assertFails
  tests/test_parse_changes.py: Actually set dsc_file=1 when testing .dsc

It would be better if the README files were generated from a template
file, but this is better than nothing.

This issue caused dak to not generate hashes for uncompressed Contents
files for some architectures in some components.  A bit of context,
there were up to 4 Contents files per architecture:

 * Contents-ARCH
 * main/Contents-ARCH
 * contrib/Contents-ARCH
 * non-free/Contents-ARCH

Any */Contents-ARCH that appeared on the filesystem AFTER the legacy
"Contents-ARCH" would be ignored, because generate-releases used the
wrong key to check if the file was already in uncompnotseen.
Signed-off-by: NNiels Thykier <niels@thykier.net>

Signed-off-by: NNiels Thykier <niels@thykier.net>

When merging two groups of auto-decruftable packages, remember to
register all members of the combined group so dak can do a reverse
look up later.
Signed-off-by: NNiels Thykier <niels@thykier.net>

Whilst the packaging is obviously not for use, I'm finding it extremely
useful at least having the Build-Depends at a point where it will run the
tests.

It might be tempting to remove debian/ entirely, but Build-Depends is
just too useful for specifying, well, dependencies that tools such as
mk-build-deps can consume just like other packages.
Signed-off-by: NChris Lamb <lamby@debian.org>

Signed-off-by: NJoerg Jaspert <joerg@debian.org>

Signed-off-by: NJoerg Jaspert <joerg@debian.org>

Signed-off-by: NJoerg Jaspert <joerg@debian.org>

* nthykier/checksumed-contents:
  generate_releases: Remove unneeded .keys() calls
  Always provide a checksum of uncompressed Contents files

Signed-off-by: NNiels Thykier <niels@thykier.net>

The new version of apt in experimental will insist on having the
checksum of the uncompressed Contents file, if it is to download the
Contents file.
Signed-off-by: NNiels Thykier <niels@thykier.net>

Signed-off-by: NChris Lamb <lamby@debian.org>

Was added in 47955ee9 but never actually
used.
Signed-off-by: NChris Lamb <lamby@debian.org>

Signed-off-by: NChris Lamb <lamby@debian.org>

Signed-off-by: NChris Lamb <lamby@debian.org>

Signed-off-by: NChris Lamb <lamby@debian.org>

Signed-off-by: NChris Lamb <lamby@debian.org>