|
Bugzilla – Full Text Bug Listing |
| Summary: | Installation sources in offline mode | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Marcel Hilzinger <marcel> |
| Component: | YaST2 | Assignee: | Duncan Mac-Vicar <dmacvicar> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | aj, bluedzins, bugz57, christian.jaeger, f-perret, fred.blaise, fremenzone, kkaempf, lslezak, mrmazda, opensuse, pallotta, uwe.hering |
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | libzypp2 | ||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Marcel Hilzinger
2006-11-24 12:25:40 UTC
I agree, the unavailable sources should be diplayed in the overview. But I don't think that it's necessary to mention this particular problem in the release notes, the sources are not removed and when the network is available again they will show up there. Linux is often two steps forward and one behind. That's what most users find annoying.... If the sources are displayed also in offline mode, then it's nut neccessary, right. but.... YaSTs behaviour until now was: all sources were selectable and all sources were displayed. How do you think, user joe will know, that these things are features and not bugs (btw. I still consider this handling as bug)? Such a fundamental change _must_ be mentioned after the disaster with package management under 10.1. Most users just will not understand, why sometimes YaST gives them all the possibilities, another time not. Maybe they do not even think, that it's related to the internet connection. And how will YaST react, if you are using networkmanager and NM gives you a Pseudo-IP (Windows style)? This looks really confusing. Can't we do this better? Btw. Just checked with KNetworkManager: If you get a pseudo IP (169.254.49.182), then YaST thinks your online and gives all possibilities to choose a new source. Nevertheless, extisting network sources are not displayed, as they cannot be reached. So it's a mess this way, too. We plan to do better, but not for 10.2, it's too late. The plan is to provide a way to manage catalogs themselves only, without any refreshing or other outside dependencies of the system (if user does not explicitly ask for it, e.g. initiating refresh action manually). Can you for 10.2 (I know it's late) at lest leave off the confusing dialog. So YaST will _not_ remove any source automatically, just not show them. Or change the text to something like: "You are in offline mode: YaST will only display local installation sources." No "Yes" or "NO" button is needed, only "OK" *** Bug 223893 has been marked as a duplicate of this bug. *** Yast does _not_ remove any source automatically, user is asked whether the sources which could not be initialized should be removed or not. The problem is that the broken sources cannot be changed (yast is even unable to get the information about them so they cannot be displayed). *** Bug 223743 has been marked as a duplicate of this bug. *** I know but it's about usability: If I click on "Yes" I will not see the sources If I click on "No" I will not see the sources So in both cases the visible result is the same. That's why I call it a confusing dialog. Omitting the dialog and not delet anything would make things more clear. Not really. Users will ask what happened to their sources anyway. In some cases you really want to remove a broken source (e.g. the server or the repository has been removed) otherwise you will see the error messages again and again when starting the module. If a source is broken (unavailable) it is not displayed, if it is not displayed it cannot be removed... It could be possible to somehow get list of the broken sources and display them in the dialog (and make them not editable), but it would be non-trivial and probably it is not worth of doing it (see comment #5). To #11: That's why I suggested to change the text in the dialog to: You are in offline mode: YaST will only display local installation sources. Why is it so hard to accept an easy fix??? To #12. This has nothing to do with the initial problem. As sources are not showed anyway, you cannot remove them. You can only remove online sources in online mode now, right? If you are in online mode and a source is broken, you will get troubles with the timeout. That's why Bug 223893 is actually a different bug. There are two problems A) YaST does not show sources in offline mode (this bug) B) You cannot really remove broken sources in online mode (Bug 223893) As problem B) cannot be fixed in 10.2. Let's at least fix problem A) with the solution I wrote in comment #6. Please. Sorry, we cannot change any text now, the texts would be untranslated. *** Bug 230725 has been marked as a duplicate of this bug. *** *** Bug 231964 has been marked as a duplicate of this bug. *** *** Bug 233523 has been marked as a duplicate of this bug. *** *** Bug 239372 has been marked as a duplicate of this bug. *** *** Bug 240575 has been marked as a duplicate of this bug. *** Since my report is now a duplicate of this one, simple solution (imho): Please, do not refresh repos when IS is launched. Do it only when SM is launched. "do not refresh repos when IS is launched. Do it only when SM is launched." This requires the refactoring for 10.3 *** Bug 249353 has been marked as a duplicate of this bug. *** *** Bug 249767 has been marked as a duplicate of this bug. *** *** Bug 249773 has been marked as a duplicate of this bug. *** When I join similar themes in one bug report I get a comment, that each one should have an individual report. When I splitt them, you mark them as duplicates of one report ... But this are two topics: a) hidden, non-reachable installation sources, when updating fails b) Updating of deactivated installation sources when refresh is active. Where a is only relevant for the installation source management and b also for the installation itself. b should be fixable easily it think: if(xxx->doRefresh()) to if(xxx->isActivate() && xxx->dorefresh()) *** Bug 252486 has been marked as a duplicate of this bug. *** *** Bug 251133 has been marked as a duplicate of this bug. *** *** Bug 265276 has been marked as a duplicate of this bug. *** *** Bug 263136 has been marked as a duplicate of this bug. *** *** Bug 266864 has been marked as a duplicate of this bug. *** RE comment #22 'This requires the refactoring for 10.3' and status changed to 'resolved later' There are great deal of resolved later towards the release of a new version. Please clarify either "wontfix for 10.2" OR "Resolved in 10.3" and resolved how - due no apparent activity and reminants of slight confusion as in comment #5 and #13 otherwise the bug indicates changes need to be made to RC 10.3 with no assignment nor resolution of actual bug and this will remain a major issue in both versions. Perhaps for clarity we need the above status indicators This is not helpful for all those who have contributed to this and duplicate bugs reports. QA - Please comment on #22 Tobe fixed with 10.3 refactoring mass reopening all 10.2 LATER+REMIND bugs. close all 10.2 LATER/REMIND bugs as WONTFIX. Reopen yourself if you still plan to work on it. |