<div dir="ltr">Actually, thinking about it, the CI results will not be representative in this case, as they use golang-go on amd64 only.<div><br></div><div>If you wanted to do a somewhat quick test of the entire archive on a specific architecture, you could replicate the setup described at <a href="https://pkg-go.alioth.debian.org/ci.html">https://pkg-go.alioth.debian.org/ci.html</a> (tl;dr: create a gopath using pgt-gopath, run ci-build). I don’t have sufficient access to non-amd64 machines to do it myself.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 28, 2018 at 8:24 AM, Michael Stapelberg <span dir="ltr"><<a href="mailto:stapelberg@debian.org" target="_blank">stapelberg@debian.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">As mentioned on IRC:<div><br></div><div><div>08:18 @sECuRE> cbmuser: yeah, replacing golang-go with golang-any should do the trick</div><div>08:19 @sECuRE> cbmuser: in fact, after the migration of our repos to salsa (a matter of a small number of weeks at this point), i </div><div> think we can trivially update all repos, wait for the CI results to trickle in, and upload the updated packages</div></div><div><br></div><div>Do note that making packages available on more architectures exposes more portability issues, so increases our workload.</div><div><br></div><div>It would be a nice gesture if you (or someone?) could volunteer to field and fix these portability issues as they arise, at least for the transition period, to help smooth out the increased workload.</div></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Wed, Feb 28, 2018 at 1:24 AM, John Paul Adrian Glaubitz <span dir="ltr"><<a href="mailto:glaubitz@physik.fu-berlin.de" target="_blank">glaubitz@physik.fu-berlin.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear Debian Go Packaging Team!<br>
<br>
Some time ago, I had a discussion with Ian Lance Taylor from Go upstream<br>
regarding the state of gccgo as compared to golang-go.<br>
<br>
According to Ian, gccgo should be able to build any package without problems<br>
that builds with golang-go. Any package that does not build fine with gccgo<br>
is considered to be a bug in gccgo and should be reported upstream.<br>
<br>
To test the validity of this statement, I picked a number of packages from<br>
your package list which have "golang-go" in their Build-Depends and replaced<br>
"golang-go" with "golang-any" and tried to test build the packages on a<br>
powerpc porterbox - an architecture which doesn't have a golang-go port.<br>
<br>
The following packages were tested:<br>
<br>
* golang-glide<br>
* gocode<br>
* codesearch<br>
* golang-petname<br>
* gopass<br>
* golang-golang-x-exp<br>
* snapd<br>
<br>
Out of these 7 packages, 5 packages built fine. Both golang-golang-x-exp<br>
and snapd didn't built because they had additional build dependencies which<br>
could not be fulfilled.<br>
<br>
However, I think this quick test shows that chances are pretty high that<br>
a large number of golang-go-any packages will build fine with gccgo on<br>
architectures like powerpc and sparc64.<br>
<br>
Thus, I would like to ask to replace "golang-go" in the Build-Depends for<br>
all Go packages which are maintained by the Debian Go Packaging Team.<br>
<br>
Would that be possible? Would be awesome to raise the number of available<br>
packages on Debian Ports architectures :-).<br>
<br>
Thanks,<br>
Adrian<br>
<span class="m_2352862157796282119HOEnZb"><font color="#888888"><br>
--<br>
.''`. John Paul Adrian Glaubitz<br>
: :' : Debian Developer - <a href="mailto:glaubitz@debian.org" target="_blank">glaubitz@debian.org</a><br>
`. `' Freie Universitaet Berlin - <a href="mailto:glaubitz@physik.fu-berlin.de" target="_blank">glaubitz@physik.fu-berlin.de</a><br>
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913<br>
<br>
______________________________<wbr>_________________<br>
Pkg-go-maintainers mailing list<br>
<a href="mailto:Pkg-go-maintainers@lists.alioth.debian.org" target="_blank">Pkg-go-maintainers@lists.aliot<wbr>h.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers" rel="noreferrer" target="_blank">http://lists.alioth.debian.org<wbr>/cgi-bin/mailman/listinfo/pkg-<wbr>go-maintainers</a><br>
</font></span></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><div class="m_2352862157796282119gmail_signature" data-smartmail="gmail_signature">Best regards,<br>Michael</div>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Best regards,<br>Michael</div>
</div>