On Tuesday, August 11, 2020 5:28:16 PM CEST PGNet Dev wrote:
On 8/10/20 10:47 PM, Pavel Raiskup wrote:
> Usually it is enough to use '%{?_pgnd_macros}' variant (see the question
> mark). For the purpose of generating source RPM, the macros aren't
> usually needed.
using
- '%{pgnd_macros}'
+ '%{?_pgnd_macros}'
the build does NOT fail for the reason the macro file itself isn't found
but the build still FAILs because the macros it's supposed to provide aren't
found.
e.g.,
https://download.copr.fedorainfracloud.org/results/pgfed/redis-6/srpm-bui...
It actually succeeded, but copr failed to further work with that src.rpm
over http protocol through AWS caching because of the special characters
in URL -- it was caused by unexpanded macro (I deduce):
stderr: warning: line 36: Possible unexpanded macro in: Release:
%{_forge_dist}
Perhaps the %_forge_dist macro needs to be used with question mark as well?
Similarly to how the %dist macro is used?
Release: 1%{?dist} => Release: 1%{?_forge_dist}
But I don't know; I never used it.
Pavel