Bug 129396
Summary: | make rpm creates erroneous version number | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | superbnerd <superbnerd> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED UPSTREAM | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | pfrields, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-11-19 04:11:58 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
superbnerd
2004-08-07 21:04:00 UTC
that's most likely intentional from the folks who implemented make rpm, you can't have more dashes the way you suggest. everything after teh last dash HAS to be the release of the rpm, and everything before it and the last-but-one dash is the "upstream" version. So here the pacakge is called "kernel", the upstream (eg our version) gets truncated to "2.6.71.494.2.2custom" and the release is "1" the real problem is that when you want to upgrade to a security fixed kernel, it won't becuase it thinks you have a newer kernel installed. 2.6.71 is assumed larger than say 2.6.8. So yum and up2date updates never succeed unless you do them manually. I would suggest that you contact the make rpm person or ask on linux-kernel.org since this is more of a generic problem than our problem, and, well, we ship a way to make "nice" rpms... it's just not "make rpm" so I can't justify spending a whole lot of time "fixing" make rpm, since the end isn't in sight that way. |