golang July 2020

golang@lists.fedoraproject.org

4 participants
11 discussions

[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] PR #20: Use --with-tests when running checks also.
by Elliott Sales de Andrade 05 Sep '21

05 Sep '21

qulogic opened a new pull-request against the project: `go-rpm-macros` that you are following: `` Use --with-tests when running checks also. `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/pull-request/20

1 2

[go-rpm-macros] PR #23: macros: Accept options for %gotest
by Alexander Todorov 21 Jun '21

21 Jun '21

atodorov opened a new pull-request against the project: `go-rpm-macros` that you are following: `` macros: Accept options for %gotest `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/pull-request/23

4 7

[go-rpm-macros] Issue #25: Consider using -trimpath
by Debarshi Ray 26 Apr '21

26 Apr '21

rishi reported a new issue against the project: `go-rpm-macros` that you are following: `` See [this](https://github.com/containers/toolbox/pull/448) [Toolbox](https://github.com/containers/toolbox) discussion for context. It might be good to include `-trimpath` in `%gobuild` and `%gobuildflags`. Apparently Arch Linux already uses it. `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/issue/25

4 9

[go-rpm-macros] Issue #19: LDFlags Macro Typos
by Brian Exelbierd (bex) 20 Apr '21

20 Apr '21

bex reported a new issue against the project: `go-rpm-macros` that you are following: `` While working with a new package, I needed some LDFlags passed. I am using this construction in my spec: ``` %build LDFLAGS="-X foo=bar " %gobuild ... ``` I have to put the space in quotes at the end as we appear to have space expansion errors. I was talking to @ignatenkobrain and he pointed out: * https://pagure.io/go-rpm-macros/blob/master/f/rpm/macros.d/macros.go-rpm#_3… there is a missing space * https://pagure.io/go-rpm-macros/blob/master/f/rpm/macros.d/macros.go-compil… ${LDFLAGS:-%{?currentgoldflags}} ← should be like that `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/issue/19

3 4

[go-rpm-macros] PR #21: Expose Go build flags directly to spec files as a macro
by Daniel P. Berrange 21 Oct '20

21 Oct '20

berrange opened a new pull-request against the project: `go-rpm-macros` that you are following: `` Expose Go build flags directly to spec files as a macro `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/pull-request/21

5 10

[go-rpm-macros] PR #24: Fix LDFLAGS macros typos
by Robert-André Mauchin 13 Aug '20

13 Aug '20

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

2 1

[Fedocal] Reminder meeting : Go SIG Meeting
by jcajka＠fedoraproject.org 18 Jul '20

18 Jul '20

Dear all, You are kindly invited to the meeting: Go SIG Meeting on 2020-07-20 from 19:00:00 to 20:00:00 Europe/Prague At fedora-golang(a)irc.freenode.net The meeting will be about: Meeting of Go SIG. For proposed agenda see the tagged tickets https://pagure.io/GoSIG/go-sig/issues?status=Open&tags=meeting Source: https://apps.fedoraproject.org/calendar/meeting/9758/

1 0

Re: Orphaning my golang packages
by Elliott Sales de Andrade 12 Jul '20

12 Jul '20

On Tue, 7 Jul 2020 at 13:05, Fabio Valentini <decathorpe(a)gmail.com> wrote: > > Hi everybody, > > I have to finally admit that I'll never again be able to play catch-up > with the ever-changing sprawling go library dependency tree of > syncthing. > > I have switched to using bundled dependencies for syncthing ~years ago > already, and I do not have the time nor the energy to do the amount of > work that would be necessary to un-bundle everything again. The > following packages are now orphaned: > > - golang-github-calmh-du > - golang-github-calmh-xdr > - golang-github-chmduquesne-rollinghash > - golang-github-d4l3k-messagediff > - golang-github-gobwas-glob This one is used by hugo, and you're already admin, so you probably want to become primary maintainer, Athos. > - golang-github-jackpal-gateway > - golang-github-minio-sha256-simd > - golang-github-petermattis-goid > - golang-github-syncthing-notify > - golang-github-thejerf-suture > - golang-github-vitrun-qart > - golang-gopkg-asn1-ber-1 > - golang-gopkg-ldap-2 These two are used by golang-vitess, Robert-André. > > I think most of them have never been used for anything but building > syncthing, so they have been useless baggage for me for years. Some > are also used by other packages, and I hope that those few can find a > new home. > > The packages should comply with the latest Packaging Guidelines for > Go, should be up-to-date, and are all building successfully, with > passing test suites. > > Thanks. > Fabio -- Elliott

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

golang July 2020