** Changed in: duplicity (Ubuntu Quantal)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
** Changed in: duplicity (Ubuntu Raring)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
** Changed in: duplicity (Ubuntu Saucy)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
** Changed in: duplicity (Ubuntu Quantal)
Status: New => Triaged
** Changed in: duplicity (Ubuntu Raring)
Status: New => Triaged
** Changed in: duplicity (Ubuntu Saucy)
Status: New => Triaged
** Changed in: duplicity (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: duplicity (Ubuntu Quantal)
Importance: Undecided => Medium
** Changed in: duplicity (Ubuntu Raring)
Importance: Undecided => Medium
** Changed in: duplicity (Ubuntu Saucy)
Importance: Undecided => Medium
** Changed in: duplicity (Ubuntu Trusty)
Importance: Undecided => Medium
--
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/1266763
Title:
Race condition between status and backup
Status in Duplicity - Bandwidth Efficient Encrypted Backup:
Fix Committed
Status in “duplicity” package in Ubuntu:
In Progress
Status in “duplicity” source package in Precise:
In Progress
Status in “duplicity” source package in Quantal:
Triaged
Status in “duplicity” source package in Raring:
Triaged
Status in “duplicity” source package in Saucy:
Triaged
Status in “duplicity” source package in Trusty:
In Progress
Bug description:
When runnining "duply X status" while running "duply X backup" (sorry,
I don't know which duplicity commands are created by duply) due to a
race-condition the code of 'sync_archive' might happend to append
newly created meta-data files to 'local_spurious' and subsequently
delete them. This delete seems to have been the reason that triggered
bug 1216921.
The race condition is that the backup command constantly creates meta-
data files while the status command queries the list of local and
remote files independently over a larger time span. This means that a
local file might already been remote but the status command did not
see it a few seconds ago.
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1266763/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
