I'm not affected with duplicity 0.7.06 on Ubuntu 16.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1252484
Title:
Possible data loss when restarting in the middle of a deleted
affected by this bug with duplicity 0.7.06
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1252484
Title:
Possible data loss when restarting in the middle of a deleted file
Status
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: duplicity (Ubuntu Quantal)
Status: Fix Committed = Won't Fix
--
You received this bug notification because you are a member of Desktop
** No longer affects: duplicity (Ubuntu Raring)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1252484
Title:
Possible data loss when restarting in the middle of a deleted file
** Changed in: duplicity
Milestone: None = 0.6.23
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1252484
Title:
Possible data loss when restarting in the middle of a deleted
** Changed in: duplicity
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1252484
Title:
Possible data loss when restarting in the middle
** Description changed:
This was recently fixed in duplicity trunk. But I'm filing a bug for
paperwork purposes and for Ubuntu SRUs.
[Impact]
When restarting a backup, duplicity may accidentally skip the first 65k
chunk of one of the source files. This means that when it is
** Description changed:
This was recently fixed in duplicity trunk. But I'm filing a bug for
paperwork purposes and for Ubuntu SRUs.
[Impact]
When restarting a backup, duplicity may accidentally skip the first 65k
chunk of one of the source files. This means that when it is
This bug was fixed in the package duplicity - 0.6.18-0ubuntu3.4
---
duplicity (0.6.18-0ubuntu3.4) precise; urgency=low
* debian/patches/11-dont-skip-first-chunk-on-restart.dpatch:
- When restarting a backup, if the file we were in the middle of
backing up is now deleted,
This bug was fixed in the package duplicity - 0.6.08b-0ubuntu2.3
---
duplicity (0.6.08b-0ubuntu2.3) lucid; urgency=low
* debian/patches/08-dont-skip-first-chunk-on-restart.dpatch:
- When restarting a backup, if the file we were in the middle of
backing up is now deleted,
** Branch linked: lp:ubuntu/lucid-updates/duplicity
** Branch linked: lp:ubuntu/precise-updates/duplicity
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1252484
Title:
Possible
It's been a while, so I've verified for 10.04 myself.
** Tags added: verification-done-lucid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1252484
Title:
Possible data loss when
And same for 12.04.
** Tags added: verification-done-precise
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1252484
Title:
Possible data loss when restarting in the middle of a
Dan, if you are getting an error using the patched version of duplicity,
can you please file a new bug with the logs and details the bug form
asks for? It may be this bug, it may be something else. I'll triage
separately.
--
You received this bug notification because you are a member of
OK, I'll do this when I get home from a trip.
Upside is I'm learning a lot about how rsync works!
Dan
On 12/18/2013 09:45 AM, Michael Terry wrote:
Dan, if you are getting an error using the patched version of duplicity,
can you please file a new bug with the logs and details the bug form
Dan, simply backing up with a fixed duplicity will not retroactively fix
the bug. That is, if you have a backup chain that is already affected
by the bug, adding more incremental backups to the chain won't be able
to recover the previous missing 65k chunk. We're just ensuring that
future backups
I tried this with a brand-new backup, not an old one.
Dan
On 12/17/2013 11:53 AM, Michael Terry wrote:
Dan, simply backing up with a fixed duplicity will not retroactively fix
the bug. That is, if you have a backup chain that is already affected
by the bug, adding more incremental backups to
I just tried a backup and restore, encrypting the backup. Failed again
on the restore, in exactly the same way as far as I can tell.
At this point I simply use Grsync to run a complete backup to an
encrypted drive. It works well enough.
On 12/15/2013 04:56 PM, Michael Terry wrote:
Lennart, see
Lennart, see my comment #11. This fix/SRU is for the root cause when
making a backup, preventing the data loss in the first place.
But if you are trying to restore a backup affected by the bug (as you
are), the traceback you see when restoring is worked-around by a
separate fix in duplicity
I believe i'm still experiencing the problems.
I have a set of backups from a machine which started with Ubuntu 12.04
and was upgraded a few weeks ago to 13.10. The backups were created via
deja-dup. I'm trying to restore on a Machine Running Linux Mint (
~Ubuntu 13.10) with duplicity
** Attachment added: test1.sh
https://bugs.launchpad.net/duplicity/+bug/1252484/+attachment/3925018/+files/test1.sh
** Description changed:
This was recently fixed in duplicity trunk. But I'm filing a bug for
paperwork purposes and for Ubuntu SRUs.
[Impact]
When restarting a
I should note for anyone experiencing any of the symptoms of this bug
when restoring [1], this fix does not let you get back the 65k chunk of
data that this bug lost. But duplicity trunk contains some additional
fixes that should let you restore the rest of your data. That is,
duplicity trunk no
This bug was fixed in the package duplicity - 0.6.21-0ubuntu4.1
---
duplicity (0.6.21-0ubuntu4.1) saucy; urgency=low
* debian/patches/03-dont-skip-first-chunk-on-restart.dpatch:
- When restarting a backup, if the file we were in the middle of
backing up is now deleted,
Hello Michael, or anyone else affected,
Accepted duplicity into raring-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/duplicity/0.6.21-0ubuntu1.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:ubuntu/precise-proposed/duplicity
** Branch linked: lp:ubuntu/quantal-proposed/duplicity
** Branch linked: lp:ubuntu/raring-proposed/duplicity
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
Hello Michael, or anyone else affected,
Accepted duplicity into lucid-proposed. The package will build now and
be available at http://launchpad.net/ubuntu/+source/duplicity/0.6.08b-
0ubuntu2.3 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:ubuntu/lucid-proposed/duplicity
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1252484
Title:
Possible data loss when restarting in the middle of a deleted
With the version in proposed the testcase in the description passed.
Tested on Ubuntu Saucy (13.10) using duplicity 0.6.21-0ubuntu4.1
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages, which
Thanks, Miklos!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1252484
Title:
Possible data loss when restarting in the middle of a deleted file
Status in Duplicity - Bandwidth
** Also affects: duplicity (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: duplicity (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: duplicity (Ubuntu Raring)
Importance: Undecided
Status: New
** Also affects: duplicity (Ubuntu
** Branch linked: lp:ubuntu/trusty-proposed/duplicity
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1252484
Title:
Possible data loss when restarting in the middle of a deleted
This bug was fixed in the package duplicity - 0.6.22-1ubuntu3
---
duplicity (0.6.22-1ubuntu3) trusty; urgency=low
* debian/patches/04-dont-skip-first-chunk-on-restart.patch:
- When restarting a backup, if the file we were in the middle of
backing up is now deleted, don't
** Description changed:
This was recently fixed in duplicity trunk. But I'm filing a bug for
paperwork purposes and for Ubuntu SRUs.
[Impact]
When restarting a backup, duplicity may accidentally skip the first 65k
chunk of one of the source files. This means that when it is
Hello Michael, or anyone else affected,
Accepted duplicity into saucy-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/duplicity/0.6.21-0ubuntu4.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:ubuntu/saucy-proposed/duplicity
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1252484
Title:
Possible data loss when restarting in the middle of a deleted
35 matches
Mail list logo
