Bug 152382 - Add a "cancel" button when refreshing sources in YAST install software
Summary: Add a "cancel" button when refreshing sources in YAST install software
Status: RESOLVED DUPLICATE of bug 141154
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 4
Hardware: Other Other
: P5 - None : Enhancement (vote)
Target Milestone: ---
Assignee: Jiri Srain
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-21 07:45 UTC by Perret Florian
Modified: 2006-08-10 11:09 UTC (History)
2 users (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 Perret Florian 2006-02-21 07:45:52 UTC 
When making an auto-refresh of sources in YAST install software, it would usefull to add a "cancel" button to allow to pass this functionnality.

I had a lot of sources in YAST and I don't want to refresh them each time I install a rpm, especially when I install a lot of them in a few times.
Comment 1 Lukas Ocilka 2006-03-15 14:53:01 UTC 
As a workaround, you can turn the "autorefresh" functionality off in the `yast2 inst_source` module and refresh them manually (or just leave only some of them autorefresh-enabled). But it might not work well :)
Comment 2 Perret Florian 2006-03-18 08:53:52 UTC 
I know this method. But it will be easier and faster to just click on a cancel button than going in YAST to disable autorefresh option for each source.
Comment 3 Jigish Gohil 2006-03-25 15:26:27 UTC 
On 10.1 Beta 8, in spite of turning off "autorefresh" functionality in yast inst_source, yast2 sw_single refreshes the sources every time it is launched. Takes about 45 minutes to 1 hour before sw_single window appears.
Comment 4 Jiri Srain 2006-08-10 11:09:52 UTC 
Will solve it together with providing progress for source refreshing...

*** This bug has been marked as a duplicate of bug 141154 ***