Re: Is my unattended upgrades working?

[Florian Lindner <mailinglists@xgm.de>]

Am Montag, 28. Oktober 2013, 11:58:00 schrieb Bob Proulx:
> Florian Lindner wrote:
> > > Florian Lindner wrote:
> > > > root@astarte ~ # ll /etc/cron.daily
> > > > -rwxr-xr-x 1 root root 14985 Jun  4 11:33 apt.dpkg-dist*
> > 
> > The thing what puzzles me most is that if the apt.dpkg-dist script
> > is called manually it logs just fine and everything. But the cron
> > job that is supposed to run logs nothing..
> 
> Are you talking about /etc/cron.daily/apt.dpkg-dist file name?  That
> name will never be run by run-parts because the name matches one of
> the standard dpkg installed files that are NOT enabled.  run-parts is
> called by cron from /etc/crontab.

Ah, didn't know that!

> Try this and see what names are printed.  The apt.dpkg-dist name will
> not be printed.  It is not run by run-parts.  Along with "#*" names
> and "*~" names and others that are skipped.
> 
>   run-parts --list /etc/cron.daily
> 
> I guess that when apt was installed or upgraded somewhere along the
> way you had modified the /etc/cron.daily/apt file.  Therefore dpkg
> didn't overwrite it and left the new version of the file there as
> apt.dpkg-dist so that you could examine it and merge it into the
> standard /etc/cron.daily/apt file if desired.

Actually I didn't modified the apt file, there is not even a apt file in 
cron.daily. Maybe it was because I I tried cron-apt too and they somehow 
conflicted.
 
> [I don't remember the difference between files with .dpkg-dist and
> .dpkg-new names.  Basically the same situation but arrived there
> differently.  Conversely if dpkg replaces a file then the old file is
> left around as .dpkg-old.  dpkg will ask you with a dialog if you want
> the old file, new file, or view differences, then you select one
> option and the result is as you see.]

Never saw such a dialog, but I think mv apt.dpkg-dist apt should have fixed it.

Thanks!
Florian