From: David Dashyan <mail@davie.li>
To: Jack Hill <jackhill@jackhill.us>
Cc: 45161@debbugs.gnu.org
Subject: [bug#45161] [PATCH 0/1] Update go?
Date: Mon, 14 Dec 2020 00:57:18 +0300 [thread overview]
Message-ID: <87r1ntz7wh.fsf@davie.li> (raw)
In-Reply-To: <alpine.DEB.2.21.2012110045490.5691@marsh.hcoop.net>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
Hello again!
Jack Hill writes:
> I've tested go 1.15 by trying to build the packages reported by `guix refresh -l
> go` on x86_64. There are some new build failures, but it doesn't look too
> bad. In fact, I've already fixed on of them, by updating go-github-com-kr-pretty
> in #45171 [0]. There were a number of packages whose tests failed because of
> changes [1] to `go vet`. The new kr-pretty release adjusts to the new vet
> behavior with a one line change [2] (kr-pretty had fortunately not fallen into
> the incorrect string() usage for which vet is now warning).
May I ask how do you do afterer redefining "go" to point to go-1.15 and
getting list of deppending packages? I mean how one buids all depended
packages in one move if there such a way to do this?
--
David aka zzappie
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-12-13 22:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 15:10 [bug#45161] [PATCH 0/1] Update go? David Dashyan
2020-12-10 15:17 ` [bug#45161] [PATCH 1/1] gnu: Update go David Dashyan
2020-12-10 17:43 ` Leo Famulari
2020-12-13 21:31 ` David Dashyan
2020-12-10 17:13 ` [bug#45161] [PATCH 0/1] Update go? Jack Hill
2020-12-10 17:37 ` Leo Famulari
2020-12-11 6:15 ` Jack Hill
2020-12-12 22:51 ` Jack Hill
2020-12-13 21:57 ` David Dashyan [this message]
2020-12-14 13:10 ` David Dashyan
2020-12-14 21:53 ` Jack Hill
2020-12-13 21:34 ` [bug#45161] [PATCH] gnu: Add go-1.15 David Dashyan
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1ntz7wh.fsf@davie.li \
--to=mail@davie.li \
--cc=45161@debbugs.gnu.org \
--cc=jackhill@jackhill.us \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).