Mailinglist Archive: opensuse-packaging (129 mails)

< Previous Next >
[opensuse-packaging] Re: golang: file paths in go-spew
I've found, package stretchr-testify doesn't require spew (but It did):

rpm -q --requires -p
golang-github-stretchr-testify-0.0.0+git20151207.e3a8ff8-1.2.x86_64.rpm
предупреждение:
golang-github-stretchr-testify-0.0.0+git20151207.e3a8ff8-1.2.x86_64.rpm:
Заголовок V3 DSA/SHA1 Signature, key ID 307d7bf9: NOKEY
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(PayloadIsLzma) <= 4.4.6-1

At the same time

/usr/lib64/go/contrib/pkg/linux_amd64/github.com/stretchr/testify/assert.a

imports go-spew (just look inside)


2016-01-21 16:13 GMT+03:00 Marguerite Su <i@xxxxxxxxxxxxx>:
Hi, Matwey,

On Thu, Jan 21, 2016 at 8:36 PM, Matwey V. Kornilov
<matwey.kornilov@xxxxxxxxx> wrote:
For some unknown reason, golang linker looks for the spew.a in the
wrong place (note there is no contrib in path).
What is wrong here?

Glad to see you here in the list.

this is because:

the test needs spew.a present in the build machine.

but you just wrote:

BuildRequires: golang-packaging
BuildRequires: golang(github.com/stretchr/testify/assert)

the command triggerd by %gotest is:

GOPATH=/home/abuild/BUILD/go:/usr/lib64/go/contrib go test -x $IMPORTPATH

while spew.a doesn't exist in that path (although that path is
invisible to you beccause the call triggers from ruby), go will
fallback to its standard path, resulting what you see.

Marguerite



--
With best regards,
Matwey V. Kornilov
http://blog.matwey.name
xmpp://0x2207@xxxxxxxxx
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups