On Sat, Jul 24, 2021 at 07:17:28PM -0700, Sarah Morgensen wrote: > Hi Efraim, > > Just following up on this. Sorry for taking so long to get back to you. > Efraim Flashner writes: > > > On Thu, Jun 24, 2021 at 11:52:55PM -0700, Sarah Morgensen via Guix-patches via wrote: > >> Hello Guix, > >> > >> This patch adds go 1.16, but does *not* make it the default for other packages > >> which use go (as suggested in [2]). There have been a lot of changes between > >> 1.14 and 1.16, and while I have fixed many issues, I am sure continued testing > >> will uncover many more. > >> > >> This patch is based on [0], which adds gccgo-10. > > > > I've applied the patch, so it should now be available in the main repo :) > > Should the following related issues be closed now? > > [0] Build go with gccgo > [1] gnu: gccgo: Add version 10. > [2] Added Go 1.16.2 > [3] Update go? Looks like they should be safe to close. > > My only concern about the patches is that I've been burned before about > > pushing updates to go packages, where some seem to have insufficient > > testing and then they'll build and fail. So in the meantime I've pushed > > the go@1.16 patch. > > Is there something specific to be done to sufficiently test them? I'm > not sure what else to do other than manually testing dependents. I thought more about it and I went ahead and applied most of them. I wasn't able to apply the go-github-com-bmatcuk-doublestar one or the restic patch. Can you resend those? > Thanks, > Sarah Thank you for doing all the work. -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted