|
Bugzilla – Full Text Bug Listing |
| Summary: | Online Update issues 2 very unusual errors and was unsucessfull | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Scott Couston <scott> |
| Component: | libzypp | Assignee: | Michael Andres <ma> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i386 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
.txt error message
1 of 3 yast log files 2 of 3 yast log files 3 of 3 yast log files |
||
|
Description
Scott Couston
2007-04-11 07:38:47 UTC
Created attachment 130298 [details]
.txt error message
Created attachment 130300 [details]
1 of 3 yast log files
Created attachment 130304 [details]
2 of 3 yast log files
Created attachment 130306 [details]
3 of 3 yast log files
The appears to be no subsequent re-try in a different online update session if a patch is skipped - how are files that fail checksum or just plain fail to be installed handled. I have never witnessed a skipped file or failed download file; attempt to be re-installed at a different online update session. Sorry to raise a separate issue here, but there is no clear information on redundancy onine updates
I don't know where these error messages (Exception.cc(log):94 error: error(-30977) getting "unix.conf" records from Basenames index) are coming from - reassigning to libzypp people to find out more. Additional information - RPM database required rebuild after error. Theses error comes from 2007-04-11 17:20:58 <0> multivac-ii(4196) [zypp] ExternalProgram.cc(start_program):172 Executing 'rpm' '--root' '/' '--dbpath' '/var/lib/rpm' '-U' '--percent' '--' '/var/adm/mount/AP_0x0000000b/rpm/i586/qt3-devel-3.3.7-14.i586.rpm' It seems that your rpm-DB has been completely corrupted at that moment. Michl, could you please check it too ? The DB is broken. *** This bug has been marked as a duplicate of bug 263698 *** |