From: Leo Famulari <leo@famulari.name>
To: Pier-Hugues Pellerin <ph@heykimo.com>
Cc: 54568-done@debbugs.gnu.org
Subject: bug#54568: Update to Go 1.17.8, Go 1.16.15
Date: Sun, 27 Mar 2022 23:14:40 -0400 [thread overview]
Message-ID: <YkEoIBL4AXNsplmy@jasmine.lan> (raw)
In-Reply-To: <CA+RyfLkzT25r7eV1wkorxmJupeAobaTGCpFfEmGggUoYYzp0uQ@mail.gmail.com>
On Fri, Mar 25, 2022 at 03:19:07PM -0400, Pier-Hugues Pellerin wrote:
> This patch updates Go 1.16 and 1.17 to their latest patch and fixes a
> security issue with the regexp/syntax package. I've looked at the current
> patch and I haven't found one for Go.
>
> This is my first contribution to guix and this process is new to me.
>
> I've made the changes in a single patch, because it covers the same CVE, if
> you prefer I can split them.
Thanks! I went ahead and split them on your behalf, pushing as commit
fff27ded10fec7efaec11a231324681fb8dd0857:
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=fff27ded10fec7efaec11a231324681fb8dd0857
> Also, I've looked to add support for go 1.18 based on the 1.17 package
> definition, at work I've had a few hiccups when upgrading to this new
> version. What would be the way to test that packages depending on go (or
> go-build-system) would still build with it ?
I think that one can use the fold-packages procedure to iterate over
packages and select those that use go-build-system. I don't have an
example off-hand. You can get some help with that on the #guix IRC
channel or the <guix-devel@gnu.org> mailing list.
prev parent reply other threads:[~2022-03-28 3:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 19:19 [bug#54568] Update to Go 1.17.8, Go 1.16.15 Pier-Hugues Pellerin
2022-03-28 3:14 ` Leo Famulari [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YkEoIBL4AXNsplmy@jasmine.lan \
--to=leo@famulari.name \
--cc=54568-done@debbugs.gnu.org \
--cc=ph@heykimo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.