On 2012-01-16 17:58 +0100, Sven Joachim wrote:
> It seems that we need a migration path to the single md5sums file, since
> (with backup-manager from git master) cron spams me with mails
> containing messages like these:
>
> ,----
> | /etc/cron.daily/backup-manager:
> | Unable to find the md5 hash of file
> | "/var/archives/turtle-etc.20120110.master.tar.gz" in file
> | "/var/archives/turtle-hashes.md5".
> | Unable to find the md5 hash of file
> | "/var/archives/turtle-etc.20120111.master.tar.gz" in file
> | "/var/archives/turtle-hashes.md5".
> | [... etc]
> `----
>
> After BM_ARCHIVE_TTL days this will hopefully stop, but it is still not
> acceptable to annoy everyone with those messages.
There is another problem that applies to upstream as well: md5sum hashes
for old backups are not removed from $MD5FILE when the archives
themselves are deleted.
Cheers,
Sven
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
