From: Danny Milosavljevic <dannym@scratchpost.org>
To: Nikolai Merinov <nikolai.merinov@member.fsf.org>
Cc: 30831@debbugs.gnu.org
Subject: [bug#30831] [PATCH] gnu: rust: Update rust from 1.22.1 release to 1.24.1
Date: Sat, 24 Mar 2018 17:26:01 +0100 [thread overview]
Message-ID: <20180324172601.070cb69d@scratchpost.org> (raw)
In-Reply-To: <87a7v12qw9.fsf@member.fsf.org>
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
Hi Nikolai,
On Thu, 22 Mar 2018 00:02:46 +0500
Nikolai Merinov <nikolai.merinov@member.fsf.org> wrote:
> I checked several times with "guix build --no-grafts --rounds=2 rust@1.24.1"
> with "guix gc" between tries, but it worked correctly. I tried on x86-64
> architecture with my patch over 79f450a120068ac1d2fc4e5b4b33ae938b604f95
> guix commit.
Weird, works fine for me with 79f450a120068ac1d2fc4e5b4b33ae938b604f95.
But with the current master, 2cac8891510533338f6214fbd5ab9c2f6204e856, it fails
as describes (I tried again, fails).
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-03-24 17:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 19:06 [bug#30831] [PATCH] gnu: rust: Update rust from 1.22.1 release to 1.24.1 Nikolai Merinov
2018-03-17 21:22 ` Ludovic Courtès
2018-03-19 12:26 ` Nikolai Merinov
2018-03-19 16:23 ` Ludovic Courtès
2018-03-20 10:56 ` Ricardo Wurmus
2018-03-22 21:01 ` Nikolai Merinov
2018-03-27 7:41 ` Ludovic Courtès
2018-03-27 12:56 ` Nikolai Merinov
2018-03-27 13:19 ` Danny Milosavljevic
2018-03-27 18:08 ` Marius Bakke
2018-03-27 19:56 ` Ricardo Wurmus
2018-03-30 23:51 ` Danny Milosavljevic
2018-03-27 13:09 ` Danny Milosavljevic
2018-03-18 18:58 ` Danny Milosavljevic
2018-03-21 19:02 ` Nikolai Merinov
2018-03-24 16:26 ` Danny Milosavljevic [this message]
2018-03-27 13:02 ` Nikolai Merinov
2018-03-30 13:48 ` bug#30831: " Danny Milosavljevic
2018-03-22 7:20 ` [bug#30831] building rust on aarch64 Efraim Flashner
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=20180324172601.070cb69d@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=30831@debbugs.gnu.org \
--cc=nikolai.merinov@member.fsf.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.
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.