[Bug 1652410] Re: 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
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/1652410 Title: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1652410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652410] Re: 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
** 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 directory contains two volumes with different file names and same volume number in the same backup set To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1652410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652410] Re: 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: 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 directory contains two volumes with different file names and same volume number in the same backup set To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1652410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652410] Re: 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
** 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 file names and same volume number in the same backup set To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1652410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652410] Re: 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
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 system reinstall 16.04 I was determined to get it up and
running and learn about it's use,and perhaps recover some old data.
- Still fails with see attached text
+ [System]
- ProblemType: Bug
- DistroRelease: Ubuntu 16.04
- Package: deja-dup 34.2-0ubuntu1.1
- ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
- Uname: Linux 4.4.0-57-generic x86_64
- ApportVersion: 2.20.1-0ubuntu2.4
- Architecture: amd64
- CurrentDesktop: Unity
- Date: Fri Dec 23 16:56:43 2016
- ExecutablePath: /usr/bin/deja-dup
- InstallationDate: Installed on 2016-12-02 (21 days ago)
- InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
- ProcEnviron:
- PATH=(custom, user)
- SHELL=/usr/bin/fish
- LANG=en_CA.UTF-8
- LANGUAGE=en_CA:en
- XDG_RUNTIME_DIR=
- SourcePackage: deja-dup
- UpgradeStatus: No upgrade log present (probably fresh install)
+ Ubuntu 16.04
+ deja-dup 34.2-0ubuntu1.1
+ duplicity 0.7.06-2ubuntu2
+
+ [Symptoms]
+
+ When the backup location unfortunately contains two backup volumes with
+ different file names and same volume number in the same backup set, for
+ instance:
+
+ duplicity-full.20161129T015237Z.vol1.difftar
+ duplicity-full.20161129T015237Z.vol1.difftar.gz
+
+ this confuses duplicity collection-status, which ends up returning an
+ undescriptive Python assertion error, as seen in this Déjà-Dup log file:
+
+ DUPLICITY: INFO 1
+ DUPLICITY: . Args: /usr/bin/duplicity collection-status [...]
+
+ [...]
+
+ DUPLICITY: DEBUG 1
+ DUPLICITY: . 12 files exist on backend
+
+ DUPLICITY: DEBUG 1
+ DUPLICITY: . Extracting backup chains from list of files:
+[u'duplicity-full.20161129T015237Z.vol1.difftar',
+ u'duplicity-full.20161129T015237Z.manifest',
+ u'duplicity-full.20161129T015237Z.vol1.difftar.gz',
+ u'duplicity-full-signatures.20161129T015237Z.sigtar.gz',
+ u'duplicity-full-signatures.20161129T015237Z.sigtar',
+ [...]
+
+ DUPLICITY: DEBUG 1
+ DUPLICITY: . File duplicity-full.20161129T015237Z.vol1.difftar is not
+ part of a known set; creating new set
+
+ DUPLICITY: DEBUG 1
+ DUPLICITY: . File duplicity-full.20161129T015237Z.manifest is part of
+ known set
+
+ DUPLICITY: ERROR 30 AssertionError
+ [...]
+ DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/collections.
+ py", line 105, in add_filename(self.volume_name_dict, filename)
+ DUPLICITY: . AssertionError:
+ ({1: 'duplicity-full.20161129T015237Z.vol1.difftar'},
+ 'duplicity-full.20161129T015237Z.vol1.difftar.gz')
+
+ What happens is that duplicity collection-status takes the uncompressed
+ duplicity-full.20161129T015237Z.vol1.difftar for the start of a backup
+ set, then tries to add the compressed duplicity-
+ full.20161129T015237Z.vol1.difftar.gz to this set, and fails because the
+ volume number of this file has already been added to the set. Otherwise
+ there would be two backup volumes with the same volume number in the
+ backup set.
+
+ Note that a similar issue may also happen for file signatures instead of
+ backup volumes, e.g.:
+
+ duplicity-full-signatures.20161129T015237Z.sigtar
+ duplicity-full-signatures.20161129T015237Z.sigtar.gz
+
+ but backup volumes appear to be tripped on first, perhaps because of
+ alphabetic order.
+
+ Note also that under normal operation, the backup location isn't
+ supposed to contain a mixed of compressed and uncompressed files (or
+ encrypted and unencrypted files), but this situation was still reported
+ by the bug reporter in the original bug report.
+
+ [Test case]
+
+ See comment 19, written for Déjà-Dup, but easily adaptable to pure
+ duplicity I think.
+
+ [Ideas for fixing]
+
+ Duplicity already has checks to avoid considering files whose names
+ don't look like they could be part of a backup set (see comment 19,
+ point 4). Perhaps this filename filter could be improved on so that
+ duplicity doesn't burp so hard when a backup volume is present in both
+ compressed and uncompressed forms? Perhaps it could have duplicity
+ prefer a particular filename when there are two volumes with the same
+ number in the same backup set? But then which one and on what grounds?
+
+ Please also see comment 23.
+
+ [Easier fix]
+
+ Worst case, if this situation can't be handled automatically and the
+ situation requires a human to examine the contents of the backup
+ repository to take adequate action, then it would be helpful that
+ duplicity return a more descriptive message than the current terse
+ assertion error.
--
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:
[Bug 1652410] Re: 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
** 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 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 file names and same volume number in the same backup set To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1652410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652410] Re: 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 (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 directory contains two volumes with different file names and same volume number in the same backup set To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1652410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652410] Re: 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
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 volumes with different file names and same volume number in the same backup set To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1652410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652410] Re: 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
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 persistence. This may save my skin someday. -- 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 file names and same volume number in the same backup set To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1652410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652410] Re: 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
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)
AssertionError: ({1: 'duplicity-full.20161129T015237Z.vol1.difftar'},
'duplicity-full.20161129T015237Z.vol1.difftar.gz')
For Ubuntu 14.04, deja-dup 30.0-0ubuntu4.1, duplicity 0.6.23-1ubuntu4.1:
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py",
line 100, in add_filename
(self.volume_name_dict, filename)
AssertionError: ({1: 'duplicity-full.20170115T235149Z.vol1.difftar'},
'duplicity-full.20170115T235149Z.vol1.difftar.gz')
Function add_filename(self, filename) parses the examined filename (in
this case "duplicity-full.$timestring.vol1.difftar.gz") and decides if
it should be added to the examined backup set (self, an instance of the
BackupSet class, consisting for now of just one backup volume,
"duplicity-full.$timestring.vol1.difftar").
The function returns True if it adds the examined filename to the
current backup set, False if it rejects it, for instance it rejects
files whose parse results don't include "full" or "inc", and files whose
parse results indicate a different timestring than the timestring of the
current backup set.
The assertion that fails is "not
self.volume_name_dict.has_key(pr.volume_number)", meaning that the
volume number found in the parse results (in our case 1) is already in
the backup set (stored as a volumenumber/filename dictionnary: {1:
duplicity-full.$timestring.vol1.difftar}).
A quick way to avoid that bug would be to turn the assertion into an "if
volume-number already in backup-set, reject filename" (i.e. return
False), which means that when encountering two or more of:
duplicity-$type.$timestring.vol$n.difftar
duplicity-$type.$timestring.vol$n.difftar.gz
duplicity-$type.$timestring.vol$n.difftar.gpg
duplicity would accept into the backup set the first filename it
processes, and reject the others.
A probably better way would be to also compare compression flags when
grouping the files into sets, in addition to backup type (full/inc) and
times. That way an uncompressed file couldn't be added to a backup set
made up of compressed files, and vice versa. In the simplest case, this
would require:
adding the attribute self.compressed to the class BackupSet
adding self.compressed = bool(pr.compressed) to the method
BackupSet.set_info, that initializes the attributes of the
class instances
adding something like
if bool(pr.compressed) != bool(self.compressed):
return False
to BackupSet.add_filename after it tests for backup type
and backup times
But then it gets complicated by the fact that a backup set can be
partially encrypted, if I understand correctly the rest of the
add_filename function ("if bool(pr.encrypted) !=
bool(self.encrypted)..."). So perhaps the function should also
accommodate backup sets which are partially compressed? Also, assuming
the add_filename is changed to group files into sets of homogeneous
compression/encryption status, then how would the function that groups
sets into chains have to be modified?
I don't know duplicity's source code well enough, and won't any time
soon, to take a decision regarding this issue and fix it by myself,
sorry.
--
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 file names and same
volume number in the same backup set
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1652410/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652410] Re: 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
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 software packages now to find the part, which needs improvement. If you do (or did?) so, it would be helpful, if you could state filename and line number of your findings. I will come back to this bug later this week ** Changed in: deja-dup Status: Triaged => 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: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1652410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652410] Re: 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
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: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1652410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652410] Re: 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
** 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: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1652410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652410] Re: 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
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 have been successfully created:
$ ls -l ~/deja-dup
-rw--- 1 luke luke 171 Jan 16 00:51
duplicity-full.20170115T235149Z.manifest
-rw--- 1 luke luke 48989 Jan 16 00:51
duplicity-full.20170115T235149Z.vol1.difftar.gz
-rw--- 1 luke luke 9965 Jan 16 00:51
duplicity-full-signatures.20170115T235149Z.sigtar.gz
2. Uncompress the backup volume:
$ gunzip --to-stdout duplicity-full.20170115T235149Z.vol1.difftar.gz >
duplicity-full.20170115T235149Z.vol1.difftar
$ ls -l ~/deja-dup
-rw--- 1 luke luke171 Jan 16 00:51
duplicity-full.20170115T235149Z.manifest
-rw-rw-r-- 1 luke luke 480256 Jan 16 00:57
duplicity-full.20170115T235149Z.vol1.difftar
-rw--- 1 luke luke 48989 Jan 16 00:51
duplicity-full.20170115T235149Z.vol1.difftar.gz
-rw--- 1 luke luke 9965 Jan 16 00:51
duplicity-full-signatures.20170115T235149Z.sigtar.gz
3. Start the first incremental backup and witness the assertion error in
duplicity that David reported:
$ deja-dup --backup
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1494, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1488, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1337, in main
do_backup(action)
File "/usr/bin/duplicity", line 1370, in do_backup
globals.archive_dir).set_values()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 697,
in set_values
self.get_backup_chains(partials + backend_filename_list)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 819,
in get_backup_chains
map(add_to_sets, filename_list)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 809,
in add_to_sets
if set.add_filename(filename):
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 100,
in add_filename
(self.volume_name_dict, filename)
AssertionError: ({1: 'duplicity-full.20170115T235149Z.vol1.difftar'},
'duplicity-full.20170115T235149Z.vol1.difftar.gz')
$ DEJA_DUP_DEBUG=1 deja-dup --backup > deja-dup.log1
# see attached file for details
4. Interestingly, duplicity already has checks to avoid considering
files whose names don't look like they could be part of a backup set, as
proven by the success and log file of the following incremental backup:
$ ls -l ~/deja-dup
-rw-rw-r-- 1 luke luke 0 Jan 16 01:08 assignment.odt
-rw-rw-r-- 1 luke luke 0 Jan 16 01:08 creative-writing-syllabus.pdf
-rw-rw-r-- 1 luke luke 0 Jan 16 01:08 duplicity-commandline-memo.txt
-rw-rw-r-- 1 luke luke 0 Jan 16 01:08 duplicity-full-1995-movie.mkv.vol1.rar
-rw--- 1 luke luke 171 Jan 16 00:51
duplicity-full.20170115T235149Z.manifest
-rw--- 1 luke luke 48989 Jan 16 00:51
duplicity-full.20170115T235149Z.vol1.difftar.gz
-rw--- 1 luke luke 9965 Jan 16 00:51
duplicity-full-signatures.20170115T235149Z.sigtar.gz
$ DEJA_DUP_DEBUG=1 deja-dup --backup > deja-dup.log2
# see attached file for details (truncated to the interesting bits)
So there's no need to come up with a brand-new extensive filename
filter, it's already here, only improve it so it doesn't burp so hard
when a backup volume is present in both compressed and uncompressed
forms.
** Attachment added: "deja-dup.log1"
https://bugs.launchpad.net/deja-dup/+bug/1652410/+attachment/4804855/+files/deja-dup.log1
--
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 file names and same
volume number in the same backup set
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1652410/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652410] Re: 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
>> 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, unfortunately, I realize it is not a file list
that Déjà-Dup passes to duplicity collection-status, but the path/URL of
the backup repository, e.g.:
duplicity collection-status [options] file://home/luke/deja-dup
This is what duplicity expects for this action, according to the man
page. So it might be trickier than I thought to have duplicity not
examine certain files, and perhaps this bug would be better solved on
duplicity's side than on Déjà-Dup's side.
Worst case, if the bug can't be fixed and the situation requires a human
to examine the contents of the backup repository to take adequate
action, then duplicity should return a more descriptive message than the
current terse assertion error.
--
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 file names and same
volume number in the same backup set
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1652410/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652410] Re: 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
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 consider this to be Triaged, even if this bug has not been replicated
by someone else. The reason for this problem is found and a way to solve
it within Dèjá Dup is given.
I will forward to upstream as well.
** Also affects: deja-dup
Importance: Undecided
Status: New
** Changed in: deja-dup
Status: New => Triaged
** Changed in: deja-dup
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
directory contains two volumes with different file names and same
volume number in the same backup set
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1652410/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652410] Re: 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
** 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 (Ubuntu)
Status: Incomplete => New
--
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 file names and same
volume number in the same backup set
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1652410/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
