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: Mon, 14 Dec 2020 16:53:59 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.21.2012131810150.5691@marsh.hcoop.net> (raw)
In-Reply-To: <87r1ntz7wh.fsf@davie.li>
On Mon, 14 Dec 2020, David Dashyan wrote:
>
> 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?
Sure. For me it involved some manual effort. There might be a more clever
way to script it that others can share, but I didn't think it was too bad,
and it allowed me to make notes about what problems I observed as I
encountered them. Nothing I did was Go-specific. Perhaps a small project
for another time, we could add a cookbook recipe for testing upgrades to
languages or other packages with many dependents.
Here's what I did after changing the default go:
* ran `./pre-inst-env guix refresh -l go` and recorded the list of
packages to build.
* ran `./pre-inst-env guix build` with that list.
* After a while there is a build failure, and the end of the log looks
like (the actually failure here is unimportant):
```
FAIL go.etcd.io/bbolt 600.127s
FAIL
command "go" "test" "go.etcd.io/bbolt" failed with status 1
Some deprecated features have been used. Set the environment
variable GUILE_WARN_DEPRECATED to "detailed" and rerun the
program to get more information. Set it to "no" to suppress
this message.
builder for `/gnu/store/6dshsgwryfj8g27sf24sp7lhnpf639d1-go-etcd-io-bbolt-1.3.5.drv' failed with exit code 1
@ build-failed /gnu/store/6dshsgwryfj8g27sf24sp7lhnpf639d1-go-etcd-io-bbolt-1.3.5.drv - 1 builder for `/gnu/store/6dshsgwryfj8g27sf24sp7lhnpf639d1-go-etcd-io-bbolt-1.3.5.drv' failed with exit code 1
derivation '/gnu/store/6dshsgwryfj8g27sf24sp7lhnpf639d1-go-etcd-io-bbolt-1.3.5.drv' offloaded to 'libre-02.local' failed: build of `/gnu/store/6dshsgwryfj8g27sf24sp7lhnpf639d1-go-etcd-io-bbolt-1.3.5.drv' failed
build of /gnu/store/6dshsgwryfj8g27sf24sp7lhnpf639d1-go-etcd-io-bbolt-1.3.5.drv failed
View build log at '/var/log/guix/drvs/6d/shsgwryfj8g27sf24sp7lhnpf639d1-go-etcd-io-bbolt-1.3.5.drv.bz2'.
cannot build derivation `/gnu/store/23jx3gb17gdhz662d3dsrmfnpp92abw4-chezmoi-1.8.1.drv': 1 dependencies couldn't be built
guix build: error: build of `/gnu/store/23jx3gb17gdhz662d3dsrmfnpp92abw4-chezmoi-1.8.1.drv' failed
```
* From this, I make a not the go-etcd-io-bbolt has a build failure, and
that I was unable to attempt chezmoi.
* I remove chezmoi from the list of packages to build and re-run `guix
build`.
Repeat that process until all the remaining packages build, and you should
have a nice list of build failures and builds that could not be attempted.
Hope that helps,
Jack
next prev parent reply other threads:[~2020-12-14 21:55 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
2020-12-14 13:10 ` David Dashyan
2020-12-14 21:53 ` Jack Hill [this message]
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.2012131810150.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.