duplicity-team team mailing list archive

[Domoradov Alex <question264557@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Answered => Open

Domoradov Alex is still having a problem:
Thanks for the info. So as I understood, all I need is to upgrade to
0.6.25?

As far as I remember 0.6.25 is not compatible with librsync-1.0.0 from the
EPEL. So what would be the best way:

1. Downgrade to librsync-0.9.x
2. Replace librsyncmodule.c from 0.7 series

I don't need any new features, all I need is - STABLE :)

Thanks in advance.

On Wed, Apr 15, 2015 at 12:56 PM, edso <question264557@xxxxxxxxxxxxxxxxxxxxx
> wrote:

> Your question #264557 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/264557
>
>     Status: Open => Answered
>
> edso proposed the following answer:
> the corruption bug was fixed in 0.6.23
>  http://duplicity.nongnu.org/CHANGELOG
> "
> * Merged in lp:~mterry/duplicity/disappearing-source
>   - When restarting a backup, we may accidentally skip the first chunk of
> one of
>     the source files. To reproduce this,:
>     1) interrupt a backup
>     2) delete the source file it was in the middle of
>     3) restart the backup
>   - When replaying the source iterator to find where to resume from, we
> can't
>     notice that the file is gone until we've already iterated past where it
>     would be!
>   - The solution I came up with is to just let duplicity stuff the data we
>     accidentally read back into the source iterator.
>   - This is actually a data loss bug, because it's possible to back up
>     corrupted files (that are missing their first chunk).
> "
>
> ..ede/duply.net
>
> On 15.04.2015 11:46, Domoradov Alex wrote:
> > Question #264557 on Duplicity changed:
> > https://answers.launchpad.net/duplicity/+question/264557
> >
> >     Status: Answered => Open
> >
> > Domoradov Alex is still having a problem:
> > # cat /etc/redhat-release
> > CentOS release 6.6 (Final)
> >
> > # yum info duplicity
> > Available Packages
> > Name        : duplicity
> > Arch        : x86_64
> > Version     : 0.6.22
> > Release     : 4.el6
> > Size        : 533 k
> > Repo        : epel
> > Summary     : Encrypted bandwidth-efficient backup using rsync algorithm
> > URL         : http://www.nongnu.org/duplicity/
> > License     : GPLv2+
> >
> > On Wed, Apr 15, 2015 at 12:07 PM, edso <
> question264557@xxxxxxxxxxxxxxxxxxxxx
> >> wrote:
> >
> >> Your question #264557 on Duplicity changed:
> >> https://answers.launchpad.net/duplicity/+question/264557
> >>
> >>     Status: Open => Answered
> >>
> >> edso proposed the following answer:
> >> On 15.04.2015 09:12, Domoradov Alex wrote:
> >>> Question #264557 on Duplicity changed:
> >>> https://answers.launchpad.net/duplicity/+question/264557
> >>>
> >>>     Status: Answered => Open
> >>>
> >>> Domoradov Alex is still having a problem:
> >>> I have the same issue (SHA1 mismatch) with local backend. Now I'm
> testing
> >>> 0.7 series
> >>
> >> what was your version that created the backup?
> >>
> >>> Do I need to notify EPEL maintainer of duplicity?
> >>>
> >>
> >> if they promote anything older than 0.6.25 it'd make sense..
> >> ede/duply.net
> >>
> >> --
> >> If this answers your question, please go to the following page to let us
> >> know that it is solved:
> >>
> >>
> https://answers.launchpad.net/duplicity/+question/264557/+confirm?answer_id=8
> >>
> >> If you still need help, you can reply to this email or go to the
> >> following page to enter your feedback:
> >> https://answers.launchpad.net/duplicity/+question/264557
> >>
> >> You received this question notification because you asked the question.
> >>
> >
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.launchpad.net/duplicity/+question/264557/+confirm?answer_id=10
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/duplicity/+question/264557
>
> You received this question notification because you asked the question.
>

-- 
You received this question notification because you are a member of
duplicity-team, which is an answer contact for Duplicity.