Description of problem:

Somehow the usage of %systemd_postun changes the rest of spec file and prevents it from using the %if statement in the %files section. This makes no sense. It *looks* like somehow the usage of any systemd macro is unsetting %xml. 


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

RHEL7 

RPM version 4.11.1
How reproducible:

Always



I have an odd rpm building issue. I ran into this on a much larger spec file, but for simplicity I have reduced it the minimum amount of spec file required to reproduce the bug. I am well aware that if this spec file would build a SRPM, that SRPM would FTBFS. I also know parts of this spec violate Fedora packaging guidelines. Again, this is just an example.

I removed all BR, Requires, %changelog, %prep, patches etc. 


Given the following spec file: 

===
%{!?xml:%define xml 1}

Summary:        An example of a bug
Name:           example
Version:        9.2.7
Release:        11
License:        MIT
Group:          Applications/Databases
Url:            http://www.example.org
# This is a dummy source, just touch example.tar.gz in ~/rpmbuild/SOURCES
Source0:        example.tar.gz

%description
I removed lots of normal stuff just to show this as a bug.

%install
rm -rf %{buildroot}

%postun
%systemd_postun %{name}.service

%files
%defattr(-,root,root)
%if %xml
/opt/lib/example/example.so
%endif
===

This is on EL7.

The goal here is build a SRPM I can build using mock.

I would normally run 

rpmbuild -bs --nodeps example.spec 

to do this.

-bash-4.2$ rpmbuild -bs --nodeps example.spec
error: parse error in expression
error: /home/stahnma/rpmbuild/SPECS/example.spec:24: bad %if condition


If I move %post under the %files section, the SRPM builds.

If I comment out the %systemd_postun line (including commenting out the macro), the SRPM builds. 

If I change the if %xml to if 0%{xml} < 1, the SRPM builds.

If I manually expand the %systemd_postun macro, and literally put that text in the %post stanza, the SRPM builds. 

-bash-4.2$ rpm --eval "%systemd_postun example.service"

/usr/bin/systemctl daemon-reload >/dev/null 2>&1 || :


Somehow the usage of %systemd_postun changes the rest of spec file and prevents it from using the %if statement in the %files section. This makes no sense. It *looks* like somehow the usage of any systemd macro is unsetting %xml. 

Just for fun, I tried other systemd macros. The same failure occurs when using systemd_post, systemd_postun_with_restart, systemd_preun
Also, if I change the %postun stanza to %post, or %pre it also still happens. 

I also, just for fun, renamed %xml to %foo. The exact same behavior occurs.


I can work around this bug using one of the many methods described above, I am just not sure where the bug is. It could be in rpmbuild, it could be in systemd macros.