all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jack Hill <jackhill@jackhill.us>
To: David Dashyan <mail@davie.li>
Cc: 45161@debbugs.gnu.org
Subject: [bug#45161] [PATCH 0/1] Update go?
Date: Thu, 10 Dec 2020 12:13:46 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.21.2012101210380.5691@marsh.hcoop.net> (raw)
In-Reply-To: <20201210151024.25316-1-mail@davie.li>

David,

On Thu, 10 Dec 2020, David Dashyan wrote:

> Yesterday I found packages that won't compile with curent guix's
> go-1.14. Apparently 1.15 is the "stable" thing today.

Awesome, thanks for working on this!

> I've updated go package locally but when I try to run './pre-inst-env guix
> build --rounds=3 go' guix just spits out currently installed go-1.14 store
> directories.  Am I right that this is not how it should work?  It supposed to
> find the modified version in source tree, right?

I think this is because the go still points at 1.14, see the following 
definition:

> (define-public go go-1.14)

We should probably update that so 1.15 is the new default version.

> But I've tested it ;) builds and works.

I've started testing it locally. I'll report back if I notice anything.

Best,
Jack




  parent reply	other threads:[~2020-12-10 17:28 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 ` Jack Hill [this message]
2020-12-10 17:37 ` [bug#45161] [PATCH 0/1] Update go? Leo Famulari
2020-12-11  6:15   ` Jack Hill
2020-12-12 22:51     ` Jack Hill
2020-12-13 21:57     ` David Dashyan
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.21.2012101210380.5691@marsh.hcoop.net \
    --to=jackhill@jackhill.us \
    --cc=45161@debbugs.gnu.org \
    --cc=mail@davie.li \
    /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.