| Summary: |
sw management - [abort] doesn't on package retrieval failure |
| Product: |
[openSUSE] openSUSE 11.1
|
Reporter: |
David Rankin <drankinatty> |
| Component: |
YaST2 | Assignee: |
E-mail List <bnc-team-screening> |
| Status: |
RESOLVED
DUPLICATE
|
QA Contact: |
Jiri Srain <jsrain> |
| Severity: |
Normal
|
|
|
| Priority: |
P5 - None
|
CC: |
forgotten_--EoyBps8f
|
| Version: |
Final | |
|
| Target Milestone: |
--- | |
|
| Hardware: |
x86-64 | |
|
| OS: |
Other | |
|
| Whiteboard: |
|
|
Found By:
|
---
|
Services Priority:
|
|
|---|
|
Business Priority:
|
|
Blocker:
|
---
|
|---|
|
Marketing QA Status:
|
---
|
IT Deployment:
|
---
|
|---|
Devs, Using the GUI interface to yast software management to perform package updates, if a package retrieval failure occurs, you are presented with the options 'retry' 'abort' 'skip'. Choosing 'abort' doesn't 'abort' but instead acts like 'skip'. This problem occurred when performing package updates on 11.1 using the 'update if never version available' option to perform a system wide update. The KDE:/qt44 repository was evidently out of sync and none of the packages from that repository were available. Upon the first and second failed retrieval, I attempted a 'retry' unsuccessfully and chose 'skip'. After I figured out it was the whole qt44 repository, I decided to 'abort' the update instead of having to 'skip' through the entire repo. However, choosing 'abort' had no effect other than to 'skip' to the next package. Choosing 'abort', I expected the update to 'abort' and run SuSE config on the installed packages and be done. Instead, I had to 'abort' through every package in the qt44 repo *before* the abort took effect. 'abort' should abort. I'll post the y2logs in a follow up. Let me know if you want me to send anything else. Thanks.