|
Bugzilla – Full Text Bug Listing |
| Summary: | update stalls - completion not signalled | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Robert Harvey <bobharvey> |
| Component: | libzypp | Assignee: | E-mail List <zypp-maintainers> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Enhancement | ||
| Priority: | P4 - Low | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | openSUSE 11.0 | ||
| Whiteboard: | |||
| Found By: | Community User | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Screenshot showing state the updater froze at
the only log file I can find that has updated today and seems relevant |
||
|
Description
Robert Harvey
2008-12-20 16:17:26 UTC
Created attachment 261598 [details]
Screenshot showing state the updater froze at
Created attachment 261599 [details]
the only log file I can find that has updated today and seems relevant
rpm was running indefinitely, after the install completed. I have rebuilt the database for rpm and re-installed opera without problems. I feel that there should be some detection for failures in rpm, including looping indefinitely, in the package manager That is hard to detect, i'm afraid there is not much we can do here. Anyway the resolution of 'FATURE' is used only if the feature is tracked in Fate (our feature tracking software), changing to enhancement, maybe others think there is something to improve here. This is basically about detecting rpmdatabase corruptions. *** This bug has been marked as a duplicate of bug 308352 *** |