nssbackup-team team mailing list archive
-
nssbackup-team team
-
Mailing list archive
-
Message #01300
[Bug 604479] [NEW] maxincrement config value is not considered, if a full backup exists
Public bug reported:
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.
** Affects: nssbackup
Importance: Undecided
Status: New
--
maxincrement config value is not considered, if a full backup exists
https://bugs.launchpad.net/bugs/604479
You received this bug notification because you are a member of NSsbackup
team, which is subscribed to NSsbackup.
Follow ups
-
[Bug 604479] Re: maxincrement config value is not considered, if a full backup exists
From: Jean-Peer Lorenz, 2010-08-11
-
[Bug 604479] Re: maxincrement config value is not considered, if a full backup exists
From: Jean-Peer Lorenz, 2010-07-21
-
[Bug 604479] Re: maxincrement config value is not considered, if a full backup exists
From: Jean-Peer Lorenz, 2010-07-20
-
[Bug 604479] Re: maxincrement config value is not considered, if a full backup exists
From: Florian Achleitner, 2010-07-12
-
[Bug 604479] [NEW] maxincrement config value is not considered, if a full backup exists
From: Florian Achleitner, 2010-07-12
References