On Wed, 2006-03-08 at 07:56 -0500, Carl Hartung wrote:
On Wednesday 08 March 2006 05:47, Mike McMullin wrote:
On Tue, 2006-03-07 at 21:59 -0500, Carl Hartung wrote:
When susewatcher fails to connect, it doesn't report "no updates available" it reports "failed to connect" and turns the little green dot yellow. And your sense of security is really no different than what you enjoy a day or two *before* these updates are announced and released, right?
I thought that yellow meant a non-security related patch was available, red a security related patch and green was no patches available.
You must interpret my words *in context*, Mike, not in a vacuum. In the context of this thread yellow was reporting a failure to connect. If it can't connect, it won't know that any new patches are available, regardless of security level. It turns the dot yellow these circumstances, as well. You are otherwise correct in your interpretation of the color scheme.
The problem is more along the lines of not recalling when the dot was yellow and I could not connect. I cannot dispute you, I just cannot off hand confirm what you say in my mind.
I think it's because it can't write a current list of prospective update servers when a connection attempt fails, so it opts to clear the list out instead of potentially writing garbage or retaining stale data.
For what ever reason, the thinking is beyond me, as I can see reasons for not touching the file at all when it would fail to connect.
Every time I've tried to second-guess the developers at SUSE, I've discovered they know a thing or two more about what they're trying to accomplish than I do. I can see reasons for both, but this thread addresses what *is*... right now, it appears to clear out the list in anticipation of receiving current data... nothing wrong with that.
Agreed, nothing wrong with that.