lp:~dernils/duplicity/docker-compose

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:~duplicity-team/duplicity/0.8-series at revision 1237

duplicity-team: Pending requested 2017-06-03

Diff: 124 lines (+76/-36)

2 files modified

testing/infrastructure/docker-compose.yml (+73/-0)
testing/infrastructure/setup.sh (+3/-36)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

1237. By nils on 2017-06-03

test infrastructure now using docker-compose

1236. By Kenneth Loafman on 2017-06-02

* Fix bug #1672540 with patch from Benoit Nadeau
  - Rename would fail to move par files when moving across filesystems.
  - Patch uses shutil.move() to do the rename instead.

1235. By Kenneth Loafman on 2017-06-02

* Some changes ported 0.7 to/from 0.8 to keep up-to-date.

1234. By Kenneth Loafman on 2017-05-31

* Revisited bug #670891 with patch from Edgar Soldin
  - Forced librsync.PatchedFile() to extract file object from TemporaryFile()
    object when on Windows or Cygwin systems. This allows us to avoid the
    problem of tmpfile() use which creates temp files in the wrong place.
  - See discussion at https://bugs.launchpad.net/duplicity/+bug/670891

1233. By Kenneth Loafman on 2017-05-29

* Fix spurious warning message, return value not needed.

1232. By Kenneth Loafman on 2017-05-21

* Checkpoint - docker testbed mostly running
  - lots of format changes in setup.sh
  - made sure to kill off network and restart
  - simplified container naming and killall process
  - most tests run now with tox, 5 fail

1231. By Kenneth Loafman on 2017-05-20

* Go back to original requirements file.

1230. By Kenneth Loafman on 2017-05-17

* May have finally fixed bug #1556553, "Too many open files...".
  - Applied patch from Howard Kaye, question #631423. The fix is to dup
    the file descriptor, and then close the file in the deallocator
    routine in the glue code. Duping the file lets the C code and the Python
    code each close the file when they are done with it.
  - Invalidated and removed the fix put in for bug #1320832.
  - Caveat: long incremental chains will still eat up a large number of file
    descriptors. It's a very risky practice, so I'm not inclined to fix it.

1229. By Kenneth Loafman on 2017-05-15

* Fix spelling and rearrange some.

1228. By Kenneth Loafman on 2017-05-15

* Added lpbuild-trusty to replace lpbuild-precise pre Aaron Whitehouse's
  comment that there was a bug in pexpect < 3.4 that affects us.