After the backuplog disk was full, I resized the disk and now I encounter this error:
File "/usr/lib64/python2.7/site-packages/duplicity/manifest.py", line 208, in from_string
assert filecount == len(self.files_changed)
Accodring to associated bug, this is fiexed in 0.7.13. The lastest release is 0.7.15 - so maybe we can update duplicity...
Major priority, since backups currently do not work, and I don't know how to fix this (delting a file, ...?)
according to http://duplicity.nongnu.org/CHANGELOG it is fixed in 0.7.14.
At least deleting .part files helped, as stated in the changelog
Assigning to all packagers collectively, since there is no registered maintainer for this package.
I've looked into this issue myself (cauldron). This is python, maybe someone with python experience can do this. The built rpm requires some python packages that can't be found.
(In reply to Marc Krämer from comment #3)
> I've looked into this issue myself (cauldron). This is python, maybe someone
> with python experience can do this. The built rpm requires some python
> packages that can't be found.
@ Python maintainers
Reassigning to you. The built duplicity rpm Marc talks about, is a newer duplicity which fixes this bug:
(In reply to Marc Krämer from comment #0)
> After the backuplog disk was full, I resized the disk and now I encounter
> this error:
> File "/usr/lib64/python2.7/site-packages/duplicity/manifest.py", line 208,
> in from_string
> assert filecount == len(self.files_changed)
Assertion error on backup =>
Assertion error in /usr/lib64/python2.7/site-packages/duplicity/manifest.pyAssignee:
Pushed latest duplicity 0.7.15 to core/updates_testing. Please test.
I had to import python-fasteners from cauldron to mga6 also as it's required by latest duplicity.
Tested in Mageia 6 x86_64
Done a backup, configured with deja-dup.
All went normal.
I can confirm this for the same platform (Mageia 6 x86_64). Looks good to me.
Adding the 64bit OK for these two successful tests
Advisory made from comment 5.
A small query before validation.
I did empirical package & dependancy tests:
BEFORE the update: python2-fasteners & python3-fasteners pkgs do not exist; and duplicity shows no dependancy for them.
AFTER (from core_updates_testing): duplicity-0.7.15-1.mga6
python2-fasteners Version : 0.14.1 Release : 1.mga6
python3-fasteners Version : 0.14.1 Release : 1.mga6
$ urpmq -d duplicity | grep fasteners
i.e. no dependancy is shown for python3-fasteners.
Should there be? Does it matter? When replying, you may clear the 'feedback' marker.
It certainly shouldn't require both.
In which case I am validating.
An update for this issue has been pushed to the Mageia Updates repository.