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>

This method install the source into an archive without adding it to
any suite. It is intended to be used to import extra source packages
(i.e. those referenced only by Built-Using).

This allows retrieving files using a temporary name, but to install
them into the archive using their proper name.

If the same source or binary package is uploaded again, the
fingerprint and changed_by might be different if some other person
signed the new .changes (or if there is no .changes). We still want to
be able to import such packages without error, retaining the
attributes already present.

Release files use different field names for checksum fields and the
set of allowed filenames is larger (slashes are allowed). This patch
allows switching the regexp used to validate filenames and the fields
for checksums to allow using parse_file_list not only for .dsc files,
but also for Release files.

I really would like to get rid of mapped components on security-master...

For example override.stretch.extra.* does not exist. Not ignoring this
pattern results in an output file containing an asterisk.

Signed-off-by: NLuca Falavigna <dktrkranz@debian.org>

Do not mention details like how often Contents indices are updates as
these depend on the suite and have changed.

Also remove the description on how to use grep to search these files.

Signed-off-by: NLuca Falavigna <dktrkranz@debian.org>

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