Package: devscripts
Version: 2.23.4
Severity: important
An example where this currently fails is
g...@salsa.debian.org:gnome-team/glib.git
I have noticed this with multiple repositories, usually when there is
more than one orig.tar files
pravi@ilvala2:~/forge/gnome-team/glib$ origtargz
pristine-tar: successfully generated
../glib2.0_2.78.0.orig-unicode-data.tar.xz
fatal: ambiguous argument
'5d3bcca0ea769dad9fd32d32274931e7bb443b0d^{tree}': unknown revision or
path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
fatal: not a valid object name:
5d3bcca0ea769dad9fd32d32274931e7bb443b0d^{tree}
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
pristine-tar: command failed: git archive --format=tar
5d3bcca0ea769dad9fd32d32274931e7bb443b0d\^\{tree\} | (cd
'/tmp/pristine-tar.GClS2GBRhr' && tar x)
pravi@ilvala2:~/forge/gnome-team/glib$ gbp export-orig --pristine-tar
gbp:info: Creating /home/pravi/forge/gnome-team/glib2.0_2.78.0.orig.tar.xz
gbp:info: Creating
/home/pravi/forge/gnome-team/glib2.0_2.78.0.orig-unicode-data.tar.xz
