|author||Ian Jackson <firstname.lastname@example.org>||2018-06-21 01:00:41 +0100|
|committer||Ian Jackson <email@example.com>||2018-06-21 01:11:11 +0100|
dgit: Non-noop git fetch is not available with --dry-run, so fail
When fetch or push wants git fetch (other than in a situation where it happes to be a noop) but --dry-run was specified, we would loop with a false coplaint about git fetch. False, because we didn't actually run git fetch so of course it didn't do anything. Instead, fail with an explanation. Closes:#871317. This does not occur, and we do not fail, if git-fetch would be a no-op. We can tell when this is the case, because we use git-ls-remote too. This leads to one suggestion for a workaround for the user, which is to do a not --dry-run fetch first. Signed-off-by: Ian Jackson <firstname.lastname@example.org>
Diffstat (limited to 'debian')
1 files changed, 4 insertions, 0 deletions
diff --git a/debian/changelog b/debian/changelog
index 3216e4a..2c30556 100644
@@ -10,6 +10,10 @@ dgit (5.2~) unstable; urgency=medium
* When quilt fixup fails because of discrepancies, print a
git diff rune which will show them. Closes:#865446.
+ * When fetch or push wants git fetch (other than in a situation where it
+ happes to be a noop) but --dry-run was specified, fail with an
+ explanation, rather than looping with a false coplaint about git
+ fetch. Closes:#871317.