diff options
author | Ian Jackson <ijackson@chiark.greenend.org.uk> | 2019-07-07 00:09:14 +0100 |
---|---|---|
committer | Ian Jackson <ijackson@chiark.greenend.org.uk> | 2019-07-07 11:18:17 +0100 |
commit | 31ce46f54f9f8a6ead0105db68646277944b940d (patch) | |
tree | 86f52b7246b575ffb459a340e4c069ec355e15f0 /tests | |
parent | e421140af47f0d64e018100b91b79c48fe83f729 (diff) |
git-debpush: Defend against git-deborig #931509
Without this, when git-deborig fails and #931509 isn't fixed,
git-debpush will silently exit with a nonzero exit status which is
very unfriendly.
With this change it does something like this:
git-debpush: git-deborig failed; maybe try git-debpush --upstream=TAG
fatal: Invalid object name 'refs/tags/couldn't find any of the following tags'.
It then exits status 127. This is obviously daft, but making this
any better is even more complex.
When git-deborig is fixed it will do this:
couldn't find any of the following tags: 1.0, v1.0, upstream/1.0
tell me a tag or branch head to make an orig.tar from: git deborig --just-print '--version=1.0-1' COMMITTISH
git-debpush: git-deborig failed; maybe try git-debpush --upstream=TAG
which is still not brilliant but I guess it will do.
The downside, if it is one, is that we lose git-deborig's original
exit status.
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
Acked-by: Sean Whitton <spwhitton@spwhitton.name>
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions