We used the remaining parameters before which is somewhat confusing.

This reverts commit 196b3433.

This should prevent changes to the {src,bin}_contents tables and result
in all helper processes seeing the same data.

This makes it less error-prone to switch compression methods: the files
that are no longer generated are automatically removed. Before they had
to be removed manually.

which is helpful when there are no .gz/.bz2 ones around to
look at.

* juliank/master:
  Only generate binary checksum fields for the requested ones
  Only generate fields in Sources for requested checksums
Signed-off-by: NJoerg Jaspert <joerg@debian.org>

This is the second step. As we are simply concatenating things,
we can just concatenate an empty string if we do not want a
checksum.

We make use of the fact that STRING_AGG ignores NULL values
when joining the values, so we do not get empty lines in there.

Mind, its still configured and exists, need to remove that, but this
should stop pushing the mirrors and changing it around.

Which makes running it inside a while loop a pain.
(Its ssh could use a -n,but this works too)

This just prepares the mirror tree and pushes the changes to the
mirrors.  It is intended to be used for point releases or in other
situations where a manual mirror push is needed.

Upstream tarballs usually come with detached signatures, which would be
useful to have in the source package, as an additional check that could
be performed to verify its integrity and provenance.

dpkg-source supports this since 1.17.20.

Closes: #759401

To: debian-dak@lists.debian.org
Cc: kibi@debian.org, Julien Cristau <jcristau@debian.org>
Date: Tue, 19 Jan 2016 11:40:01 +0100 (12 hours, 2 minutes, 47 seconds ago)
Resent-From: debian-dak@lists.debian.org

stable-proposed-updates is called "proposed-updates" in projectb, so
that's what we pass to the byhand script.  It shouldn't be turned into
"proposed-updates-proposed-updates".
Signed-off-by: NJulien Cristau <jcristau@debian.org>

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.

If a binary-only upload including debug packages gets accepted from a
policy queue, the source might be missing from the debug suite.
Reported-by: NMatthias Klumpp <mak@debian.org>

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>

Especially proper adding to the TMPFILES variable to get rid of em
again.