|
Bugzilla – Full Text Bug Listing |
| Summary: | database disk image is malformed | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Bernhard Walle <bwalle> |
| Component: | libzypp | Assignee: | Duncan Mac-Vicar <dmacvicar> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Duncan Mac-Vicar <dmacvicar> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Bernhard Walle
2007-10-12 09:44:33 UTC
is there a .journal file in the same dir? No: kepler:/var/cache/zypp # find -name '*journal*' kepler:/var/cache/zypp # Sorry, we can't help with the information available (in order to reproduce it), I guess some abnormal termination of zypper or YaST corrupted the cache. (Ctrl-C?). That may be true. But: The average user is lost here! If the database is corrupted, then yast/zypper must recover automatically by deleting the cache und creating a new one. Letting the user do this is not an option IMO. I agree, I haven't said that the bug is not important, the point is the report does not help to find the cause of the bug in any way. *** This bug has been marked as a duplicate of bug 337657 *** |