|
Bugzilla – Full Text Bug Listing |
| Summary: | Product Creator creates product without content asc | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | Dean Hilkewich <deanjo> |
| Component: | YaST2 | Assignee: | Ladislav Slezák <lslezak> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | dmacvicar, jsuchome |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | openSUSE 11.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | y2log: starting installation with unsigned source | ||
|
Description
Dean Hilkewich
2009-04-18 17:43:28 UTC
content.asc is only created for signed products Then shouldn't there be some sort of check to see if the product is to be bootable as it allows you to create such a product that is unusable? True. Created attachment 287035 [details]
y2log: starting installation with unsigned source
Why does zypp report error on missing content.asc when unsigned source is used? Could it be suppressed somehow? I tried it using HAE and deleting the .asc and .key file:
> sudo zypper ref hae
File 'content' is unsigned, continue? [yes/_no_]: y
Retrieving repository 'hae' metadata [done]
Building repository 'hae' cache [done]
Specified repositories have been refreshed.
So I can't reproduce what you mean.
Did you check the log? There's 2009-04-21 07:35:54 <5> linux(2923) [zypp] Exception.cc(log):119 MediaHandler.cc(getFile):1234 THROW: MediaHandler.cc(getFile):1234: File '/content.asc' not found on medium 'cd:///?devices=/dev/sr0' 2009-04-21 07:35:54 <5> linux(2923) [zypp] Exception.cc(log):119 2009-04-21 07:35:54 <5> linux(2923) [zypp] Exception.cc(log):119 MediaSetAccess.cc(provideFileInternal):282 CAUGHT: MediaHandler.cc(getFile):1234: File '/content.asc' not found on medium 'cd:///?devices=/dev/sr0' 2009-04-21 07:35:54 <5> linux(2923) [zypp] Exception.cc(log):119 Jano, can you tell anything about it? Yes, zypp complains when the repo is not sined and UIs are supposed to ask the user whether to continue despite of that. But the UI should not get a "media" error, but the "repo unsigned" error, like in c#6. It seems the error happens, because yast specifically uses just the media backend via SourceProvideSignedFile builtin: 2009-04-21 07:35:54 <1> linux(2923) [Pkg] Packages.ycp:986 Pkg Builtin called: SourceProvideSignedFile If the requested file is not signed, the call (rightfully so :O) fails. Ehm - Ladislav, seems that in some cases, SourceProvideSignedFile should not be used... I looked at the code of Fetcher, and if you ask for a digested file, the following things are expected: - file checksum is listed in some index, index is retrieved and checked for signatures. If signature does not exist, the signature and key are optional so it does not fail and ask the user to confirm unsigned file (for the index). A digested file is a file mentioned in some index (for use with signed checksum indexes like content or SHA1SUMS) or a filename + a known checksum. Note that Fetcher has no concept of "signed files", like the index itself or content itself which need to be retrieved using enqueue + a SignatureFileChecker. I don't know the context in which YaST downloads content file itself. 11.1 is out of openSUSE scope. As this is pre-ruby yast migration please open a new issue against current codestream if the issue is still present. |