scfc reported a new issue against the project: `go-rpm-macros` that you are 
following:
``
On building Go packages, often multiple warnings `grep: warning: stray \ before 
:` are emitted (cf. 
https://kojipkgs.fedoraproject.org/packages/golang-github-d2g-dhcp4client/1.0.0/13.fc40/data/logs/aarch64/build.log):
````
[…]
+ RPM_EC=0
++ jobs -p
+ exit 0
grep: warning: stray \ before :
grep: warning: stray \ before :
grep: warning: stray \ before :
grep: warning: stray \ before :
grep: warning: stray \ before :
grep: warning: stray \ before :
grep: warning: stray \ before :
grep: warning: stray \ before :
Provides: golang(github.com/d2g/dhcp4client) = 1.0.0-13.fc40 
golang-github-d2g-dhcp4client-devel = 1.0.0-13.fc40 
golang-ipath(github.com/d2g/dhcp4client) = 1.0.0-13.fc40
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 
4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Requires: go-filesystem golang(github.com/d2g/dhcp4) 
golang(golang.org/x/sys/unix)
[…]
````
Unfortunately, even with `--verbose` and `--debug`, `edpkg mockbuild` cannot be 
persuaded to reveal which program it is calling that is producing such 
warnings, but I assume that it is `/usr/bin/go-rpm-integration`'s:

````
[…]
for m in version tag commit branch ; do
  v=$(grep "^${m}\:" "${medadatafile}" | head -1)
  v="${v#${m}:}"
  [[ -n "${v}" ]] && metadata["${m}"]="${v}"
done
[…]
````
where the backslash in front of the colon should probably be removed.
``

To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/issue/72
-- 
_______________________________________________
golang mailing list -- golang@lists.fedoraproject.org
To unsubscribe send an email to golang-le...@lists.fedoraproject.org
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/golang@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to