Bug 456103 - rpm: %if "%{?macro}" == "foo" constructs give error: parseExpressionBoolean returns -1
rpm: %if "%{?macro}" == "foo" constructs give error: parseExpressionBoolean r...
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: rpm (Show other bugs)
rawhide
All Linux
low Severity low
: ---
: ---
Assigned To: Panu Matilainen
Fedora Extras Quality Assurance
:
: 456420 (view as bug list)
Depends On:
Blocks: F10Target
  Show dependency treegraph
 
Reported: 2008-07-21 11:26 EDT by Rex Dieter
Modified: 2008-08-04 02:50 EDT (History)
4 users (show)

See Also:
Fixed In Version: rpm-4.5.90-0.git8444.1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-08-04 02:50:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Rex Dieter 2008-07-21 11:26:49 EDT
Constructs of the form
%if "%{?macro}" == "foo"
are no longer accepted, and yield 
foo.spec:12: parseExpressionBoolean returns -1
errors now
Comment 1 Rex Dieter 2008-07-21 11:28:14 EDT
For example,
http://koji.fedoraproject.org/koji/taskinfo?taskID=722265

We worked-around it by simply avoiding using constructs of that form (I think we
converted easy to a numeric compare instead).
Comment 2 Panu Matilainen 2008-07-22 07:43:27 EDT
Easily reproduced, the regression seems to originate from commit
90eec724a834c26131be11145a62084efe3bafb8.

Florian, please have a look... (I'm on vacation and computer time is somewhat
limited ;)
Comment 3 Panu Matilainen 2008-07-24 03:49:18 EDT
*** Bug 456420 has been marked as a duplicate of this bug. ***
Comment 4 Florian Festi 2008-07-25 06:33:53 EDT
One problem was an parsing error from empty double quoted strings ("") that
happen when %{?macro} in not defined. This is fixed upstream.
Comment 5 Panu Matilainen 2008-08-04 02:50:31 EDT
In rawhide now.

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