Control: fixed -1 0.93.1+nmu1
On Fri, 24 Aug 2012 09:55:06 +0300 Teodor MICU <mteo...@gmail.com> wrote:
> Since I had this problem only on my workstation, I have found that the
> cause was the network being down at the time Cron jobs were executed
> -- including u-a.
>
> Yesterday, I've added a short python script to /etc/cron.hourly that
> sent a nice message every hour:
> | /etc/cron.hourly/unattended-upgrade:
> | {'DESCRIPTION': u'Debian GNU/Linux unstable (sid)', 'RELEASE':
> u'unstable', 'CODENAME': 'sid', 'OS': 'GNU/Linux', 'ID': 'Debian'}
>
> The python script is:
> | #! /usr/bin/python
> |
> | import lsb_release
> | print lsb_release.get_distro_information()
>
> Today U-A was executed with network UP and the log starts with:
> | Preconfiguring packages ...
> | {'DESCRIPTION': u'Debian GNU/Linux unstable (sid)', 'RELEASE':
> u'unstable', 'CODENAME': 'sid', 'OS': 'GNU/Linux', 'ID': 'Debian'}
>
> I don't know if there is anything to fix for this case.
This issue has been fixed by the NMU making u-u-s run before network
becomes available.
Since the default installation now starts u-u from systemd rather than
from cron the fix should solve the problem for almost all users.
Cheers,
Balint
