maxincrement config value is not considered, if a full backup exists
Bug #604479 reported by
Florian Achleitner
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nssbackup |
Fix Released
|
Low
|
Jean-Peer Lorenz | ||
0.2 |
Confirmed
|
Low
|
Unassigned |
Bug Description
I found the bug in BackupManager.py. The value returned by self.config.get(..) is a string and it was not converted to an int before comparison in this particular if expression.
The attached patch fixes this.
Changed in nssbackup: | |
status: | New → Confirmed |
importance: | Undecided → Low |
assignee: | nobody → Jean-Peer Lorenz (peer.loz) |
Changed in nssbackup: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix committed to trunk. Thanks Florian.