From: Maxime Devos <maximedevos@telenet.be>
To: kiasoc5@tutanota.com, 53461@debbugs.gnu.org
Subject: [bug#53461] [kiasoc5@tutanota.com: Rust CVE]
Date: Sat, 26 Feb 2022 11:35:42 +0100 [thread overview]
Message-ID: <1174c7a10cf26efa69c9e2ee31d8f115cf65e851.camel@telenet.be> (raw)
In-Reply-To: <MwocHBM--3-2@tutanota.com>
[-- Attachment #1: Type: text/plain, Size: 656 bytes --]
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.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-02-26 10:36 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 [this message]
2022-02-27 6:50 ` kiasoc5--- via Guix-patches via
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=1174c7a10cf26efa69c9e2ee31d8f115cf65e851.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=53461@debbugs.gnu.org \
--cc=kiasoc5@tutanota.com \
/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.