On 27 October 2017 at 22:38, James Cowgill <jcowg...@debian.org> wrote:
> Hi, > > On 26/10/17 20:33, John Paul Adrian Glaubitz wrote: > > On 10/26/2017 07:12 PM, peter green wrote: > >> Therefore golang maintainers you have two choices. > >> > >> 1. Accept John's changes so that your package can be built on mips*. > >> 2. File a removal request for the binaries uploaded by John > > > > I assume that gccgo on mips is still broken as this situation hasn't > changed, > > so I would suggest removing the packages again. I can file a bug for that > > since I am the one who is responsible that these packages are there in > the > > first place. > > gccgo was fixed in gcc-7 a few weeks ago and I've filed a bug against > golang-1.9 already. Since golang-defaults already points to golang-1.9 > in unstable, I am guessing that older versions are now irrelevant for mips. > > I suggest: > - Apply the patch in #879764 to golang-1.9. > LGTM. > - Remove the mips binaries from golang-1.8 (or remove 1.8 entirely). > I think we should remove the mips binaries. > - Enable mips in golang-defaults. > +1 > A reply from the golang maintainers would be very helpful in all of this... > Sorry for the lack of response. I have to admit that I've found the whole issue very confusing to follow but I'm very grateful to the people who've put the effort in to make the simple patch attached to #879764 all that is required! Cheers, mwh
