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

This adds an option to dak rm to remove only the binaries that were built from
an outdated version of the specified source package.

This silences several warnings "W605 invalid escape sequence" reported
by newer versions of flake8.

The .changes file may no longer have a "Binary" field since
4c22c773 for source-only uploads.

One could look at the .dsc instead, but in the end this would need
duplicating more logic from archive.py to handle binaries not built in
Debian correctly.  Dropping the check makes binary-NEW uploads in the
deferred queue available, but that seems acceptable.

There is no need to suggest violence towards people that were nice to
Mormons.

The changes table requires a not NULL binaries column. But we should not
be requiring a Binary field for source-only uploads. There have been
other changes to accommodate that, but the schema still requires the
values, and uploading such .changes files returns this misleading
rejection message:

  source_version_arch.changes is already known.

from daklib/archive.py:_install_changes() due to an exception when
inserting the DBChange() into the database.

Creating a Changes object doesn't parse it immediately, so we
were not catching InvalidChangesException here. Force the
parsing so we can detect invalid changes and stop processing
them, otherwise process-upload explodes and no further changes
are processed after the broken one.

Use daklib.daksubprocess.check_output over do_command to prevent HTML tag wrapping. (Closes: #909252)

This was adding <pre>..</pre> tags which were then getting mangled by a
subsquent os.bath.basename into "pre> check for ...".

Thanks, Ansgar!

The sequence didn't exist on at least security-master.d.o.

The unique constraint suite_src_formats_suite_key also exists as primary
key constraint.  Alembic is not able to handle such duplicate indexes.