Comment 4 for bug 356152

Thanks for the logs, I had a closer look at them now.

The log have dpkg runs at:
Log started: 2009-03-09 09:40:45
Log started: 2009-03-11 12:18:38
Log started: 2009-03-11 12:21:16
Log started: 2009-03-11 12:22:02
Log started: 2009-03-14 11:24:26
Log started: 2009-03-16 14:48:30
Log started: 2009-03-20 18:54:41
Log started: 2009-03-26 09:47:24
Log started: 2009-03-26 10:03:57
Log started: 2009-03-26 10:04:35
Log started: 2009-03-26 10:34:19
Log started: 2009-03-27 09:40:17
Log started: 2009-03-27 10:21:46
Log started: 2009-03-27 12:09:19
Log started: 2009-03-27 13:21:52
Log started: 2009-03-30 09:38:44
Log started: 2009-03-31 17:55:29
Log started: 2009-04-07 13:09:53

The time between the last runs (2009-03-31 and 2009-04-07) is according to pythons datetime:
6 days, 19:14:24 So we missed the 7 days time by some hours.

This maybe a usability bug. update-notiifer just checks when the last apt/dpkg action was performed
and calcualtes the 7 days based on that. But from a user perspective installing a new software and
installing a update is something different so it may not be clear why update-manager does not appear
in this situation.

I will ask the design team for its opinion.

Thanks,
 Michael