Having a command makes it easier to manage upload permissions for the
signing service.

for now, exit 0. suboptimal, doesnt run the afteraction thingies.

* deploy:
  Also keep dak-code at main archive

See merge request ftp-team/dak!1

The old implementation had all-by-and and any-by-all disabled in fear of
problems.  Do the same for now in the new implementation.

This also runs the new selection code in the normal mode and lists the
differences into the log for later inspection.

This code can run in no-action mode and provide a complete result in
table format.

This code actually needs changes done in step one (removal of arch:any)
to do the source and arch:all removal step.

Really only useful at the beginning of a tasks file, to ensure that
all action will always be rerun.

The name will also be used for the name of the archive which is useful
to have fixed for tests.

TBD: proofread, fixup, enhance, ...

Postgres already checks non-null constraints for us.  It is not needed
to duplicate some of these checks in Python.

We only fetch stuff, so work against origin/master or use git ls-tree,
no need to have a second directory.

The code only goes live at the git checkout line at the end anyways.

Policy allows a changes file's urgency to have a trailing comment
(separated by a space).  If such a comment exists, the urgency needs to
be extracted so it is properly parsed.  This ensures the urgency is
propagated properly.
Signed-off-by: NJames McCoy <jamessan@debian.org>

Handle gracefully nonexisting architectures during removals (Closes: #816712)

See merge request ftp-team/dak!5