Bug 11319 - Strange error if .rpmmacros is wrong
Summary: Strange error if .rpmmacros is wrong
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
(Show other bugs)
Version: 6.2
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-05-09 04:05 UTC by crichton
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-05-09 16:54:13 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description crichton 2000-05-09 04:05:02 UTC
Something weird happens if the format of the .rpmmacros file is wrong:

If I do:

"%_topdir   /home/crichton/srpm"

I get:

Failed to rename /usr/share/locale/en_US/LC_MESSAGES/libc.mo to
/usr/src/redhat/SPECS/rpm-spec.1GN3Nd: Permission denied: No such file or
directory

If the quotes are gone, things work.

I have a funny feeling about this one...

RPM is stock from Zoot, no errata fixes applied.

Comment 1 Jeff Johnson 2000-05-09 16:54:59 UTC
This is basically a configuration problem, and rpm should arguably enforce
stricter rules in parsing the macros file (current behavior is to ignore
any lines, after trimming leading white space, that do not begin with a leading
'%').

Trying to build with a broken configuration (i.e. the correct value for %_topdir
was not set) can lead to all sorts of weirdness, as the _topdir value is used
to construct almost all of rpm's paths.

Try alka-seltzer for the "funny feeling", it ain't what you think it is :-)

Comment 2 Jeff Johnson 2000-05-09 16:56:59 UTC
OOPs, yes it was you think it is, freed memory used in an error message.
This is fixed in the tree.


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