Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 133623 - rpm 4.2.x doesn't handle %{perl_vendorlib}, %{perl_vendorarch} and more
rpm 4.2.x doesn't handle %{perl_vendorlib}, %{perl_vendorarch} and more
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: rpm (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2004-09-25 06:23 EDT by Robert Scheck
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-26 13:38:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Robert Scheck 2004-09-25 06:23:23 EDT
Description of problem:
rpm 4.2.x of Red Hat Enterprise Linux 3 isn't able to handle 
%{perl_vendorlib} correct, but %{perl_sitearch} and %{perl_archlib}

Version-Release number of selected component (if applicable):

How reproducible:
Everytime, see below.

Steps to Reproduce:
1a. Use "%{perl_vendorlib}" in a spec file
1b. Use "%{!?perl_vendorlib: %define perl_vendorlib %(eval "`%{__perl} -V:installvendorlib`"; echo $installvendorlib)}" 
    and "%{perl_vendorlib}" in a spec file
2. Build the RPM.
3. Try to install the RPM.
4. Die with: "/usr/lib/perl5/vendor_perl/5.8.0 is needed by XYZ".
5. /usr/lib/perl5/vendor_perl/5.8.0 exists, see:
   # file /usr/lib/perl5/vendor_perl/5.8.0
   /usr/lib/perl5/vendor_perl/5.8.0: directory
Actual results:
%{perl_vendorlib} isn't working.

Expected results:
Working %{perl_vendorlib}.
Comment 1 Robert Scheck 2004-09-25 06:32:59 EDT
BTW, %{perl_vendorarch}, %{perl_sitelib} and %{perl_privlib} don't 
also work as expected.
Comment 2 Jeff Johnson 2004-09-26 13:38:03 EDT
The fix for this is to upgrade RHEL3 to rpm-4.3.x, not otherwise.

The problem exists for any additional change to default rpm
configuration, exists for all versions of rpm prior to rpm-4.3,
not just RHEL3. You can add the macros to what was then the
rpm default configuration.

Note You need to log in before you can comment on or make changes to this bug.