From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Problem updating python3-cryptography
Date: Tue, 03 May 2022 11:32:06 +0100 [thread overview]
Message-ID: <0D7D4D9E-BCA1-445E-AE6C-2E873ADD665E@ipfire.org> (raw)
In-Reply-To: <b322bcb6-ef36-0ab0-1b33-1d2e4b1ec9da@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
Hello Adolf,
It looks like it is looking for a Rust package called asn1.
You can create this in a very simple way by running:
tools/download-rust-crate asn1
That will create a new LFS file for this package and automatically download any sources. You will only need to add this to make.sh and build it.
You might need some further dependencies later on.
-Michael
> On 10 Apr 2022, at 12:32, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi All,
>
>
> I have gone through and updated all python3 modules that I found with a new version. Everything built fine except for python3-cryptography.
>
> I have gone through the log info and it seems to me, but I might be wrong, that wants pyasnl1 but it seems to be looking for asnl1.
>
> However I have not been able to figure out where it should be changed to correct this, if my interpretation is even right.
>
>
> I would appreciate any guidance/suggestions of what to look for.
>
>
> Log feedback for the build of cryptography is attached below.
>
>
> Regards,
>
> Adolf.
> <_build.ipfire.log>
next prev parent reply other threads:[~2022-05-03 10:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 11:32 Adolf Belka
2022-05-03 10:32 ` Michael Tremer [this message]
2022-05-03 21:02 ` Adolf Belka
2022-06-15 20:02 ` Adolf Belka
2022-06-16 10:45 ` Michael Tremer
2022-06-16 13:43 ` Adolf Belka
2022-06-16 19:00 ` Michael Tremer
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=0D7D4D9E-BCA1-445E-AE6C-2E873ADD665E@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox