Bug 9091
Summary: | %files -f doesn't work like it should | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Oliver Jones <oliver> |
Component: | rpm | Assignee: | Jeff Johnson <jbj> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | ||
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: | 2001-04-03 12:19:46 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
Oliver Jones
2000-02-03 12:07:51 UTC
The file name is relative to the build directory (/usr/src/redhat/BUILD/pkgname-version/) This has been the behavior of rpm from inception AFAIK. I'll try to permit an absolute file name after rpm-3.0.4 is released. Even if absolute paths names are not possible. Just changing the error message to provide the full path that rpm tried to open (rather than just the supplied string) would help in debuging. In my case I was making a package that didn't have a BUILD/%{name}-%{version}/ directory hence I could not find where to put the file list. Fixed in CVS, will be in rpm-3.0.4-0.43. FWIW, using absolute paths in a spec file is almost always the wrong thing to do. Well. In this case it would have helped _a lot_. There is always a case for doing something 'different'. Supporting the 'different' behaviour doesn't mean advocating it. This problem appears to be resolved. Please reopen if I'm wrong. |