> On 06 Aug 2015, at 15:40, Pat Riehecky <[log in to unmask]> wrote: > > On 08/06/2015 08:37 AM, Paul Millar wrote: >> Hi Pat, >> >> On 06/08/15 15:01, Pat Riehecky wrote: >>> This looks like the same behavior noted in: >>> https://bugzilla.redhat.com/show_bug.cgi?id=594672 >> >> Yes, I think this is the underlying cause. >> >> This "well known" feature of RPM (that macros are expanded, even when commented out) wasn't known to me. It is also inconsistently documented; c.f. >> http://www.rpm.org/max-rpm/ch-rpm-specref.html >> and >> http://www.rpm.org/max-rpm-snapshot/ch-rpm-specref.html >> >> [Unfortunately, it seems nearly impossible to report this inconsistency to whoever maintains the Max RPM documentation, so the incorrect documentation will likely linger, *sigh*] >> >> That all said, given how macros are expanded, I think it's fair to say that the previous successful builds worked-by-accident, and there is no regression. >> >> Sorry for the noise. >> >> Paul. > > No worries, I didn't know about this "well known" behavior until it bit me too.... Me too :-) And BTW, it's not even a change to rpmbuild. It's just the new dependency on redhat-rpm-config, which causes the buildroot to be cleared at the beginning of %install. Note that this has various other side effects. Stephan -- Stephan Wiesand DESY - DV - Platanenallee 6 15738 Zeuthen, Germany