Comment 4 for bug 218051

Revision history for this message
Matthew Woerly (nattgew) wrote :

I kind of feel bad commenting on a "closed" bug, but I noticed the same behavior when I upgraded to Intrepid. Some of my third-party repos weren't quite right, and so when I checked for updates, they came back with key errors or a 404. As long as this happened, the "last updated" time stayed at the same spot, so after a while the little warning triangle came up. Once I fixed the errors in the sources list, it finally set the time correctly.
So I would say the problem is that if it has errors, it doesn't update that time. I'm pretty sure that worked fine in Hardy.