-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RPM macro "%{_arch}" in source URL is not evaluated #22
Comments
Is there a workaround possible? |
On 2018-01-03 08:26:58 +0000, Oliver Kurz wrote:
## Observation
https://build.opensuse.org/request/show/560971 fails because the source validator fails to parse the rpm macro `%{_arch}` and therefore rejecting the SR.
Hmm we could adapt the obs-service-source_validator to consider the
%{_arch} macro, but IMHO this would be wrong in general, because
- the resulting src.rpm is arch specific (no problem in your case,
but in general)
- the result of a source validator run depends on the arch on which
the source validator is executed
@DimStar77: is it correct that the source validator complains in this
case?
As a workaround/fix: replace %{_arch} with x86_64 in the Source0 tag.
|
Erm.. Mis clicked... So again a summary: The right thing, after thinking about it, would probably be to avoid the arch macro and list the supported ones as source1..source(n) (they have to be in parallel to an ExclusiveArch anyway, as any nonlisted arch would potenitally lead to a non existing source anyway... ) |
ok, I replaced the macro with explicit statement of x86_64. If you don't want to act on this issue in any way, e.g. improve the error feedback, we could close the issue. |
Observation
https://build.opensuse.org/request/show/560971 fails because the source validator fails to parse the rpm macro
%{_arch}
and therefore rejecting the SR.Steps to reproduce
Problem
Seems like https://github.com/openSUSE/obs-service-download_files/blob/master/download_files#L225 evaluates RPM macros but not
%{_arch}
?The text was updated successfully, but these errors were encountered: