lp:~ed.so/duplicity/gpg.tmp

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:duplicity/0.6 at revision 874

duplicity-team: Pending requested 2012-10-07

Diff: 31 lines (+4/-3)

1 file modified

duplicity/gpg.py (+4/-3)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

878. By ede on 2012-10-07

place gpg.py tempfiles in duplicity's tmp subfolder which is cleaned whatever happens

877. By Michael Terry on 2012-10-02

tests: apparently on hardy chroots, /bin can be smaller than 3MB compressed, so instead of using /bin in test_multi_volume_failure, use largefiles

876. By Michael Terry on 2012-10-02

tests: whoops, I had accidentally disabled one of the new tests for ignoring double entries in a tarball

875. By Michael Terry on 2012-10-02

tests: don't use subprocess.check_output, which was only added in Python 2.7

874. By Michael Terry on 2012-09-30

don't use unittest.TestCase.assertSetEqual, which isn't supported in older Python versions

873. By Kenneth Loafman on 2012-09-30

Update Changelog.GNU

872. By Kenneth Loafman on 2012-09-30

- Merged in lp:~ed.so/duplicity/ssh-pexpect-msgbug
  + Fixes 'UnboundLocalError: local variable 'msg' referenced before assignment'
    in _ssh_pexpect.py

871. By Kenneth Loafman on 2012-09-29

Wrap CHANGELOG to col 80.

870. By Kenneth Loafman on 2012-09-29

Update Changelog.GNU

869. By Kenneth Loafman on 2012-09-29

- Merged in lp:~mterry/duplicity/ropath.index
  + This branch does two main things:
    1) Skips base dir entries when compiling the list of deleted delta iters.
       (this gracefully recovers from the sort of situations that lead to bug
       929067). I'm reasonably confident this is an uninvasive change, but
       please confirm.
    2) Overwrites the sigtar file on backup-restart. This is because AFAICT,
       duplicity will rewrite the entire sigtar each restart. But we were
       opening the sigtar file as "ab", so we'd just dump the contents on top
       of the previous contents. Which was causing some confusion in bug 929067.
       If I'm wrong that we don't always rewrite the entire sigtar each time,
       this needs some rethink. Please also confirm that.
  + In addition, I added two tests for the above two changes and make some
    improvements elsewhere in the restarttest.py file while I was at it.