unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: kiasoc5--- via Guix-patches via <guix-patches@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>, 53461 <53461@debbugs.gnu.org>
Subject: [bug#53461] [kiasoc5@tutanota.com: Rust CVE]
Date: Sun, 27 Feb 2022 07:50:40 +0100 (CET)	[thread overview]
Message-ID: <MwtwWAK--3-2@tutanota.com> (raw)
In-Reply-To: <1174c7a10cf26efa69c9e2ee31d8f115cf65e851.camel@telenet.be>

mrustc v0.10 was just released, and can bootstrap Rust 1.54. It would help to update mrustc first, then we can try to bootstrap 1.59 from 1.54 and hopefully save some compile time :)


Feb 26, 2022, 10:35 by maximedevos@telenet.be:

> kiasoc5--- via Guix-patches via schreef op za 26-02-2022 om 07:07
> [+0100]:
>
>> +(define rust-1.59
>> +  (rust-bootstrapped-package
>> +   rust-1.58 "1.59.0"
>> "1yc5bwcbmbwyvpfq7zvra78l0r8y3lbv60kbr62fzz2vx2pfxj57"))
>>
>
> Is building rust@1.59 with rust@1.58 necessary?  Can it be built
> with an earlier rust instead?  I.e., would
>
> (define rust-1.59 (rust-bootstrapped-package rust-1.57 "1.59.0" [...]))
>
> or even
>
> (define rust-1.59 
>  (package
>  (inherit rust-1.56)
>  (source
>  (origin
>  (inherit (package-source rust-1.56))
>  (uri (rust-uri version))
>  (sha256 (base32 [...]))))))
>
> work?
>
> Greetings,
> Maxime.
>





      reply	other threads:[~2022-02-27  6:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-23  0:29 [bug#53461] [kiasoc5@tutanota.com: Rust CVE] Leo Famulari
2022-01-23  3:33 ` Maxim Cournoyer
2022-01-23 19:28   ` Leo Famulari
2022-01-24 21:31     ` Maxim Cournoyer
2022-01-25  4:30       ` Leo Famulari
2022-01-25 23:06         ` Maxim Cournoyer
2022-01-26  2:57           ` Leo Famulari
2022-01-27 21:59             ` Maxim Cournoyer
2022-02-26  6:07 ` kiasoc5--- via Guix-patches via
2022-02-26 10:35   ` Maxime Devos
2022-02-27  6:50     ` kiasoc5--- via Guix-patches via [this message]

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=MwtwWAK--3-2@tutanota.com \
    --to=guix-patches@gnu.org \
    --cc=53461@debbugs.gnu.org \
    --cc=kiasoc5@tutanota.com \
    --cc=maximedevos@telenet.be \
    /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).