rishi opened a new pull-request against the project: `go-rpm-macros` that you are following:
``
Revert "Set _dwz_low_mem_die_limit only when a go binary is built"
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/71
Dear all,
You are kindly invited to the meeting:
Go SIG meeting on 2025-04-21 from 20:00:00 to 21:00:00 Europe/Madrid
At fedora-meeting-1(a)irc.libera.chat
The meeting will be about:
The regular meeting of Go SIG at the [fedora-meeting-1 room](https://matrix.to/#/#meeting-1:fedoraproject.org).
For the proposed agenda, please refer to the [tagged tickets](https://pagure.io/GoSIG/go-sig/issues?status=Open&tags=meeting).
Source: https://calendar.fedoraproject.org//meeting/10699/
Dear all,
You are kindly invited to the meeting:
Go SIG meeting on 2025-04-07 from 20:00:00 to 21:00:00 Europe/Madrid
At fedora-meeting-1(a)irc.libera.chat
The meeting will be about:
The regular meeting of Go SIG at the [fedora-meeting-1 room](https://matrix.to/#/#meeting-1:fedoraproject.org).
For the proposed agenda, please refer to the [tagged tickets](https://pagure.io/GoSIG/go-sig/issues?status=Open&tags=meeting).
Source: https://calendar.fedoraproject.org//meeting/10699/
Hi,
This is a heads-up regarding the impact of Go 1.24, now available in
Fedora, and the subsequent mass-rebuild for Fedora 42. Over 200
packages are currently failing to build from source (FTBFS) [1] due to
a stricter check introduced in Go 1.24 [2].
The failure occurs due to a stricter vet check requiring non-constant
format strings to be explicitly handled. Affected builds fail with an
error like:
non-constant format string in call to <function_name>
The failures typically occur during the %check phase, which is why
"source-only" packages are also affected.
Fixing this issue is relatively simple, and some patches have already
been submitted upstream [3][4]. However, addressing all affected
packages downstream will likely take several months.
Best regards,
Mikel
[1] https://koschei.fedoraproject.org/groups/go-sig?collection=f42
[2] https://tip.golang.org/doc/go1.24#vet
[3] https://github.com/coreos/ignition/pull/2000
[4] https://github.com/opentofu/opentofu/pull/2390
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…)
````
[…]
+ 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