Bugzilla – Bug 156031
YAST 2 Package Manager doesn't Skip package, but aborts
Last modified: 2006-04-07 12:42:53 UTC
When a package is unreadable on a repository (due to refresh or network errors), clicking Skip doesn't move on to the next package as it did in 10.0, but has the same affect as Abort, it stops downloading all packages and exits the download process and runs the config scripts before asking if you want to add or remove more packages or exit.
Please notice bug #154090 Does the abort-button work in the intended way? Please attach the yast logfiles in /var/log/YaST2
Abort works correctly. Not at beta machine currently, will post logs shortly.
Reassigning to Klaus, not sure if this is backend-related.
Created attachment 71808 [details] y2log per request
Created attachment 71812 [details] y2logRPM per request Do you need any of the other log files in addition to these two?
If the media change callback returns SKIP, there is no way how SourceImpl::provideFile() can inform the caller about the user's choice.
*** Bug 157549 has been marked as a duplicate of this bug. ***
Stano, what should be done here?
We need to introduce a new kind of exception for Source providing a file, so the user selected to skip this package. TargetImpl::commit() then needs to catch the exception and behave accordingly. Klaus, any idea who could fix this?
Working on it
Fix in libzypp rev. 2987
Works in build 906.
great, thanks a lot you guys rock :-)