Dear Maintainer,

I am a developer of Kali Linux (https://wiki.debian.org/Derivatives/Census/Kali) and am upgrading
our version of oclHashcat-plus. The tool contains kernels for each type of GPU it supports so
the resultant tarball is very large even after removing the Windows executables from the 7z
archive available on their site.

When I try to import the tarball via git-import-orig, it fails with the following:

error: excessively large binary delta for /tmp/pristine-tar.Oo4GbRUxeB/origtarball
(Please consider filing a bug report.)
pristine-tar: failed to generate delta

Pasted below is the complete sequence of steps from downloading the tool right through to
the failed import.

dookie@kali:/tmp/work$ gbp-clone git@git.kali.org:packages/oclhashcat-plus --all
Branch pristine-tar set up to track remote branch pristine-tar from origin.
Branch upstream set up to track remote branch upstream from origin.
dookie@kali:/tmp/work$ wget https://hashcat.net/files/oclHashcat-plus-0.15.7z --quiet
dookie@kali:/tmp/work$ 7z x oclHashcat-plus-0.15.7z -y > /dev/null
dookie@kali:/tmp/work$ rm -rf oclHashcat-plus-0.15/*.exe oclHashcat-plus-0.15/*.cmd
dookie@kali:/tmp/work$ mv oclHashcat-plus-0.15 oclhashcat-plus-0.15
dookie@kali:/tmp/work$ tar czpf oclhashcat-plus_0.15.orig.tar.gz oclhashcat-plus-0.15/
dookie@kali:/tmp/work$ cd oclhashcat-plus
dookie@kali:/tmp/work/oclhashcat-plus$ git-import-orig ../oclhashcat-plus_0.15.orig.tar.gz
What is the upstream version? [0.15]
gbp:info: Importing '../oclhashcat-plus_0.15.orig.tar.gz' to branch 'upstream'...
gbp:info: Source package is oclhashcat-plus
gbp:info: Upstream version is 0.15
xdelta: warning: no matches found in from file, patch will apply without it
error: excessively large binary delta for /tmp/pristine-tar.Oo4GbRUxeB/origtarball
(Please consider filing a bug report.)
pristine-tar: failed to generate delta
gbp:error: Couldn't commit to 'pristine-tar' with upstream 'upstream': /usr/bin/pristine-tar returned 1
gbp:error: Import of ../oclhashcat-plus_0.15.orig.tar.gz failed
dookie@kali:/tmp/work/oclhashcat-plus$ ls -lh ../oclhashcat-plus_0.15.orig.tar.gz
-rw-r--r-- 1 dookie dookie 435M Aug 26 14:57 ../oclhashcat-plus_0.15.orig.tar.gz

I can workaround this with the --no-pristine-tar option so I chose "normal" priority for the bug.

Best regards,
Devon (dookie) Kearns
dookie[shift-2]kali.org

Devon (dookie) Kearns wrote:

You have untarred the tarball to oclhashcat-plus-0.15, but you are
running pristine-tar inside a different directory, oclhashcat-plus.

If pristine-tar cannot find all the files in this directory that are in
the tarball, it has to use a binary delta to represent them. Apparently
the directory you ran it in contains none of the files at all, so the
delta is too large.

Besides not using pristine-tar correctly, there is absolutely no reason
to be using it at all in this case. oclhashcat-plus_0.15.orig.tar.gz is
a file you have created; it is not the original file from upstream. So
there is little or no value in being able to regenerate that file from
your source checkout.