|author||Ian Jackson <firstname.lastname@example.org>||2018-07-01 11:08:21 +0100|
|committer||Ian Jackson <email@example.com>||2018-07-05 13:45:13 +0100|
dgit: Check that entirely-new uploads to Debian are not source-only-uploads.
Avoids the user pushing things that will inevitably be REJECTed. We end up introducing some new config and force options to support this. We do not reuse test_source_only_changes, as it doesn't have quite the right shape (in particular, it sometimes blithers on stdout). Also arguably it is better to look, specifically, for .debs, for the purpose of this test. This requires a new archive protocol method. We implement it for ftpmasterapi (where it is actualliy needed) and dummycatapi (where we need it for tests.) Implementing it for madisonish methods would be easy. For aptget, it would probably involve iterating over suites, and not be adviseable. Closes:#801435. Signed-off-by: Ian Jackson <firstname.lastname@example.org>
Diffstat (limited to 'dgit.1')
1 files changed, 13 insertions, 0 deletions
@@ -1050,6 +1050,17 @@ The result is a fresh import,
discarding the git history
that the person who pushed that .dsc was working with.
+Carry on and
+even though dgit thinks your distro does not permit that.
+Carry on and do a source-only upload,
+without any binaries,
+even though dgit thinks your distro does not permit that,
+or does not permit that in this situation.
Carry on even if
dgit thinks that your git tree contains changes
@@ -1226,6 +1237,8 @@ or when pushing and
.BI dgit-distro. distro .rewrite-map-enable
+.BR dgit-distro. \fIdistro\fR .source-only-uploads " " ok | always | never | not-wholly-new
.BI dgit.dsc-url-proto-ok. protocol