Go plugin creating invalid env #161

Merged
merged 1 commit into from Dec 11, 2015

Conversation

Projects
None yet
4 participants
Contributor

jocave commented Dec 9, 2015

Member

elopio commented Dec 9, 2015

This makes sense to me, but I would feel safer with a regression test. Have you been able to reduce the issue to a minimum scenario?

Contributor

cwayne18 commented Dec 11, 2015

@elopio We haven't been able to reduce it to a minimum scenario quite yet (so far we're only seeing it with building our snap that we'd rather share in public repos yet). Will this block us from landing this? It'd be great to not need a fork of snapcraft to build our snap :)

Member

elopio commented Dec 11, 2015

If this is urgent for you, sure, we can land it. But if it can wait, I would prefer to fully understand the issue before making a fix, by writing a regression test.
Can you share the snapcraft with me?

Member

elopio commented Dec 11, 2015

Merging. Now I see this is a clear fix for the issue and the test updated ensures the space is in there.
I'll ask Sergio next week why we are sharing a single env. The error happens when wrapping the python3 executable, and CGO_LDFLAGS are not needed in there. I'll keep digging.
Thanks for the report, and thanks for the fix!

elopio added a commit that referenced this pull request Dec 11, 2015

@elopio elopio merged commit 74c81b7 into snapcore:master Dec 11, 2015

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
coverage/coveralls Coverage remained the same at 95.771%
Details
Member

kyrofa commented Jan 20, 2016

This needs to be backported to 1.x.

@jocave jocave deleted the jocave:go-ldflags-env-fix branch Mar 2, 2016

kalikiana pushed a commit to kalikiana/snapcraft that referenced this pull request Apr 6, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment