October 2022 - golang - Fedora mailing-lists

[go-rpm-macros] Issue #2: EPEL availability
by Nicolas Mailhot 29 Mar '24

29 Mar '24

nim reported a new issue against the project: `go-rpm-macros` that you are following: `` The macro code needs massaging to also work on EPEL. Most of the work is spec side since some of the macros are going to collide with the ones provided by previous iterations of Go macro packages `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/issue/2

2 4

[go-rpm-macros] Issue #3: %goprep should apply patches automatically
by Nicolas Mailhot 29 Mar '24

29 Mar '24

nim reported a new issue against the project: `go-rpm-macros` that you are following: `` `%goprep` should apply patches automatically, so there is no convenience gap with `%autosetup`. This is generic work that should be done *redhat-rpm-config* side in forge macros and then reused in`%goprep`. Basically: 1. define a `patch_flags<suffix>` rpm variable holding the parameters that should be passed to `%patch<suffix>` 2. define a `default_flags<suffix>` fallback 3. define a `source_patches<suffix>` holding an ordered space separated list of patch suffixes associated with a particular forge/go source. And then write the usual lua loops to apply it all at the right moment in the spec. `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/issue/3

6 9

[go-rpm-macros] Issue #36: Renaming BUILDTAGS and LDFLAGS to include GO prefixes
by Link Dupont 29 Mar '24

29 Mar '24

linkdupont reported a new issue against the project: `go-rpm-macros` that you are following: `` In #34 and #35, it was brought up to rename the `BUILDTAGS` variable to `GOBUILDTAGS` in order to be more explicit about the intended use of the variables and to avoid any potential namespace collision with other variables. I looked into what packages are using `BUILDTAGS` today to figure out how much of an impact a rename like this will have. As of this writing, the following packages are using `BUILDTAGS` in some capacity: ``` buildah.spec containernetworking-plugins.spec cri-tools.spec go-compilers.spec golang-github-prometheus-node-exporter.spec golang-github-prometheus.spec grafana.spec hugo.spec moby-engine.spec oci-seccomp-bpf-hook.spec pack.spec podman.spec reg.spec runc.spec skopeo.spec snapd.spec source-to-image.spec stargz-snapshotter.spec syncthing.spec weldr-client.spec ``` And the follow packages use `LDFLAGS`: ``` aerc.spec age.spec butane.spec clash.spec containerd.spec doctl.spec fzf.spec geoipupdate.spec git-lfs.spec golang-github-aliyun-cli.spec golang-github-colinmarc-hdfs-2.spec golang-github-haproxytech-dataplaneapi.spec golang-github-hub.spec golang-github-jsonnet-bundler.spec golang-github-magefile-mage.spec golang-github-prometheus.spec golang-github-rfjakob-gocryptfs.spec golang-github-tdewolff-minify.spec golang-github-theoapp-theo-agent.spec golang-mvdan-editorconfig.spec ignition.spec kiln.spec micro.spec open-policy-agent.spec osbuild-composer.spec rclone.spec reg.spec source-to-image.spec syncthing.spec tinygo.spec vgrep.spec weldr-client.spec ``` I identified these packages by grepping the contents of the [current spec tarball](https://src.fedoraproject.org/repo/rpm-specs-latest.tar.xz). To avoid breaking these packages that are currently using `BUILDTAGS` or `LDFLAGS`, there are two possible approaches I see to safely rename the variables: #### 1. Rebuild everything in a side-tag Patch `go-rpm-macros` to rename `BUILDTAGS` and `LDFLAGS` to `GOBUILDTAGS` and `GOLDFLAGS` respectively. Then patch the above packages and stage them all in a side-tag to update them in one monolithic Bodhi update. #### 2. Support both old and new variables at the same time Patch `go-rpm-macros` to support **both** `BUILDTAGS`/`LDFLAGS` *and* `GOBUILDTAGS`/`GOLDFLAGS` simultaneously. Then patch the above packages over time until everything has been ported over to using `GOBUILDTAGS` and `GOLDFLAGS`, and then drop the old variables from `go-rpm-macros`. I'm not sure how easy either of these approaches will be. They are both moving targets as new packages are constantly getting added. It might just be a constant effort to try and keep on top of all the patches as new packages come along and patches need to be rebased onto their target's changes. `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/issue/36

4 5

[go-rpm-macros] Issue #46: %gobuildflags missing double quotation marks
by Petr Hruska 29 Mar '24

29 Mar '24

hruskape reported a new issue against the project: `go-rpm-macros` that you are following: `` It seems that commit https://pagure.io/go-rpm-macros/c/359d80bbfe7f0490fc51c43af8d986863516c5bb?… breaking %gobuildflags usage in spec file. Getting error, as double quotation marks are removed. Specfile section unset LDFLAGS %make_build GOBUILDFLAGS="%{gobuildflags}" Error: + /usr/bin/make -O -j16 V=1 VERBOSE=1 'GOBUILDFLAGS=-buildmode pie -compiler gc -tags=rpm_crashtraceback' ' -ldflags ' -B 0x3433f3bcad171c4e7f8f736da295a9fac8289b8c -compressdwarf=false -extldflags '-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -a -v -x' /usr/bin/make: invalid option -- 'c' /usr/bin/make: invalid option -- 'x' Usage: make [options] [target] ... `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/issue/46

2 3

[go-rpm-macros] PR #41: Convert LDFLAGS to GOLDFLAGS and BUILTAGS to GOBUILDTAGS
by Robert-André Mauchin 15 Mar '24

15 Mar '24

eclipseo opened a new pull-request against the project: `go-rpm-macros` that you are following: `` Convert LDFLAGS to GOLDFLAGS and BUILTAGS to GOBUILDTAGS `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/pull-request/41

2 1

Thread to send your Golang package reviews which are waiting
by Robert-André Mauchin 07 Mar '23

07 Mar '23

Thread to send your Golang package reviews which are waiting... reply to this thread so we can sync up our efforts. Best regards Robert-André

5 6

[golist] PR #30: Don't skip testdata
by Matyáš Kroupa 22 Feb '23

22 Feb '23

krouma opened a new pull-request against the project: `golist` that you are following: `` Don't skip testdata `` To reply, visit the link below or just reply to this email https://pagure.io/golist/pull-request/30

3 3

[go-rpm-macros] PR #34: Add BUILDTAGS to %gobuildflags
by Brian C. Lane 21 Feb '23

21 Feb '23

bcl opened a new pull-request against the project: `go-rpm-macros` that you are following: `` Add BUILDTAGS to %gobuildflags `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/pull-request/34

7 19

[golist] PR #29: Deduplicate CollectProjectDeps
by Matyáš Kroupa 21 Feb '23

21 Feb '23

krouma opened a new pull-request against the project: `golist` that you are following: `` Deduplicate CollectProjectDeps `` To reply, visit the link below or just reply to this email https://pagure.io/golist/pull-request/29

2 1

[Fedocal] Reminder meeting : Go SIG
by jcajka＠fedoraproject.org 23 Oct '22

23 Oct '22

Dear all, You are kindly invited to the meeting: Go SIG on 2022-10-24 from 20:00:00 to 21:00:00 Europe/Prague At fedora-golang(a)libera.chat The meeting will be about: Fedora's Go SIG meeting More information available at: [https://pagure.io/GoSIG/go-sig/](https://pagure.io/GoSIG/go-sig/) Source: https://calendar.fedoraproject.org//meeting/10012/

1 0

Building package with dependencies and submitting for update
by Mark E. Fuller 17 Oct '22

17 Oct '22

Hi All, As I wrote previously, one of my packages has a new dependency. How do I build the package and its dependency together and submit them as an update together? Is this what the buildroot overrides are for? Thanks

2 1

Review Swaps
by Mark E. Fuller 16 Oct '22

16 Oct '22

Hi all, I have two packages for which I'd like to offer to swap reviews: 1) Bug 2135036 - Review Request: golang-github-sajari-fuzzy https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2135036 This is a new dependency blocking an update to one of my existing (Go) packages. Autogenerated spec, should be a trivial review. 2) Bug 2126785 - Review Request: usbrelay https://bugzilla.redhat.com/show_bug.cgi?id=2126785 USB-connected electrical relay control, based on hidapi Thank you -- Mark E. Fuller, Ph.D. fuller(a)fedoraproject.org fuller(a)mefuller.dev @fuller:fedora.im @fuller:one.ems.host https://mefuller.dev PGP Fingerprint: 73F1 A30C BDF4 DB4B C75F FD0F D599 E76C FFCA BF60

2 1

[Fedocal] Reminder meeting : Go SIG
by jcajka＠fedoraproject.org 09 Oct '22

09 Oct '22

Dear all, You are kindly invited to the meeting: Go SIG on 2022-10-10 from 20:00:00 to 21:00:00 Europe/Prague At fedora-golang(a)libera.chat The meeting will be about: Fedora's Go SIG meeting More information available at: [https://pagure.io/GoSIG/go-sig/](https://pagure.io/GoSIG/go-sig/) Source: https://calendar.fedoraproject.org//meeting/10012/

1 0

RE: SPR no. 34791 - SENEGINDIA Enquiry No. 2977
by Ved＠fedoraproject.org 05 Oct '22

05 Oct '22

1 0

Hashicorp Consul Packages
by Mark E. Fuller 01 Oct '22

01 Oct '22

In my continuing work on building terraform[0], I have a what appears to be a version conflict between two hashicorp consul packages: ... Error: Transaction test error: file /usr/share/gocode/src/github.com/hashicorp/consul/.goipath conflicts between attempted installs of golang-github-hashicorp-consul-sdk-devel-0.7.0-5.fc37.noarch and golang-github-hashicorp-consul-api-devel-1.9.1-7.fc38.noarch file /usr/share/gocode/src/github.com/hashicorp/consul/CHANGELOG.md conflicts between attempted installs of golang-github-hashicorp-consul-sdk-devel-0.7.0-5.fc37.noarch and golang-github-hashicorp-consul-api-devel-1.9.1-7.fc38.noarch file /usr/share/gocode/src/github.com/hashicorp/consul/go.mod conflicts between attempted installs of golang-github-hashicorp-consul-sdk-devel-0.7.0-5.fc37.noarch and golang-github-hashicorp-consul-api-devel-1.9.1-7.fc38.noarch ... Both of these packages (see [1] and [2]) are derived from the same repo, github.com/hashicorp/consul. My question is, why are there two packages pointing to the same repo? (Yes, I realize it is two different modules within it, but could they be merged?) Second, is there a way I can address this conflict on my end or are modifications to one or both of the consul packages required to resolve the issue? [0] https://download.copr.fedorainfracloud.org/results/fuller/terraform/fedora-… [1] https://src.fedoraproject.org/rpms/golang-github-hashicorp-consul-sdk/blob/… [2] https://src.fedoraproject.org/rpms/golang-github-hashicorp-consul-api/blob/… -- Mark E. Fuller, Ph.D. fuller(a)fedoraproject.org fuller(a)mefuller.dev @fuller:fedora.im @fuller:one.ems.host https://www.stossrohr.net PGP Fingerprint: 73F1 A30C BDF4 DB4B C75F FD0F D599 E76C FFCA BF60

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

golang October 2022