I must force a reload / check before update-manager find updates.

[Removed by request]

Binary package hint: update-manager

My system checks for updates everyday and the update-manager works well.

But because there are many updates with Dapper I sometimes want to know if new versions of package are available.
So I run manually update-manager (graphic program System > administration > etc.), and it tells me first that my system is up to date (after having examined my system). But if I force the search for new updates It finds new updates ...(after having downloaded package informations).

Update-manager must find new-updates as soon as it's launched without any user operation.

[Sitsofe Wheeler (sitsofe)]

Thanks for your bug report.

In order to find new updates as soon as it is launched would mean going off and polling the network repositories every single time it is launched. I'm not so sure that is desirable and any one who really wanted to check for updates multiple times a day can manually do so already...

[Removed by request (removed30301)]

So update-manager might not indicate the sytem is up to date when it's not.

[Sitsofe Wheeler (sitsofe)]

Well I'd say that depends on your definition of up to date. If you mean up to date this very minute then yes you have a point. But where is the line? If you do an upgrade then one minute after the upgrade another update comes out you are technically not up to date...

Generally my understanding about software updates is you go a day between automated checks. Any more and you risk bringing servers to their knees with a stampede of unnecessary polling.

[Sitsofe Wheeler (sitsofe)]

This is very similar to Bug #35009

[Removed by request (removed30301)]

Yes.
I understand the problem with the servers.
Just make it less confusing for the end user.

[Sebastian Heinlein (glatzor)]

Furthermore the server are not updated more than once a day.

[Removed by request (removed30301)]

"Furthermore the server are not updated more than once a day."

May be for stable releases, but this is not the case at all for unstable ones.

[Sebastian Heinlein (glatzor)]

I think that our primary target should be the stable system.

[Removed by request (removed30301)]

It's very useful for testers (unstable) to know if there are another available packages or not (before reporting a bug for example or checking translations etc.).

So I think it's better not to take care of this point (in the futur the servers could be updated more than once a day).

Let's try to do our best so that the software is as user-friendly as possible.