Hi!
On Sun, 2014-05-18 at 11:06:51 +0200, Ralf Jung wrote:
> Package: dpkg
> Version: 1.17.9
> Severity: normal
> each time an alternative is removed, I get an email from cron next day because
> the "dpkg" job in cron.daily produces output.
> For example, I just got an email after updating mime-support yesterday
> (which removed the "view" alternative):
>
> /etc/cron.daily/dpkg:
> tar: alternatives/view: Warning: Cannot stat: No such file or directory
>
> The problem is the call to
>
> tar -df ${dbalt}.tar.0 --warning=none -C $dbdir $dbalt
>
> in the cronjob: tar complains if the file it compares to does not exist, and
> it does so on stderr (hence the "> /dev/null" after this command does not
> help).
> I verified this by manually running this command with the alternatives.1.tar
> file,
> and indeed I get the output I got via email.
Hmm, bother. When I added the --warning=none, I checked the tar source
code to see if such warnings would be silenced but it, and it seemed
so, I guess I either missed some codepaths or missread some of the
code. In any case I'll just send stderr to /dev/null for 1.17.10.
Thanks,
Guillem
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
