tags 567477 + confirmed
thanks
Am 29.01.2010 um 11:38 schrieb Michael Below:
> Package: backup-manager
> Version: 0.7.9-1
> Severity: serious
> Justification: user changes in /etc/ have to be preserved (10.7.3)
>
> I just noticed that the cron-job for backup-manager has been moved
> back to /etc/cron.daily from cron.weekly where I placed it. This
> has to have happened since last weekly execution on Monday. I
> assume it happenend during an update to backup-manager (I
> use testing, with more or less daily updates).
Since backup-manager 0.7.9-1 has just migrated to testing, that seems
reasonable. And I can reproduce it when moving the cron script around
and reinstalling the package. The bug itself isn't new, however:
I haven't touched the maintainer scripts at all since I took over the
package six months ago. Looks like I have to do that now.
As a workaround, run "dpkg-reconfigure -pmedium backup-manager" and
select the desired cron frequency to prevent this from happening again.
> Today I got a report from cron.daily:
>
> From: Anacron <r...@judiz.de>
> To: r...@judiz.de
> Subject: Anacron job 'cron.daily' on ossietzky
> Date: Fri, 29 Jan 2010 10:54:01 +0100
>
> /etc/cron.daily/backup-manager:
> When validating the configuration file /etc/backup-manager.conf, 1
> warnings were found.
> failed, check /tmp/bm-burning.log.zxR0LQ
> run-parts: /etc/cron.daily/backup-manager exited with return code
> 1
Not sure if you want me to look at this problem as well, but if you do
please make a separate report.
> The regulars in #debian.de advised me to report this with severity
> "serious", so here it is...
These guys were absolutely right, also about the severity.
Cheers,
Sven
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
