nim reported a new issue against the project: `golist` that you are following:
``
`golist` only implements a single output format, which means this output needs to be reprocessed in shell before being fed to other software, like rpm¹.
This shell reprocessing is brittle and adds noise to Go package build logs.
Mature utilities allow specifying an output format template, which simplifies their integration with other software. This can be done:
* either by defining a custom format string using predefined variables (as [done](http://man7.org/linux/man-pages/man1/time.1.html) by the `time -f`command),
* or by specifying a specific package dep format built-in (as done by the `fcquery --format '%{=pkgkit}'` command, that allowed direct integration [within rpm](https://github.com/rpm-software-management/rpm/blob/ff4b9111aeba01dd02… in [2009](https://bugs.freedesktop.org/show_bug.cgi?id=17107)).
`golist` should implement something similar.
¹ Typically to [add `golang()`](https://pagure.io/go-rpm-macros/blob/master/f/rpm/macros.d/macros.go-rpm#_228) around dependencies, would need more processing if it ever evolves to list version constrains
``
To reply, visit the link below or just reply to this email
https://pagure.io/golist/issue/13
nim reported a new issue against the project: `golist` that you are following:
``
Because the naming of Go projects is a mess many of them (including core Google modules) have started asserting how they should be named.
This results in golist panics.
Because golist is often called by other scripts (for example, rpm dependency scripts) the panic messages are unhelpful, because the recipient of those messages has not called golist directly and does not know what exact golist call resulted in this panic.
golist should handle this case by default and:
1. output useful info to stderr, including what exactly it was doing at the panic time
2. abort with an error code
``
To reply, visit the link below or just reply to this email
https://pagure.io/golist/issue/14
nim reported a new issue against the project: `golist` that you are following:
``
The last stage of rpm packaging is copying a clean final copy of all the files that will be shipped in an arborescence under a `%{buildroot}` prefix.
That is the deployment tree that is operated on to compute the actual requires and provides rpm will generate.
As a consequence of this rpm design we can not change:
* the files operated on are not in their final place but under a root prefix (`%{buildroot}/something` instead of `something`), and
* absolute symbolic links that point within the target deployment tree are left dangling (they point to `something`, when `/something` is still at `%{buildroot}/something`)
Since *golist* is used to compute provides and requires for Go sources, and those sources can include absolute symlinks, and will continue to prefer absolute symlinks over relative symlinks because relative symlinks are quite hard to get right, *golist* needs to learn to work in prefix mode, and learn to walk to `%{buildroot}/something` when encountering a `/something` symlink in the source tree.
``
To reply, visit the link below or just reply to this email
https://pagure.io/golist/issue/12
nim reported a new issue against the project: `golist` that you are following:
``
golist relies on an obsolete release of gopkg.in/urfave/cli.v1 (1.18) and does not work with the current one (1.20)
+ go build -buildmode pie -compiler gc '-tags=rpm_crashtraceback ' -ldflags ' -X github.com/gofed/symbols-extractor/version.commit=aecba475bf76f5269c11367da… -X github.com/gofed/symbols-extractor/version=0 -B 0x53a515e8225a08687fb15659311c31138f10deef -extldflags '\''-Wl,-z,relro '\''' -a -v -x -o _bin/golist github.com/gofed/symbols-extractor/cmd/golist
…
cd /builddir/build/BUILD/symbols-extractor-aecba475bf76f5269c11367da0a190419cd9a133/_build/src/github.com/gofed/symbols-extractor/cmd/golist
/usr/lib/golang/pkg/tool/linux_amd64/compile -o $WORK/b001/_pkg_.a -trimpath $WORK/b001 -shared -p main -complete -installsuffix shared -buildid W7hFQx2bLlwdklLGWaGL/W7hFQx2bLlwdklLGWaGL -goversion go1.10 -D "" -importcfg $WORK/b001/importcfg -pack ./golist.go
# github.com/gofed/symbols-extractor/cmd/golist
cmd/golist/golist.go:25:40: cannot use nil as type string in field value
cmd/golist/golist.go:25:68: cannot use "" (type string) as type bool in field value
cmd/golist/golist.go:25:72: cannot use false (type bool) as type *cli.StringSlice in field value
cmd/golist/golist.go:26:41: cannot use nil as type string in field value
cmd/golist/golist.go:26:74: cannot use "" (type string) as type bool in field value
cmd/golist/golist.go:26:78: cannot use false (type bool) as type *cli.StringSlice in field value
cmd/golist/golist.go:27:42: cannot use nil as type string in field value
cmd/golist/golist.go:27:87: cannot use "" (type string) as type bool in field value
cmd/golist/golist.go:27:91: cannot use false (type bool) as type *cli.StringSlice in field value
cmd/golist/golist.go:28:61: cannot use "" (type string) as type bool in field value
cmd/golist/golist.go:28:61: too many errors
``
To reply, visit the link below or just reply to this email
https://pagure.io/golist/issue/1
qulogic opened a new pull-request against the project: `golist` that you are following:
``
Replace Go internals with go/build
``
To reply, visit the link below or just reply to this email
https://pagure.io/golist/pull-request/17
qulogic opened a new pull-request against the project: `golist` that you are following:
``
Fix compile against latest urfave/cli.
``
To reply, visit the link below or just reply to this email
https://pagure.io/golist/pull-request/16
Hi golang list,
Are there plans to update the golang package in fedora 30 and 31 to
the final 1.12 release soon-ish?
One of my packages had weird issues / crashes on some architectures
(ppc64le and others) with the 1.12 prereleases, and I'd like to know
if the 1.12 final release fixes those issues (it should?).
See:
https://github.com/oschwald/maxminddb-golang/issues/51https://github.com/containerd/containerd/issues/3005https://github.com/golang/go/issues/30283
As mentioned in the other bug reports, it looks like multiple other
fedora packages are affected by this problem, too.
Fabio