unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: guix-devel <guix-devel@gnu.org>
Cc: Marius Bakke <marius@gnu.org>
Subject: Re: python-cryptography and rust [was: Re: ‘staging’ branch is open!]
Date: Sun, 15 May 2022 23:22:05 +0200	[thread overview]
Message-ID: <87v8u6bif6.fsf@gnu.org> (raw)
In-Reply-To: <YnphmGn2vf0/oG4X@3900XT> (Efraim Flashner's message of "Tue, 10 May 2022 15:59:04 +0300")

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?

Besides, since mrustc was updated on ‘staging’, does that new version
better support platforms other than x86_64?

Thanks for the heads-up,
Ludo’.


  reply	other threads:[~2022-05-15 21:22 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 [this message]
2022-05-16  7:43     ` Efraim Flashner
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=87v8u6bif6.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@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).