From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: go: update to 1.13.1.
Date: Sat, 28 Sep 2019 00:52:54 +0200 [thread overview]
Message-ID: <20190927225254.8V-1w1I-gTgHZU8stWl4etSlcweUEdnxQMVrgWsRAFM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14212@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 422 bytes --]
New comment by nilium on void-packages repository
https://github.com/void-linux/void-packages/pull/14212#issuecomment-536120211
Comment:
The PR has been updated with the patch for the i686 issue. This fails to build in Travis but succeeds both on i686 hardware and in a 32-bit VirtualBox VM (ran stdlib tests on the latter to check behavior), so I'm attributing the failure to Travis resource limits for the time being.
next prev parent reply other threads:[~2019-09-27 22:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 18:18 [PR PATCH] go: update to 1.13 voidlinux-github
2019-09-04 18:32 ` voidlinux-github
2019-09-08 17:04 ` voidlinux-github
2019-09-08 18:32 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-08 18:32 ` voidlinux-github
2019-09-08 19:15 ` voidlinux-github
2019-09-08 19:15 ` voidlinux-github
2019-09-08 19:27 ` voidlinux-github
2019-09-08 19:27 ` voidlinux-github
2019-09-15 4:36 ` voidlinux-github
2019-09-20 12:05 ` voidlinux-github
2019-09-24 18:51 ` voidlinux-github
2019-09-24 19:09 ` voidlinux-github
2019-09-26 18:13 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-26 18:13 ` voidlinux-github
2019-09-26 18:13 ` go: update to 1.13.1 voidlinux-github
2019-09-26 18:16 ` voidlinux-github
2019-09-27 22:15 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-27 22:15 ` voidlinux-github
2019-09-27 22:52 ` voidlinux-github [this message]
2019-09-28 2:41 ` [PR PATCH] [Closed]: " voidlinux-github
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=20190927225254.8V-1w1I-gTgHZU8stWl4etSlcweUEdnxQMVrgWsRAFM@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).