|
Bugzilla – Full Text Bug Listing |
| Summary: | software manager: smart error reporting and recovery | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.4 | Reporter: | macias - <bluedzins> |
| Component: | libzypp | Assignee: | E-mail List <zypp-maintainers> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Enhancement | ||
| Priority: | P4 - Low | CC: | dmacvicar, kkaempf, lslezak, ma, ncutler, schubi, william |
| Version: | Factory | ||
| Target Milestone: | Factory | ||
| Hardware: | i586 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
macias -
2007-08-21 19:37:23 UTC
Again, please , please.. install a copy of 10.3 beta1 and check if your suggestion is already implemented, the software manager stuff has been almost completely rewritten and probably your report dont apply anymore. Ok, I will wait for 10.3, thank you for the answer. The error handling is same in 10.3, no change. Yast displays all errors immediately when they occur. I'm to sure if it's reasonable to implement such error collector. At first we would need support in libzypp, yast doesn't know the context of the error message, it doesn't know what to do in step 4) in your proposal. The current implementation displays a popup requesting user feedback, I'm not sure if it's always possible to postpone it later... I assumed that yast gets some kind of error code too. But even without I (at least) would like such postponing error. Reason: too many times I am waiting for yast to finish fetching data, it could take 10 minutes, so I check progress after 10 minutes just to find out that yast stuck at the very beginning. Hmm, it seems to me as if the current behaviour is indeed right. The order in which package are installed (and hence repositories accessed) is determined by the require and prerequire dependencies. So if packages from 'B' (to cite the initial comment) cannot be installed, it probably makes little sense to download packages from 'C'. The current implementation is still limited by the fact that it doesn't account for mirrors (that is if a package is available from more than one repo). If 'B' is unavailable but a mirror, e.g. B1, is alive, the download should automatically retry the mirror thereby minimizing errors. But thats post-10.3 :-( Maciej, what do you think ? Klaus, misunderstanding. You are totally right (*), but when I said about starting SM I really meant _starting_ (when you click SM in yast). Not when you select packages, and you run install. So I was/am talking about the process of getting data _about_ packages in repos, not packages itself. And this is 100% independent. (*) However the same reason applies here with the correction you mentioned -- packages _could_ be dependant, but if it looks like this package: A -> B (error) -> C ; D -> F so it would be useful to wait with error about B and just run (install D and F, because they are both independent of A, B and C. It would be useful because installation is a lengthy process and it is very likely that user does not sit and stare in her/his monitor :-) Reassign to Michael as he's working on a next-gen solution. Still reproducible on current 11.3 Tested by pointing my google chrome repo (dl.google.com) to localhost via /etc/hosts then running Software manager. SM displays a modal error and pauses the refresh until it is cleared. Software Manager is gone. |