On 8/11/20 11:08 AM, Pavel Raiskup wrote:
> 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.
noted.
I'm not sure why that should be expected to work. There's no fallback ... and,
in this case, i expect/require that %{_forge_dist} is def'd. Exactly as it
does in the local mock env.
In any case, if I change in the spec
- %global dist %{?_forge_dist}
+ %global dist %{?_forge_dist}
Name: %{_redis_name}
36 Release: %{dist}
The build fails again, but now at
stderr: error: line 36: Empty tag: Release:
can't parse specfile
I'm stymied as to why COPR build -- which I understood to be a mock env? --
behaves significantly differently than a local mock build.
_______________________________________________
buildsys mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
