Bug 260081
| Summary: | Cannot use %{version} consistently for directory naming in rpmbuild | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Philip Ashmore <contact> |
| Component: | rpm | Assignee: | Panu Matilainen <pmatilai> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7 | CC: | pnasrat, triage |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-06-17 02:15:08 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
Philip Ashmore
2007-08-28 13:23:58 UTC
My reason for re-raising this issue lies not with the practice of bundling different packages in the same source RPM - it happens and the "spec" file parser allows it. It lies with the use of the "version" variable. This should be copied to "rpm_version" when first encountered, or ideally from the source RPM package name itself. The reason - one can inspect the "rpmbuild" directory and see the same name-version as is present in the source RPM package - that way you know what version the sources relate to. This issue most obviously surfaced with the "RPM" package itself but I was looking for a pragmatic solution, not an ideal solution that doesn't relate to the real world. I think that being able to identify what source RPM version got installed into the rpmbuild directory by looking at the directory name is definitely worth it. This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists. Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs: http://docs.fedoraproject.org/release-notes/ The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping I would suggest bumping this from Fedora 7 to Fedora 8 as it will continue to be a problem as long as 1. spec files can contain more than one package 2. there isn't a way to specify the originating SRPM version in spec files containing more than one package (I suggested a variable named "rpm_version"). As long as there are sub-packages, there is the potential for multiple
Version: tags. So there is no obvious choice for automagically choosing
a conventional value for %{version}
OTOH, its rather trivial to do
%define my_one_true_version 1.2.3_whatever_you_want
...
Version: %{my_one_true_version}
and then use %{my_one_true_version} instead of %{version}
Alternatively, if you simply _MUST_ use %{version}, the value is likely
to be the same as the last
Version: 1.2.3_whatever_you_want
parsed in the spec file. You can arrange your sub-package stanzas so that the Version: you
want in %{version} appears last.
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. Fedora 7 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |