On Sun, Feb 2, 2014 at 8:54 AM, Luis Ibanez <[email protected]> wrote:

> On Sun, Feb 2, 2014 at 4:54 AM, Andreas Tille <[email protected]> wrote:
>
>> > xdelta: warning: no matches found in from file, patch will apply
>> without it
>> >
>> > error: excessively large binary delta for
>> > /tmp/pristine-tar.ETnVfcsL8q/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
>>
>> I have not seen this error message (did you filed a bug as it said)?
>>
>> When I was running into trouble with larger tarballs previously it
>> helped to use
>>
>>     TMPDIR=/var/tmp git import-orig --pristine-tar <tarball>
>>
>> -----------------------
>
>
> Andreas,
>
> I'm trying your suggestion now, and also reading more
> about git-import-orig.
>
> [...]
>
>  I'll keep exploring...
>
>


No luck yet...

Here is what I have tried:


$  git branch -a

* master
  upstream
  remotes/origin/HEAD -> origin/master
  remotes/origin/master
  remotes/origin/upstream


$  TMPDIR=/var/tmp git import-orig --pristine-tar
../../Replication/vista-foia_0.20130405.orig.tar.gz

What is the upstream version? [0.20130405]
gbp:info: Importing '../../Replication/vista-foia_0.20130405.orig.tar.gz'
to branch 'upstream'...
gbp:info: Source package is vista-foia
gbp:info: Upstream version is 0.20130405
xdelta: warning: no matches found in from file, patch will apply without it
error: excessively large binary delta for
/var/tmp/pristine-tar.bC1wZJOkad/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 ../../Replication/vista-foia_0.20130405.orig.tar.gz
failed:


$  pwd
/home/ibanez/src/debian-med/SecondPass/PristineTar/vista-foia-0.20130405



It may well be, that I'm not properly
matching the directory name yet....


      Luis

Reply via email to