These were reported by flake8 as "F401 [...] imported but unused".

There is no need to create empty files for source-only uploads.

This does not yet do anything without changes to dak.conf.

Reported-by: NAdam D. Barratt <adsb@debian.org>

Too many uploads seem to include files that have no reasonable name.

For policy queues dak keeps the .buildinfo and .changes around until
the upload is processed.  As the uploads might already be sent to
buildds while waiting in the policy queue, the buildd upload might use
the same filename and end up getting rejected.  With this change, the
upload getting rejected should be the maintainer's upload.

When accepting an upload on the security archive, we need the
`.buildinfo` files to forward the upload to ftp-master.  For now,
store them along with the `.changes` in the queue directory.

Automatic debug packages are not listed in the source's Package-List
field, but are considered NEW in suites without an associated debug
suite (e.g. jessie).

While arch:all binNMUs might work for some packages, they still tend
to create problems due to versioned dependencies using

  arch-all-package (= ${source:Version})

as these will be broken by the binNMU.  To avoid these, we reject
arch:all binNMUs for now.

This is intended to be used to forbid uploads to policy queues and build
queues which would result in confusing results.  While we already have a
"reject" option in the dak.conf's SuiteMappings, having the option in
the database means we don't have to edit dak.conf when configuring new
suites.

Another usecase will be the "unstable" suite for Debian Ports: here we
want to import the source packages (and arch:all) from the main archive
and only accept binary uploads.  Additional source packages must go into
the "unreleased-*" suites.  This was not possible via SuiteMappings.

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

Debug packages are exempt from NEW if the target suite has a seperate
debug suite.  However the code checked if the target's override suite
had a debug suite...  For the Debian archive this went unnoticed as
experimental's override suite is unstable and both suites have a
seperate debug suite.
Reported-by: NMatthias Klumpp <mak@debian.org>

We want to allow debug packages without overrides.

To: debian-dak@lists.debian.org
Cc: Julien Cristau <jcristau@debian.org>
Date: Wed,  2 Dec 2015 08:01:37 +0100 (14 hours, 9 minutes, 8 seconds ago)
Resent-From: debian-dak@lists.debian.org

We have it readily available, and most scripts try to get it back from
the changes file anyway.

This makes things consistent for the scripts, so they won't get confused
by aliases (due to codenames or suite mappings) depending on whatever is
in the .changes file.
Signed-off-by: NJulien Cristau <jcristau@debian.org>
Signed-off-by: NJoerg Jaspert <joerg@debian.org>

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

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

Use the input_filename that was introduced in
64292a3e

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.

This should make moving packages between components (e.g. packages
moving from non-free to main) less painful.

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

This allows to eventually drop old entries from the signature_history
table.