From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Problem updating python3-cryptography
Date: Tue, 03 May 2022 23:02:08 +0200 [thread overview]
Message-ID: <681f6cb5-ab2c-8c34-9404-6909584b7798@ipfire.org> (raw)
In-Reply-To: <0D7D4D9E-BCA1-445E-AE6C-2E873ADD665E@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 3220 bytes --]
Hi Michael,
On 03/05/2022 12:32, Michael Tremer wrote:
> 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.
That is a very nice script. Worked very well.
>
> You might need some further dependencies later on.
That is an understatement.
I am at the stage where python3-cryptography has required asn1, ouroboros and pem and each of then has had additional dependencies. so I have reached an additional 20 new rust packages. 5 of those had to be separately re-downloaded as specific versions were required and not the latest version.
Then python3-cryptography indicated that a newer rust-pyo3 was required but not the most up to date version. I added that version in and then rust-pyo3 flagged up that the requirement was for indoc to be at version 0.3.6 but the currently installed version is 1.0.3. That would mean reverting indoc to a much older version than the one already installed and running. The log file for this is below.
I am not sure what to do now.
Regards,
Adolf.
Building rust-pyo3 log
May 3 17:30:37: Building rust-pyo3 pyo3-0.15.1.tar.gz checksum OK
+ cd /usr/src/lfs
+ make -f rust-pyo3 LFS_BASEDIR=/usr/src install
====================================== Installing pyo3-0.15.1 ...
Install started; saving file list to /usr/src/lsalr ...
cd /usr/src/pyo3-0.15.1 && mkdir -p /usr/src/pyo3-0.15.1/.cargo && echo "${CARGO_CONFIG}" > /usr/src/pyo3-0.15.1/.cargo/config && rm -f Cargo.lock
cd /usr/src/pyo3-0.15.1 && CARGOPATH=/usr/src/pyo3-0.15.1/.cargo RUSTC_BOOTSTRAP=1 cargo --offline build --release -Z avoid-dev-deps -j6
error: failed to select a version for the requirement `indoc = "^0.3.6"`
candidate versions found which didn't match: 1.0.3
location searched: directory source `/usr/share/cargo/registry` (which is replacing registry `crates-io`)
required by package `pyo3 v0.15.1 (/usr/src/pyo3-0.15.1)`
perhaps a crate was updated and forgotten to be re-vendored?
As a reminder, you're using offline mode (--offline) which can sometimes cause surprising resolution failures, if this error is too confusing you may wish to retry without the offline flag.
make: *** [rust-pyo3:77: /usr/src/log/pyo3-0.15.1] Error 101
>
> -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 21:02 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
2022-05-03 21:02 ` Adolf Belka [this message]
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=681f6cb5-ab2c-8c34-9404-6909584b7798@ipfire.org \
--to=adolf.belka@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