|
Bugzilla – Full Text Bug Listing |
| Summary: | can't skip refresh of repository during installation if repo is unavailable | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | Stefan Assmann <sassmann> |
| Component: | libzypp | Assignee: | Ladislav Slezák <lslezak> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | forgotten_xs3PtXj4XH, locilka, lslezak |
| Version: | Beta 5 | ||
| Target Milestone: | --- | ||
| Hardware: | PowerPC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
yast-skip.png
y2logs.tar.bz2 |
||
What about YaST logs, do you have some? Created attachment 254338 [details]
y2logs.tar.bz2
oh sorry I was too slow ;-) The problem is probably related to evaluating callbacks or to reading UI events... I guess the problem is in libzypp, there is no progress callback when libcurl is waiting for data. The progress callback should be called at least after (let's say) 3 seconds even when there is no real progress (the same state) so the abort button state is evaluated. Jano is that possible? Lado, to your question, no, it's not possible in libzypp - libzypp just registers a callback with libcurl; it's libcurl which needs to call back more often. But this report is about skipping the refresh from the error dialog - the reporter says that even after skipping all the erroneous repos, yast wants to refresh all the repos again. See the initial comment. Ladislav closed my bug here: https://bugzilla.novell.com/show_bug.cgi?id=537883 with WONTFIX. The issue may or may not be related, but clicking "Abort" does nothing either if the repository is unavailable. Surely this could easily be fixed by just having the abort button kill all child processes immediately? OpenSuSE 11.3 no longer displays this behaviour. A user clicking "Skip"receives the message "Error in repository initialisation" and is then taken straight to the package management interface. Should this bug be closed? Yes, thank you very much for testing/verifying! |
Created attachment 254336 [details] yast-skip.png - clicking on the skip button because repo-oss timed out - yast tries to refresh the next repository (repo-non-oss) and times out, clicking skip again - now yast tries to refresh repo-oss again - goes on forever