Bug 465223 - zypper: check the network first, then access the repo over network
Summary: zypper: check the network first, then access the repo over network
Status: RESOLVED WONTFIX
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Final
Hardware: x86-64 Other
: P4 - Low : Enhancement with 2 votes (vote)
Target Milestone: ---
Assignee: Jan Kupec
QA Contact: E-mail List
URL:
Whiteboard: patches-welcome
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-11 20:40 UTC by macias -
Modified: 2010-02-21 17:52 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description macias - 2009-01-11 20:40:52 UTC
zypper: check the network first, then access the repo over network

The problem is when the network is down (no driver loaded, no interface up, simply nothing at hardware level) and zypper still tries hard to make a connection and then ask the user for _each_ repo if she/he would like to abort/ignore/etc.

Please, add the hardware capabilities -- if there is no network, there is no chance to get the connection, so if would be really useful to add option "skip all repositories accessible via the network". This is just a suggestion, but main point is -- to make it faster/easier to use only local repos.
Comment 1 Jan Kupec 2009-01-15 16:10:26 UTC
Agreed, but low priority.
Comment 2 Jan Kupec 2010-02-21 17:52:01 UTC
I won't get to this in near future, so i'll close the report for now. Patches are welcome, though. See also http://en.opensuse.org/Zypper/Bugs_For_Adoption.

Also, there is now --no-remote global option, which will disable remote repos for current command. There's also 'zypper mr -dt' which will disable all the remote repos for good ('zypper mr -et' to enable them again).