Bug 140091 - change source of installation / install and remove software (found in SUSE 9.3)
Summary: change source of installation / install and remove software (found in SUSE 9.3)
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: unspecified
Hardware: i686 Linux
: P5 - None : Enhancement
Target Milestone: ---
Assignee: Jiri Srain
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-18 07:22 UTC by ferdinand gassauer
Modified: 2006-04-06 14:29 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ferdinand gassauer 2005-12-18 07:22:49 UTC 
Hi!

1) IMHO these 2 components should be merged for convenience

2) adding a directory with frequent changes like 
pub/i386/supplementary/KDE/update_for_9.3/yast-source
seems to lead to messages like "file not on Installation medium" in "install and remove software" unless the a "refresh" is done for this directory "change source of installation".

IMHO the refresh should be done at least automagically, especially because the refresh option is well hidden behind the edit button and it took me quite some time to figure out what was (not) happening.
Comment 1 Michael Gross 2005-12-19 16:02:09 UTC 
Sorry, but SUSE LINUX prior to version 10.0 can not be supported in this open bugzilla. I don't think these two seperate modules should be merged. Also refreshing the installation sources could take some time on slow media or connections. Jiri: Please give us a comment anyway.
Comment 2 ferdinand gassauer 2005-12-19 16:42:29 UTC 
I know for 9.3, but it's the same in 10.0

if the refresh is not done automagicaly the user runs into the problem mentioned above. 

so at some point it is necessary to do a refresh with or without user intervention. 

IMHO the argument of the slow connection is not valid, because trying to update loads the new rpm's until it reaches a file which is not present any more and - to be sure - the update procedure should be canceled. Hence waisting time and band width.
Comment 3 Michael Gross 2005-12-19 17:43:10 UTC 
Jiri should decide here.
Comment 4 Christoph Thiel 2006-04-06 14:29:53 UTC 
We have autorefresh in 10.0, which you obviously didn't test/use.