Question #284756 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/284756
Status: Answered => Solved
Jonathan Elchison confirmed that the question is solved:
no printouts for segfault when running duplicity directly (sans duply).
also, removing `--progress` has no effect.
however, i isolated the issue, it's caused by upgrading librsync from
1.0.0 to 2.0.0.
relevant threads, for posterity:
* https://github.com/librsync/librsync/issues/50
* https://bbs.archlinux.org/viewtopic.php?pid=1593684
* https://bugs.archlinux.org/task/47645
* https://bbs.archlinux.org/viewtopic.php?id=207080
sorry for the hassle, thanks for your help!
--
You received this question notification because your team duplicity-team
is an answer contact for Duplicity.
_______________________________________________
Mailing list: https://launchpad.net/~duplicity-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~duplicity-team
More help : https://help.launchpad.net/ListHelp
