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>

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: NMark Hymers <mhy@debian.org>

Signed-off-by: NMark Hymers <mhy@debian.org>

This should help with avoiding removal of source-only uploads where no
binary was built yet.

28903fa3 tried to allow temporary
files used by rsync, however these started with a dot and were still
deleted.

The patch in 9a1cfa78 is not enough to
start accepting *.asc.

Bug: https://bugs.debian.org/759401

Two regexes were defined twice.

Source packages should be allowed to include an optional upstream
signature in a *.asc file.

rsync appends a suffix while uploading and renames them later. We
don't want to remove in-progress uploads so we have to allow these.

For any debug packages, redirect binary packages to the binary debug
suite if set, otherwise install as normal.

This is the first step in creating a debug deb suite for the archive,
and diverts debs that would be added to a suite into the debug suite
linked.

In the event the suite does not support diverting debug debs, the
process-new routine will accept the package into the target suite.

 Alter the schema to add `debugsuite` to the suite table, to point at
 the suite to copy debug debs to.

 In particular, we should tolerate .deb packages that are in the
 Files, but are not present in the Binary package listing, since
 adding them into debian/control is a pretty bad idea.

 debhelper (currently, this will be default later), when givin
 `DH_BUILD_DDEBS=1` will build DH_BUILD_DDEBS that are in the Files
 list, named foo-dbgsym.

 The check now validates that the -dbgsym package corresponds to
 a package that *is* listed in the Binary package listing, and in
 the section "debug".

The new subcommand allows importing packages from an existing
repository. It is currently intended to be used on Debian Ports to
import source and arch:all packages from the main archive.

There are still several places that need work.

Use the input_filename that was introduced in
64292a3e

The InRelease file is currently signed using multiple keys and we want
to be able to verify its signature. So allow multiple signatures as
long as all of them are valid.

For uploads (.changes files) we still require that only a single
signature is present. This is currently enforced by the 'fingerprint',
'primary_fingerprint' and 'signature_id' accessors.

Requested-by: NEnrico Zini <enrico@enricozini.org>