Bug#835360: rkt: FTBFS on several architectures

[Potter, Tim (HPE Linux Support)]

On 29 Aug 2016, at 8:59 PM, Luca BRUNO  wrote:
> 
> 1.13.0+dfsg-1 has been built without issues on i386:
> https://buildd.debian.org/status/fetch.php?pkg=rkt=i386=1.13.0%2Bdfsg-1=1472188080
> 
> ppc64 and s390x are in progress upstream and should hopefully
> be back in the next releases.
> 
> Ciao, Luca

PPC support looks like it has been added in rkt 1.14 and above [1].  According 
to the
release notes on golang.org, experimental support has been added for s390 
systems
in Go 1.7.  We're currently up to Go 1.7 in unstable so we could have rkt 
building on
all architectures pretty soon.


Tim.

[1] https://github.com/coreos/rkt/blob/v1.14.0/configure.ac#L49
[2] https://golang.org/doc/go1.7


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#835698: [pkg-go] Bug#835698: golang-x-text: FTBFS: dh_auto_test: go test -v -p 1 golang.org/x/text golang.org/x/text/cases golang.org/x/text/collate golang.org/x/text/collate/build golang.org/x/te

[Potter, Tim (HPE Linux Support)]

This was fixed by a recent upload of version 0.0~git20160816.0.d69c40b-1 but 
this bug
wasn't closed in d/changelog.


Tim.

On 28 Aug 2016, at 8:24 PM, Lucas Nussbaum  wrote:
> 
> Source: golang-x-text
> Version: 0.0~git20160606.0.a4d77b4-1
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20160828 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.

[...]



signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#830729: [pkg-go] Bug#830729: Bug#830729: Bug#830729: golang-github-mitchellh-go-homedir: FTBFS: homedir_test.go:44: "/home/lamby" != "~"

[Potter, Tim (HPE Linux Support)]

On 2 Aug 2016, at 4:22 AM, Tianon Gravi <tia...@debian.org> wrote:
> 
> On 31 July 2016 at 20:20, Potter, Tim (HPE Linux Support)
> <timothy.pot...@hpe.com> wrote:
>> Patch attached to fix this, but it's a bit icky (and has been replaced by a 
>> shell out to call
>> getent in a later version.
> 
> Very nice catch indeed!
> 
> Given that the code in question is rewritten in newer commits, do you
> think it'd be worthwhile to instead just bump our snapshot?  (since
> the newer code no longer relies on $USER)

Sure thing.  I just did the upload now.


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#830729: [pkg-go] Bug#830729: Bug#830729: golang-github-mitchellh-go-homedir: FTBFS: homedir_test.go:44: "/home/lamby" != "~"

[Potter, Tim (HPE Linux Support)]

On 20 Jul 2016, at 6:35 PM, Chris Lamb  wrote:
> 
>> My _hunch_ is that whatever you're using to build (pbuilder perhaps?)
>> is running as your user ("lamby") but not including "/etc/passwd" from
>> your host
> 
> It is running as my user and /etc/passwd includes:
> 
>  lamby:x:1000:1000:,,,:/home/lamby:/bin/bash
> 
> .. so, alas, that's not the problem.
> 
> (am using Docker, not pbuilder)

I've tracked this down to lack of a $USER environment variable, either in a 
Docker container, or
by some other means.

> cmd := exec.Command("sh", "-c", "eval echo ~$USER")

Patch attached to fix this, but it's a bit icky (and has been replaced by a 
shell out to call
getent in a later version.


Tim.


830729-golang-github-mitchellh-go-homedir.patch
Description: Binary data


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#830519: [pkg-go] Bug#830519: docker-swarm: FTBFS: docker/swarm/api/flusher.go:8:2: cannot find package "github.com/docker/docker/pkg/ioutils"

[Potter, Tim (HPE Linux Support)]

Rebuilds cleanly now so closing this bug.


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#820249: [pkg-go] Bug#820249: Please switch from softhsm to softhsm2

[Potter, Tim (HPE Linux Support)]

I've just pushed a patch for this to the package repository on alioth.


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#820149: [#820149] Fixed by uploading newer upstream version

[Potter, Tim (HPE Linux Support)]

This FTBFS should be fixed by the upload of the newer version in #812838.


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#819638: [pkg-go] Bug#819638: golang-github-armon-gomdb: FTBFS: panic: runtime error: cgo argument has Go pointer to Go pointer

[Potter, Tim (HPE Linux Support)]

On 6 Apr 2016, at 4:07 PM, Potter, Tim (HPE Linux Support) 
<timothy.pot...@hpe.com> wrote:
> 
> On 31 Mar 2016, at 11:14 PM, Chris Lamb <la...@debian.org> wrote:
> 
> [...]
> 
>>dh_auto_test -O--buildsystem=golang
>>  go test -v github.com/armon/gomdb
>> === RUN   TestEnvOpen
>> --- PASS: TestEnvOpen (0.00s)
>> === RUN   TestEnvCopy
>> --- PASS: TestEnvCopy (0.00s)
>>  env_test.go:67: Env path: /tmp/mdb_test840057194
>> === RUN   TestTest1
>> --- FAIL: TestTest1 (0.00s)
>> panic: runtime error: cgo argument has Go pointer to Go pointer [recovered]
>>  panic: runtime error: cgo argument has Go pointer to Go pointer
> 
> This appears to be something to do with how cgo rewrites calls to C functions 
> in Go 1.6:
> 
> https://github.com/golang/go/issues/14210

See also the comments here:

https://github.com/hashicorp/consul-migrate/issues/1


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#819638: [pkg-go] Bug#819638: golang-github-armon-gomdb: FTBFS: panic: runtime error: cgo argument has Go pointer to Go pointer

[Potter, Tim (HPE Linux Support)]

On 31 Mar 2016, at 11:14 PM, Chris Lamb  wrote:

[...]

> dh_auto_test -O--buildsystem=golang
>   go test -v github.com/armon/gomdb
>  === RUN   TestEnvOpen
>  --- PASS: TestEnvOpen (0.00s)
>  === RUN   TestEnvCopy
>  --- PASS: TestEnvCopy (0.00s)
>   env_test.go:67: Env path: /tmp/mdb_test840057194
>  === RUN   TestTest1
>  --- FAIL: TestTest1 (0.00s)
>  panic: runtime error: cgo argument has Go pointer to Go pointer [recovered]
>   panic: runtime error: cgo argument has Go pointer to Go pointer

This appears to be something to do with how cgo rewrites calls to C functions 
in Go 1.6:

https://github.com/golang/go/issues/14210

I don't fully understand it yet but hopefully I can figure out a fix shortly.

A bigger problem is that now this package could only be runnable under one of 
Go 1.5
or Go 1.6.


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail