This can also happen if, for some unlikely reason (like a corrupted NTFS
partition), the file system lists the same file twice. See Question
#670964
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/165241
** No longer affects: deja-dup
** No longer affects: deja-dup (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652410
Title:
Undescriptive duplicity/collection-status error when the backup
** Changed in: duplicity (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652410
Title:
Undescriptive duplicity/collection-status error when the backup
dire
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652410
Title:
Undescriptive duplicity/collection-status error when the backup
directory contains two volumes with different fil
Added this bug to duplicity, since it is probably better suited for
resolution there than in Déjà-Dup.
Also updated the description.
** Tags removed: amd64 xenial
** Tags added: testcase
** Description changed:
- Deja-dup has never worked for me (last 5 years) always errors.
- No after a new sy
** Also affects: duplicity
Importance: Undecided
Status: New
** Also affects: duplicity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: duplicity
Status: New => Confirmed
** Changed in: duplicity (Ubuntu)
Status: New => Confirmed
--
You received this
** Changed in: deja-dup (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652410
Title:
Undescriptive duplicity/collection-status error when the backup
direc
I'm glad we could help!
All the best
Naël
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652410
Title:
Undescriptive duplicity/collection-status error when the backup
directory contains two volum
Vej and Nathanael
Update :
I deleted all the contents of dropbox backup file
restarted and it functioned without apparent error.
I did not, as you suggested, choose only a small file for backup, so ended up
vol 399.
Running again today after startup no apparent errors.
Thank you for you time and
The file and function I examined are those mentioned in the traceback
reported by David for Ubuntu 16.04, deja-dup 34.2-0ubuntu1.1, duplicity
0.7.06-2ubuntu2:
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py",
line 105, in add_filename
(self.volume_name_dict, filename)
Ass
Resetting to "Confirmed", because it turned out, that more triaging is
needed.
@Nathanael: Thanks for replicating the bug.
I did some searching for related bugs in duplicity and found bug
#1471818, which states, that these files are sometimes even deleted. So
we need to go into the code of both s
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: deja-dup (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652410
Title:
U
** Attachment added: "deja-dup.log2"
https://bugs.launchpad.net/deja-dup/+bug/1652410/+attachment/4804856/+files/deja-dup.log2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652410
Title:
Undesc
I have also replicated the bug, on Ubuntu 14.04 deja-dup 30.0 duplicity
0.6.23 (haven't got a more recent version yet but David has), as a
newly-created user with the default Déjà-Dup settings:
1. Perform the first full backup and check that the backup, the file
signatures, and the manifest file h
>> To fix this bug from happening in the future, we could perhaps
>> restrict the file list that is passed from Déjà-Dup to duplicity
>> collection-status? Perhaps to *.{diff,sig}tar.{gz,gpg} and
>> *.manifest files only, or something like that?
> This sounds good to me!
On further investigation,
Regarding comment #15:
> To fix this bug from happening in the future, we could perhaps restrict the
> file list that is passed from Déjà-Dup to duplicity collection-status?
>Perhaps to *.{diff,sig}tar.{gz,gpg} and *.manifest files only, or something
>like that?
This sounds good to me!
I cons
** Summary changed:
- duja-dup AssertionError: ({1: 'duplicity-full.20161129T015237Z.vol1.difftar'}
+ Undescriptive duplicity/collection-status error when the backup directory
contains two volumes with different file names and same volume number in the
same backup set
** Changed in: deja-dup (U
17 matches
Mail list logo
