Running that perl script showed that update notifier is
probably getting confused by log rotation!
It's telling me that it won't run update manager
because /var/log/dpkg.log is too new... even when
the darn file is only new because the log was rotated and is zero size.
I'm attaching a (bad) patch showing how this might be worked around.
I think this is an old bug, only exposed in Jaunty because of the change to not showing nonsecurity updates for a week.
Don't know how much of the problem this explains, but it does seem to explain the behavior of two systems I have access to, at least today.
Running that perl script showed that update notifier is
probably getting confused by log rotation!
It's telling me that it won't run update manager
because /var/log/dpkg.log is too new... even when
the darn file is only new because the log was rotated and is zero size.
I'm attaching a (bad) patch showing how this might be worked around.
I think this is an old bug, only exposed in Jaunty because of the change to not showing nonsecurity updates for a week.
Don't know how much of the problem this explains, but it does seem to explain the behavior of two systems I have access to, at least today.