duplicity-team team mailing list archive

[edso <question674425@xxxxxxxxxxxxxxxxxxxxx>]

Question #674425 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/674425

    Status: Open => Answered

edso proposed the following answer:
On 28.09.2018 00:17, BenRifkah Bergsten-Buret wrote:
> Question #674425 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/674425
> 
> BenRifkah Bergsten-Buret gave more information on the question:
> I did some more digging and this looks to me like a bug in duplicity
> 0.7.18.1. I was able to reproduce it with the both rsync and scp
> backends on the following new Vagrant Box installations:
> 
> ubuntu/bionic64 – built locally. No RPM available
> centos/7 – from EPEL package
> 
> I couldn't reproduce it with duplicity 0.7.17:
> ubuntu/bionic64 – from RPM
> centos/7 – built locally. No RPM available
> 
> I'm happy to provide more details but if this needs to be turned into a
> bug report let me know and I'll provide details there.
> 
> Thanks,
> 

seems to be
"
* Partial fix of bug #1734144 with patch from Joris van Eijden
  - Note: this is really just a partial fix for now, since it only covers
    the case where the local size does not yet match the remote size.  A
    case where -1 is the returned length is not fixed.
"
  https://bazaar.launchpad.net/~duplicity-team/duplicity/0.7-series/revision/1354

it does not check if the entry is 'None' which is the case if the backend does not support file size meta data fetching (most do not) 
  https://bazaar.launchpad.net/~duplicity-team/duplicity/0.8-series/view/head:/duplicity/backend.py#L616

for now you can stick w/ 0.7.17.. hopefully Ken will fix this soonish,
as it probably breaks lot's of installations.

..ede/duply.net

-- 
You received this question notification because your team duplicity-team
is an answer contact for Duplicity.