Bug 133811

Summary: refreshing installation source: error does not say which one it is
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Martin Vidner <mvidner>
Component: YaST2Assignee: Jiri Srain <jsrain>
Status: RESOLVED FIXED QA Contact: Klaus Kämpf <kkaempf>
Severity: Normal    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: i686   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: y2log-133811

Description Martin Vidner 2005-11-15 10:34:05 UTC
I ran yast2 -i and it tried to refresh a remote installation source. It failed and gave me an error popup:

Could not read the description of a remote source          {in Czech}
ERROR(Media:connection failed)[couldn't connect to host]   {in English}
[Retry] [Skip Refresh] [Disable Source]

The bug is that it does not say which source it is. I would like to see both its name and URL.

y2log follows. The remote host does not respond to pings at the moment.
Comment 1 Martin Vidner 2005-11-15 10:36:23 UTC
Created attachment 57355 [details]
y2log-133811
Comment 2 Martin Vidner 2005-11-15 13:55:22 UTC
One more minor thing: when I click Skip Refresh above, a popup appears
  The installation source has not been refreshed.
  [OK]
I think it is superfluous.
Comment 3 Jiri Srain 2005-12-02 10:22:12 UTC
Superfluous popup has been disabled for 10.1...
Comment 4 Jiri Srain 2005-12-02 10:26:44 UTC
Package manager does not report the name or URL of the source. Michael, could it be added to the map which is argument of the ErrorSourceRefresh callback?
Comment 5 Michael Andres 2005-12-02 11:06:42 UTC
Url, product_dir and label of the source are sent on CB_StartSourceRefresh.

Subsequent callbacks (CB_ErrorSourceRefresh,CB_DoneSourceRefresh) belong to 
this source. You'll never get an CB_Error or CB_Done without having got an 
initial CB_Start.

yast2-pkg-bindings-2.13.1 will store and repeat the StartSourceRefresh map
in subsequent callbacks.
Comment 6 Martin Vidner 2005-12-02 11:35:50 UTC
But that does not solve the bug yet. The UI needs to dispay the newly provided info.
Comment 7 Jiri Srain 2005-12-02 11:45:10 UTC
Now reporting this info is in SVN.