The result of our email discussion is that the --allow-concurrency
option needs to be removed but the locking mechanism stays. A note will
be added to the error message to indicate the lockfile that needs to be
removed to overturn the locking if it has been left behind from a failed
session.
I switched back the upstream status to In Progress to highlight the fact
that the solution that was merge is now incomplete. I'm starting to work
on a new patsh that should come in shortly
** Changed in: duplicity
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1266763
Title:
Race condition between status and backup
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1266763/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
