Bug#844258: golang-go: go SIGILL on s390x

[Andreas Henriksson]

Package: golang-go
Version: 2:1.7~1
Severity: serious

Dear Maintainer,

Filing this as promised and as previously discussed in #835360 [0]. It
seems we're having problem building go packages on s390x when they end
up on a certain buildd[1]. AIUI the issue boilds down to upstream go
community doesn't define their support for s390 as we define the s390x
port in Debian. ie. they consider certain older s390 hardware
unsupported which is still part of the defined hardware set of debian
s390x. See for example [2].

I'd suggest simply removing s390x binaries and all reverse dependencies
of golang on s390x. Also go package maintainers should limit their
Architecture: field to only include archs that is actually supportable
rather than using eg. 'all' like golang-github-shirou-gopsutil does
despite including parsing code which only covers linux/x86* (and other
archs we don't have in Debian).

Please note that I'm not really interested in being part of any
discussion around this bug, so please feel free to leave me
out of it! Thanks!

Regards,
Andreas Henriksson

[0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835360#87
[1]: https://buildd.debian.org/status/fetch.php?pkg=golang-github-appc-spec&arch=s390x&ver=0.8.7%2Bdfsg-1&stamp=1476313145
[2]: https://github.com/golang/go/issues/16637

[Michael Hudson-Doyle]

Post by Andreas Henriksson
Filing this as promised and as previously discussed in #835360 [0]. It
seems we're having problem building go packages on s390x when they end
up on a certain buildd[1]. AIUI the issue boilds down to upstream go
community doesn't define their support for s390 as we define the s390x
port in Debian. ie. they consider certain older s390 hardware
unsupported which is still part of the defined hardware set of debian
s390x. See for example [2].
I'd suggest simply removing s390x binaries and all reverse dependencies
of golang on s390x. Also go package maintainers should limit their
Architecture: field to only include archs that is actually supportable
rather than using eg. 'all' like golang-github-shirou-gopsutil does
despite including parsing code which only covers linux/x86* (and other
archs we don't have in Debian).
Please note that I'm not really interested in being part of any
discussion around this bug, so please feel free to leave me
out of it! Thanks!

FWIW, we have now two of three builders and the porter box supporting
the s390x CPU feature set that Go requires.
I suppose the other way out could be that we decom zemlinsky (which
won't have a replacement). I know that Aurelien already had some patches
to Go, but not a complete set.

Have they talked to the IBM folks about this? I remember some comments
along the lines of "porting to z10 would be feasible but we don't have any
real reason to do it". If the Debian issue was raised with them, they might
be willing to help.

Nothing will happen in time for stretch, of course.

Cheers,
mwh