From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>, Marius Bakke <marius@gnu.org>
Subject: Re: python-cryptography and rust [was: Re: ‘staging’ branch is open!]
Date: Mon, 16 May 2022 10:43:29 +0300 [thread overview]
Message-ID: <YoIAoe7u23CvqZuk@3900XT> (raw)
In-Reply-To: <87v8u6bif6.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]
On Sun, May 15, 2022 at 11:22:05PM +0200, Ludovic Courtès wrote:
> Hi Efraim,
>
> (+Cc: Marius.)
>
> Efraim Flashner <efraim@flashner.co.il> skribis:
>
> > python-cryptography now depends on rust. We're going to need 3.4.8 from
> > the 3.4 series for the other architectures. Currently
> > python-cryptography@36.0.1 is gating about 3000 packages.
>
> Yes, so what do you mean? Should we keep the old 3.3.1 for use on
> non-x86_64 platforms? Would that even work?
I'll add 3.4.8 for non-x86_64 platforms and see if I can do something
about the rust inputs for python-cryptography, to shorten the graph a
bit and note which crates are "locked" in their current versions.
> Besides, since mrustc was updated on ‘staging’, does that new version
> better support platforms other than x86_64?
I hear we should be able to do aarch64 with our new version of mrustc
but I haven't tried building it yet on my machines. I'd leave it as a
happy bonus for now and leave aarch64 with the C counterparts for this
round, rather than relying on the rust bootstrap chain, considering how
much RAM it can use.
> Thanks for the heads-up,
> Ludo’.
>
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-05-16 7:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 23:08 ‘staging’ branch is open! Ludovic Courtès
2022-04-30 8:40 ` zimoun
2022-05-07 22:04 ` Ludovic Courtès
2022-05-08 20:14 ` zimoun
2022-05-15 20:55 ` Ludovic Courtès
2022-05-16 21:37 ` zimoun
2022-05-23 15:23 ` Ludovic Courtès
2022-05-31 7:34 ` Christopher Baines
2022-06-01 16:44 ` ‘staging’ to be merged soon: help needed! Ludovic Courtès
2022-05-03 17:54 ` ‘staging’ branch is open! Maxim Cournoyer
2022-05-10 12:59 ` python-cryptography and rust [was: Re: ‘staging’ branch is open!] Efraim Flashner
2022-05-15 21:22 ` Ludovic Courtès
2022-05-16 7:43 ` Efraim Flashner [this message]
2022-05-23 15:25 ` Ludovic Courtès
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=YoIAoe7u23CvqZuk@3900XT \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=marius@gnu.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).