Bug 120954

Summary: Adding Installation sources errors
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Dirk Stoecker <opensuse>
Component: YaST2Assignee: Jiri Srain <jsrain>
Status: RESOLVED FIXED QA Contact: Klaus Kämpf <kkaempf>
Severity: Enhancement    
Priority: P5 - None CC: mmeeks
Version: RC 1   
Target Milestone: ---   
Hardware: Other   
OS: All   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Dirk Stoecker 2005-10-07 10:42:32 UTC 
Hello, 
 
when adding installation sources in yast2 there are some things, which cause 
trouble: 
 
a) When adding a source I would prefer a larger window, where I can seee whole 
URL. At last 3/4 size of yast window would be fine. There is no real need to 
have it that small. 
b) Why is server and path splitted? This makes double work when using copy and 
paste. Maybe add an point "URL", where a complete source including ftp:// or 
http:// can be inserted in one field using C&P. 
c) When adding URL delays, there is no way to abort. Sometimes a "kill" 
command is the only solution after 10-15 minutes of delay. This also kills all 
previous added sources. 
d) Shorten the wait time in case of network errors (see point c). 
e) yast2 sometimes forgot a installation source completely if updating failed 
(in 9.3, don't know if fixed in 10.0)
Comment 1 Jiri Srain 2005-10-18 09:04:57 UTC 
a) Should be no problem to force the dialog to be wider

b) I can imagine another possibility saying "Type URL" with URL as the only entry in the dialog

c), d) Michael?

e) Please, check if the problem persist in 10.0, and if you manage to reproduce it, attach the YaST logs, please.
Comment 2 Michael Andres 2005-10-18 10:26:25 UTC 
c), d) is bug #124332. There's little difference between adding and refreshing a source.
Comment 3 Jiri Srain 2005-10-18 14:29:35 UTC 
a), b) have been fixed in SVN for 10.1.

Please, reopen and attach logs if e) occurres with 10.0.
Comment 4 Jiri Srain 2005-12-16 07:58:06 UTC 
*** Bug 137580 has been marked as a duplicate of this bug. ***