|
Bugzilla – Full Text Bug Listing |
| Summary: | yast2 addon creator creates inconsistent metadata | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Jigish Gohil <cyberorg> |
| Component: | YaST2 | Assignee: | Jiří Suchomel <jsuchome> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | mvidner |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | y2log | ||
|
Description
Jigish Gohil
2008-07-28 11:04:42 UTC
It is not changing "anything". It happens when you add/change an RPM while YaST is running and click Create product. The metadata are not recreated. Created attachment 230247 [details]
y2log
logs from the following procedure:
1 start yast addon creator
2 build image
3 start sw_single remove old repo exit
4 start sw_single, add new repo
5 select pattern and try to install - errors
After some debugging, I discovered that add-on-creator has an option to sign the RPMs. The problem is that it does so *after* generating the metadata and thus it makes the RPM checksums invalid. Signing RPMs and the metadata should be separated to prevent this. A workaround is to sign the RPMs beforehand outside add-on-creator. BTW the logs should be more verbose so that I could see all this from them alone ;-) Hm, it probably won't be that easy, create_package_descr is run at the start... Fixed in yast2-add-on-creator-2.17.3 for next release. For 11.0, fixed version is yast2-add-on-creator-2.16.14 and can be found at http://download.opensuse.org/repositories/home:/jsuchome/openSUSE_11.0/noarch/ released |