GnuPGInterface prints exit statuses incorrectly

Binary package hint: python-gnupginterface

duplicity can produce a traceback like this:

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 582, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 576, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 568, in main
    incremental_backup(sig_chain)
  File "/usr/bin/duplicity", line 272, in incremental_backup
    bytes_written = write_multivol("inc", tarblock_iter, globals.backend)
  File "/usr/bin/duplicity", line 151, in write_multivol
    at_end = gpg.GzipWriteFile(tarblock_iter, tdp.name, globals.volsize)
  File "/usr/lib/python2.5/site-packages/duplicity/gpg.py", line 290, in GzipWriteFile
    new_block = block_iter.next(bytes_to_go)
  File "/usr/lib/python2.5/site-packages/duplicity/diffdir.py", line 466, in next
    result = self.process(self.input_iter.next(), size)
  File "/usr/lib/python2.5/site-packages/duplicity/diffdir.py", line 176, in get_delta_iter
    for new_path, sig_path in collated:
  File "/usr/lib/python2.5/site-packages/duplicity/diffdir.py", line 261, in collate2iters
    relem2 = riter2.next()
  File "/usr/lib/python2.5/site-packages/duplicity/diffdir.py", line 322, in combine_path_iters
    range(len(path_iter_list))))
  File "/usr/lib/python2.5/site-packages/duplicity/diffdir.py", line 300, in get_triple
    path = path_iter_list[iter_index].next()
  File "/usr/lib/python2.5/site-packages/duplicity/diffdir.py", line 235, in sigtar2path_iter
    sigtarobj.close()
  File "/usr/lib/python2.5/site-packages/duplicity/dup_temp.py", line 118, in close
    assert not self.fileobj.close()
  File "/usr/lib/python2.5/site-packages/duplicity/gpg.py", line 162, in close
    self.gpg_process.wait()
  File "/var/lib/python-support/python2.5/GnuPGInterface.py", line 639, in wait
    raise IOError, "GnuPG exited non-zero, with code %d" % (e << 8)
IOError: GnuPG exited non-zero, with code 131072

Regardless of the underlying error, the raise statement in python-gnupginterface is bizarrely wrong. It's probably intended to be a >> to get just the exit code, but even then it would be much better to use os.WEXITSTATUS. However, since gnupg could well terminate other than because of exit(), it's probably simplest just to print the whole wait status and let people decode signals, exit statements or whatever.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
Package: python-gnupginterface 0.3.2-9ubuntu1
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_AU.UTF-8
 SHELL=/bin/zsh
SourcePackage: gnupginterface
Uname: Linux 2.6.28-8-generic x86_64