Update Manager not updating last time checking repo

Bug #218051 reported by Dean Loros on 2008-04-16
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

With the last update of Update Manager I have noted that it no longer updates the last time it checked the repository. Seems to be "stuck' on the day it was installed. Hardy Heron Testing, all current updates done. Update Manager version 1:0.87.18

Michael Vogt (mvo) wrote :

Thanks for your bugreport.

what is the output of:
$ ls -l /var/lib/apt/periodic/
$ cat /etc/apt/apt.conf.d/10periodic

Does update-manager display in its top panel when the last update was performed?

Changed in update-manager:
status: New → Incomplete

Michael Vogt wrote:
> Thanks for your bugreport.
>
> what is the output of:
> $ ls -l /var/lib/apt/periodic/
> $ cat /etc/apt/apt.conf.d/10periodic

Output looks like:

dean@linux:~$ ls -l /var/lib/apt/periodic/
total 0
-rw-r--r-- 1 root root 0 2008-04-07 07:58 update-stamp
-rw-r--r-- 1 root root 0 2008-04-08 18:01 update-success-stamp

dean@linux:~$ cat /etc/apt/apt.conf.d/10periodic
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Download-Upgradeable-Packages "0";
APT::Periodic::AutocleanInterval "0";
APT::Periodic::Unattended-Upgrade "0";

Have included a screenshot taken just after dowwloading/installing the
morning updates.

Dean

Dean Loros (autocrosser) wrote :

Ok-I see what is happening. I have Rui Pais's repository included & it has been "off" for the last several days, as soon as I excluded it in software sources the "problem" went away. Interesting that that will cue several warnings from update manager about outdated lists. I think it would be nice to include a Gconf "switch" to turn off the warnings. Thanks for the prompt E-mail about this "issue"--had I realized the change, I wouldn't have made the report---CONSIDERED CLOSED.

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.

Ralph Janke (txwikinger) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Dean Loros (autocrosser) wrote :

Far too long ago for me my friend--am in the last of Karmic testing & more than ready to move to the Lynx....I closed the bug back on 2008-04-16.

Jean-Baptiste Lallement (jibel) wrote :

Thanks for following up. I'm closing this report due to your last comment.
Don't hesitate to submit any new bug.

Changed in update-manager (Ubuntu):
status: Incomplete → Invalid
Matthew Woerly (nattgew) wrote :

I still think this is a valid bug... when one or more repositories cannot be updated, it freezes the "last updated" time, which is misleading.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers