Bug 136383
| Summary: | /tmp/myrequires should be handled otherwise | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Cluster Suite | Reporter: | Jos Vos <jos> |
| Component: | gfs | Assignee: | Chris Feist <cfeist> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | GFS Bugs <gfs-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3 | ||
| 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: | 2009-12-22 20:38:49 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: | |||
The "%define .." should indeed be moved after "Source1: ..." in that case, I just checked. This bug will be fixed in the next build of GFS for RHEL-3. It appears the best solution is the put the my_requires file into the %_buildir directory which allows us to keep everything in the .spec file and not distribute extra files to build the rpm. Cleanup. This bugzilla should be resolved with the current packages from RHN for Red Hat Global File System for Red Hat Enterprise Linux 3. GFS-6.0.2.36-9 |
Description of problem: The spec file now creates a /tmp/myrequires in the core of the spec file. The right way (or at least a better way) to do this is to include the file, say gfs-requires, as Source1 and %define __find_requires %{SOURCE1} (it might be that the %define should be after the Source1, I don't know for sure). The problem with /tmp/my_requires is that builds might conflict w.r.t. ownership etc. The simple example I saw was a -bs done as root followed by a --rebuild done as a normal user, which caused errors because the file was owned by root. If more packages would use a similar method, this would even cause everything being screwed up. Version-Release number of selected component (if applicable): 6.0.0-15