From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: "kiasoc5" <kiasoc5@disroot.org>, "Tobias Geerinckx-Rice" <me@tobias.gr>
Cc: 54439@debbugs.gnu.org
Subject: [bug#54439] Rust 1.61.0
Date: Fri, 01 Jul 2022 10:39:20 +0100 [thread overview]
Message-ID: <CL47X6F1N7SD.RHVVC7ZD1FN@guix-aspire> (raw)
In-Reply-To: <20220701011109.1a436efa@aria>
On Fri Jul 1, 2022 at 2:11 AM BST, kiasoc5 via Guix-patches via wrote:
> I feel like this is too much of a challenge for me.
I updated Rust to 1.57 when I was new to Guix, it wasn't very hard at
all. The main problem was that the build took aaaaaaages. See commit
89afe76a164c53aef66e6f819137bd0c65089fe8.
-- (
next prev parent reply other threads:[~2022-07-01 9:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 0:21 [bug#54439] Rust: Add Rust 1.59, set default to 1.59 Paul Alesius
2022-03-18 8:23 ` Maxime Devos
2022-03-18 8:55 ` Paul Alesius
2022-03-18 8:25 ` Maxime Devos
2022-03-18 8:25 ` Maxime Devos
2022-03-18 8:26 ` Maxime Devos
2022-03-20 13:58 ` Maxime Devos
2022-03-20 15:36 ` Paul Alesius
2022-03-21 3:31 ` [bug#54439] kiasoc5--- via Guix-patches via
2022-03-26 13:36 ` [bug#54439] Pierre Langlois
2022-04-11 20:04 ` [bug#54439] kiasoc5--- via Guix-patches via
2022-05-20 2:39 ` [bug#54439] Rust 1.61.0 kiasoc5--- via Guix-patches via
2022-06-30 18:57 ` kiasoc5 via Guix-patches via
2022-06-30 20:17 ` Tobias Geerinckx-Rice via Guix-patches via
2022-07-01 1:11 ` kiasoc5 via Guix-patches via
2022-07-01 9:39 ` ( via Guix-patches via [this message]
2022-07-03 4:25 ` kiasoc5 via Guix-patches via
2022-08-04 1:47 ` [bug#54439] [PATCH core-updates] gnu: rust: Use rust-1.60.0 Jim Newsome
2022-08-04 11:03 ` bug#54439: " Marius Bakke
2022-08-04 15:08 ` [bug#54439] " Jim Newsome
2022-08-04 1:47 ` [bug#54439] [PATCH core-updates 1/2] gnu: rust: decouple rust-1.57 and "rust" Jim Newsome
2022-08-04 1:47 ` [bug#54439] [PATCH core-updates 2/2] gnu: rust: Use rust-1.60.0 Jim Newsome
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=CL47X6F1N7SD.RHVVC7ZD1FN@guix-aspire \
--to=guix-patches@gnu.org \
--cc=54439@debbugs.gnu.org \
--cc=kiasoc5@disroot.org \
--cc=me@tobias.gr \
--cc=paren@disroot.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 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).