tags 361373 + upstream tags 361373 + confirmed thanks Hello,
You have pointed out a real bug: when the repository is too big for the
optical medium (> BM_BURNING_MAXSSIZE) backup manager tries to burn only
the last generated archives; but then, it displays an empty string where
it should display the date:
Cannot burn archives of the , too big: 1791M, must fit in 650
If the date was correctly set, this message won't happen and BM will
manage to burn the archives.
> As you can see, it has attempted to burn all files in my repository, not just
> the most recent (I only keep three days' worth of files there.)
Well, this is not how backup-manager behaves. See the user guide for details
about the burning process:
http://www.backup-manager.org/documentation/user-guide-devel/ch-configuration.html#s-exports-burning
This will be fixed in 0.7.3, Backup Manager 0.6.2 (stable branch) is not
affected by this bug.
Regards,
Alexis.
--
Alexis Sukrieh <[EMAIL PROTECTED]>
0x1EE5DD34
Debian http://www.debian.org
Backup Manager http://www.backup-manager.org
signature.asc
Description: Digital signature
