[golist] Issue #1: golist relies on an obsolete release of
gopkg.in/urfave/cli.v1 (1.18) and does not work with the current one (1.20)
by Nicolas Mailhot
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=aecba475bf76f5269c11367... -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
5 years
[golist] Issue #10: unexpected directory layout (whatever that means)
by Nicolas Mailhot
nim reported a new issue against the project: `golist` that you are following:
``
golist fails to output project go files on github.com/rubiojr/go-vhd
```sh
Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.NZHyXq
+ umask 022
+ cd /builddir/build/BUILD
+ '[' /builddir/build/BUILDROOT/golang-github-rubiojr-vhd-0-0.1.4.20180320git0bfd3b3.el7.llt.x86_64 '!=' / ']'
+ rm -rf /builddir/build/BUILDROOT/golang-github-rubiojr-vhd-0-0.1.4.20180320git0bfd3b3.el7.llt.x86_64
++ dirname /builddir/build/BUILDROOT/golang-github-rubiojr-vhd-0-0.1.4.20180320git0bfd3b3.el7.llt.x86_64
+ mkdir -p /builddir/build/BUILDROOT
+ mkdir /builddir/build/BUILDROOT/golang-github-rubiojr-vhd-0-0.1.4.20180320git0bfd3b3.el7.llt.x86_64
+ cd go-vhd-0bfd3b39853cdde5762efda92289f14b0ac0491b
+ go-rpm-integration install -i github.com/rubiojr/go-vhd -s /builddir/build/BUILD/go-vhd-0bfd3b39853cdde5762efda92289f14b0ac0491b -b /builddir/build/BUILD/go-vhd-0bfd3b39853cdde5762efda92289f14b0ac0491b/_build -o devel.file-list -p /builddir/build/BUILDROOT/golang-github-rubiojr-vhd-0-0.1.4.20180320git0bfd3b3.el7.llt.x86_64 -g /usr/share/gocode -r '.*example.*'
install: creating directory '/builddir/build/BUILDROOT/golang-github-rubiojr-vhd-0-0.1.4.20180320git0bfd3b3.el7.llt.x86_64/usr'
install: creating directory '/builddir/build/BUILDROOT/golang-github-rubiojr-vhd-0-0.1.4.20180320git0bfd3b3.el7.llt.x86_64/usr/share'
install: creating directory '/builddir/build/BUILDROOT/golang-github-rubiojr-vhd-0-0.1.4.20180320git0bfd3b3.el7.llt.x86_64/usr/share/gocode'
install: creating directory '/builddir/build/BUILDROOT/golang-github-rubiojr-vhd-0-0.1.4.20180320git0bfd3b3.el7.llt.x86_64/usr/share/gocode/src'
Installing: github.com/rubiojr/go-vhd
install: creating directory '/builddir/build/BUILD/go-vhd-0bfd3b39853cdde5762efda92289f14b0ac0491b/_build'
install: creating directory '/builddir/build/BUILD/go-vhd-0bfd3b39853cdde5762efda92289f14b0ac0491b/_build/src'
install: creating directory '/builddir/build/BUILD/go-vhd-0bfd3b39853cdde5762efda92289f14b0ac0491b/_build/src/github.com'
install: creating directory '/builddir/build/BUILD/go-vhd-0bfd3b39853cdde5762efda92289f14b0ac0491b/_build/src/github.com/rubiojr'
2018/03/23 16:49:12 unexpected directory layout:
import path: _/builddir/build/BUILD/go-vhd-0bfd3b39853cdde5762efda92289f14b0ac0491b/_b...
root: /builddir/build/BUILD/go-vhd-0bfd3b39853cdde5762efda92289f14b0ac0491b/_build/src
dir: /builddir/build/BUILD/go-vhd-0bfd3b39853cdde5762efda92289f14b0ac0491b/_build/src/github.com/rubiojr/go-vhd/vhd
expand root: /builddir/build/BUILD/go-vhd-0bfd3b39853cdde5762efda92289f14b0ac0491b/_build/src
expand dir: /builddir/build/BUILD/go-vhd-0bfd3b39853cdde5762efda92289f14b0ac0491b/vhd
separator: /
install: creating directory '/builddir/build/BUILDROOT/golang-github-rubiojr-vhd-0-0.1.4.20180320git0bfd3b3.el7.llt.x86_64/usr/share/gocode/src/github.com'
install: creating directory '/builddir/build/BUILDROOT/golang-github-rubiojr-vhd-0-0.1.4.20180320git0bfd3b3.el7.llt.x86_64/usr/share/gocode/src/github.com/rubiojr'
install: creating directory '/builddir/build/BUILDROOT/golang-github-rubiojr-vhd-0-0.1.4.20180320git0bfd3b3.el7.llt.x86_64/usr/share/gocode/src/github.com/rubiojr/go-vhd'
'/builddir/build/BUILD/go-vhd-0bfd3b39853cdde5762efda92289f14b0ac0491b/notes.md' -> '/builddir/build/BUILDROOT/golang-github-rubiojr-vhd-0-0.1.4.20180320git0bfd3b3.el7.llt.x86_64/usr/share/gocode/src/github.com/rubiojr/go-vhd/notes.md'
'/builddir/build/BUILD/go-vhd-0bfd3b39853cdde5762efda92289f14b0ac0491b/README.md' -> '/builddir/build/BUILDROOT/golang-github-rubiojr-vhd-0-0.1.4.20180320git0bfd3b3.el7.llt.x86_64/usr/share/gocode/src/github.com/rubiojr/go-vhd/README.md'
'/builddir/build/BUILD/go-vhd-0bfd3b39853cdde5762efda92289f14b0ac0491b/.goipath' -> '/builddir/build/BUILDROOT/golang-github-rubiojr-vhd-0-0.1.4.20180320git0bfd3b3.el7.llt.x86_64/usr/share/gocode/src/github.com/rubiojr/go-vhd/.goipath'
'/builddir/build/BUILD/go-vhd-0bfd3b39853cdde5762efda92289f14b0ac0491b/.goflags' -> '/builddir/build
```
After much investigation in https://github.com/gofed/symbols-extractor/issues/147
it seems triggered by the `./vhd` in
```go
package main
import (
"./vhd"
"fmt"
...
)
```
https://github.com/rubiojr/go-vhd/blob/master/cli.go#L4
``
To reply, visit the link below or just reply to this email
https://pagure.io/golist/issue/10
5 years, 2 months
Skipping the 26th Dec Go -SIG meeting
by Jakub Cajka
Hello,
I propose to skip the next meeting as I will be unavailable to chair that meeting. 26th is a public holiday in CZ and I will be 100% offline on that day.
JC
5 years, 4 months
[golist] Issue #11: golist should permit identifying Go packages that import
a specific import path
by Nicolas Mailhot
nim reported a new issue against the project: `golist` that you are following:
``
This is a continuation and modernization of https://github.com/gofed/go-macros/issues/35
When bootstrapping a set of Go projects, with circular dependencies, you need to identify quickly the parts that participate in the loop, so they can be culled in the initial bootstrap package
For example if `docker-x` depends directly or indirectly on `docker-y`, and `docker-y` imports `docker-x` in its own code (or tests), you want to identify the `docker-x` parts that use `docker-y` and remove them in `%prep`. And then, once the result is built, and permits an initial built of `docker-y`, you can use the resulting `docker-y` to build `docker-x` without removing anything
This could be done by adding a `-x` `--exclude-import-path` switch to golist.
The switch can occur several times, to specify several exclusions in one pass, as some codebases participate in several loops at once
``
To reply, visit the link below or just reply to this email
https://pagure.io/golist/issue/11
5 years, 4 months
[golist] Issue #5: [RFE] list buildable commands in a Go project
by Nicolas Mailhot
nim reported a new issue against the project: `golist` that you are following:
``
It would be awfully nice if `golist` had a mode that outputed, for every path that can be built as a binary:
* the buildable path
* a separator that can not occur in paths
* the expected command output name (via heuristics if necessary)
The result could then be fed to `%gobuild` by [go-rpm-macros](https://pagure.io/go-rpm-macros/)
``
To reply, visit the link below or just reply to this email
https://pagure.io/golist/issue/5
5 years, 4 months