Go leaves will be mass retired in one month
by Maxwell G
(Resending as it seems this didn't reach the ML the first time...)
Hi Fedorians,
Changes/Mass_Retire_Golang_Leaves [1] has been approved by FESCo. As
part of this Change, all Go library packages that are leaves will be be
mass retired and removed from the Fedora 39 repositories in
approximately one month.
The following maintainers/groups own co-maintain or watch at least one
package that we have identified as a leaf:
@deepinde-sig
@go-sig
@osbuild-sig
agerstmayr
anthr76
athoscr
atim
carlwgeorge
dcavalca
dctrud
eclipseo
fab
fale
fuller
gundersanne
jchaloup
jdoss
jjelen
laiot
logic
mayorga
mgoodwin
nathans
obudai
pwouters
qulogic
rga
rominf
yanqiyu
I will forward this message to those users separately instead of BCCing.
Apparently, some people have broken filters that hide any email sent to
the ML even if it's addressed to them directly.
See [2] for a full list of leaves and [3] for a maintainer by maintainer
breakdown. Maintainers may opt out by cloning
https://pagure.io/GoSIG/go-leaves/ and pushing an `opt-out/{PKGNAME}`
file with a short justification.
Something like:
```
git clone ssh://git@pagure.io/GoSIG/go-leaves.git
cd go-leaves
echo "Dependency for foo (review bug #XXXXX)" > ./opt-out/bar
git add ./opt-out/bar
git commit -m "opt out bar"
git push origin
```
All Go SIG members have write access to this repository. Other users can
submit a pull request. You're also welcome to file an issue and I'll
push the file for you.
After a month has passed, we'll remove Go SIG write access from the
repository and stop accepting additional opt-outs. Then, we'll preform
test builds in Copr to make sure there's no false positives in the list.
Finally, I'll verify the results, opt out any additional false
positives, and preform the mass retirement. As usual, anybody can
unretire packages without a re-review within eight weeks by filing a
releng ticket.
[1] https://fedoraproject.org/wiki/Changes/Mass_Retire_Golang_Leaves
[2] https://pagure.io/GoSIG/go-leaves/blob/main/f/leaves
[3] https://pagure.io/GoSIG/go-leaves/blob/main/f/leaves-by-maintainer
Thank you for your cooperation,
--
Maxwell G (@gotmax23)
Pronouns: He/They
2 months, 3 weeks
Using %gobuildflags with %meson
by Link Dupont
I have a package[1] that I'm updating to a new upstream version. Upstream, the project uses meson to compile the binaries (written in Go), as well as generate and install a number of data files. I want to use meson to compile and install the project downstream because I feel meson does a good job managing all the data files and installation directories.
I am trying to replicate the logic of the %gobuild macro so that I can continue to use meson *and* use as much of the go-rpm-macros as possible, with as little duplication as possible. Upstream, I have defined custom_targets[3] for the Go binaries with the following command array:
> [go, 'build', gobuildflags, '-o', '@OUTPUT@', '-ldflags', goldflags, packagename]
gobuildflags is an array that is constructed[4] from a meson build option[3].
In my spec %build, I attempt to set the gobuildflags meson build option like so:
> %meson -Dgobuildflags=%{shescape:%gobuildflags}
When meson parses the incoming gobuildflags value and splits the string into an array, it separates the value of the -tags flag into two separate single-quoted command line arguments like this (extracted from the resulting ninja.build):
> COMMAND = /usr/bin/go build -buildmode pie -compiler gc '-tags="rpm_crashtraceback' '$${BUILDTAGS:-}"' ...
Is there some other way I can pass the output of %gobuildflags into meson as a build option that doesn't split apart the double-quoted values like this?
1: https://src.fedoraproject.org/rpms/yggdrasil
2: https://github.com/RedHatInsights/yggdrasil/blob/main/cmd/yggd/meson.buil...
3: https://github.com/RedHatInsights/yggdrasil/blob/main/meson_options.txt#L4
4: https://github.com/RedHatInsights/yggdrasil/blob/main/meson.build#L25
3 months
