Package: git-buildpackage
Version: 0.6.0~git20120822
Severity: normal

Dear Maintainer,

I just caught git-import-dscs continuing after what should have been a
fatal error.  I ran "git-import-dscs --pristine-tar" against all the
coreutils .dsc files from debsnap with a ~200 MB /tmp, and after a while
it printed this:

,----
| gbp:info: Tag upstream/8.1 not found, importing Upstream tarball
| 
| zgz: stdout: No space left on device
| pristine-gz: command failed: zgz --gnu -n -9 --rsyncable -F  -T 0 -c
| pristine-tar: command failed: pristine-gz --no-verbose --no-debug --no-keep 
gendelta 
/home/naesten/hacking/debian/source-coreutils/coreutils_8.1.orig.tar.gz 
/tmp/pristine-tar.xnp0q3MKx4/wrapper
| pristine-tar: failed to generate delta
| gbp:error: Couldn't commit to 'pristine-tar' with upstream 'upstream': 
/usr/bin/pristine-tar returned 9
| gbp:info: Tag upstream/8.4 not found, importing Upstream tarball
`----

... and tried to keep going.  (It also ate the first couple of SIGINTs
when I tried to kill it.)

So, it looks like git-import-dscs is eating exceptions that happen while
"running git-import-dsc" ...

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages git-buildpackage depends on:
ii  devscripts       2.12.5
ii  git              1:1.7.10.4-1
ii  python           2.7.3~rc2-1
ii  python-dateutil  1.5+dfsg-0.1

Versions of packages git-buildpackage recommends:
ii  cowbuilder    0.70
ii  pristine-tar  1.26

Versions of packages git-buildpackage suggests:
ii  python-notify  0.1.1-3
ii  unzip          6.0-7

-- no debconf information

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to