http://bugzilla.suse.com/show_bug.cgi?id=1020117 http://bugzilla.suse.com/show_bug.cgi?id=1020117#c1 Stefan Hundhammer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Stefan Hundhammer --- We have two places where you can see the software repositories: - The "software repositories" YaST module where you can add, remove, enable/disable repositories or change their priorities - The "repositories" view in the package selector You are describing the behaviour in the package selector. That view intentionally does not show disabled repositories because the subsequent behaviour would be confusing: If disabled repos were listed there and the user would click on such a disabled repo, what should happen? The connected package list on the right side would still show the packages from that repo - or not? If a user tried to select such a package from a disabled repo, what should happen? Worse, if that package exists in several repos, including the disabled one (but also on one or more enabled repos), what should happen if the user selected such a package for installation or upgrade? Would he get the best one from one of the enabled repos - or, if the one from the disabled repos was the newest one, that one despite that repo not being enabled? This would introduce all kinds of confusion and inconsistencies; that's why those repos are *not* shown in that view. To get an overview over all repos, including disabled ones, please use the "software repositories" module. IMHO this behaves as intended -> INVALID (still a valuable contribution to discuss product features, of course). -- You are receiving this mail because: You are on the CC list for the bug.