|
Bugzilla – Full Text Bug Listing |
| Summary: | RPM signature check fails for release notes package | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Katarina Machalkova <kmachalkova> |
| Component: | Installation | Assignee: | Duncan Mac-Vicar <dmacvicar> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Alpha 4 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
all the internet-test logs showing release-notes download failure.
full YaST2 install logs |
||
|
Description
Katarina Machalkova
2007-05-16 13:16:13 UTC
2007-05-16 14:36:19 <1> linux-wft5(4368) [wfm] clients/inst_do_net_test.ycp:484 Pkg Builtin called: RpmChecksig
2007-05-16 14:36:19 <2> linux-wft5(4368) [zypp] RpmDb.cc(checkPackage):1517 Public key is unavailable. /tmp/YaST2-04368-wtMGHH/1-release-notes.rpm{- 0644 0/0 size 23592}
2007-05-16 14:36:19 <3> linux-wft5(4368) [YCP] clients/inst_do_net_test.ycp:487 checksig of release notes failed
2007-05-16 14:36:30 <3> linux-wft5(4368) [YCP] Report.ycp:484 Cannot install downloaded release notes. RPM signature check failed.
The package seems to be ok rpm --checksig release-notes-10.3.0-23.noarch.rpm release-notes-10.3.0-23.noarch.rpm: sha1 md5 gpg OK And I was able to install the Alpha4 (15th May 2007 release) without any problems. Could you please test it again? Ok, feel free to close as invalid, I was using customized installation source because I've debugged something in installation, hence probably the failure to verify sig. According to comment #3 I'll close this bug report as INVALID. I'm reopening this bug as this has also happened to me when using downloaded i386 CD images of 10.3 alpha4 and configured to use a proxy. From the internet test logs, curl fails to download initially, receiving a 400 error, and so goes direct to www.suse.com (resolved as 195.135.220.3). For some reason, curl appears to retrieve the file but includes the entire binary of the rpm in the log file and then reports a failure. I've attached all the internet-test logs showing the failure. If required, I can supply the full install logs as well. Created attachment 141553 [details]
all the internet-test logs showing release-notes download failure.
Please attach all install logs. Created attachment 142298 [details]
full YaST2 install logs
complete contents of /var/log/YaST2
Purely out of curiosity, is it possible that this bug is related to bug #277117 and the fact that, during stage 2 of the installation, YaST2 doesn't know/trust _any_ gpg keys? It may be that this failure is because YaST2 can't check the signature of the RPM because it doesn't have the key available. I observed the release notes failure bug on a CD install of Alpha 5. *** Bug 290675 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 277117 *** |