From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Problem updating python3-cryptography Date: Thu, 16 Jun 2022 20:00:33 +0100 Message-ID: <9EA86A0F-964C-431B-BA2B-45F6E5289722@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6608303897953047283==" List-Id: --===============6608303897953047283== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, > On 16 Jun 2022, at 14:43, Adolf Belka wrote: >=20 > Hi Michael, >=20 > On 16/06/2022 12:45, Michael Tremer wrote: >> Hello Adolf, >> I ran into those problems too when I packaged the first bunch of rust pack= ages. >> The problem is, that cargo cannot easily differentiate what dependencies i= t actually needs. Developers of those crates can list certain dependencies fo= r only certain platforms (e.g. Windows), and those will only be built on thos= e platforms then. However, they still need to be all present on all systems -= even though they are not being built. >> Not the best design, but probably okay for everyone who downloads those pa= ckages live using cargo. >> What I have done in those cases is just remove those dependencies manually: >> https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dblob;f=3Dsrc/patches/rust-d= irs-1.0.5-fix-metadata.patch;h=3D0c51222127924cab1d6a85ee099c7bd05667948a;hb= =3DHEAD >> https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dblob;f=3Dsrc/patches/rust-g= etrandom-0.2.4-fix-metadata.patch;h=3D083b6d6c80a5577a349f8dbe34929b48229ca05= d;hb=3DHEAD >> https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dblob;f=3Dsrc/patches/rust-h= ome-0.5.3-fix-metadata.patch;h=3D78e154af69554b3b53ab067d8f1722ef069ddf7d;hb= =3DHEAD >> There are lots more in src/patches. >> And this is the only way to avoid packaging stuff that will never and can = never be used on IPFire. >> Hope this helps. > That indeed helped. I now know how to get rid of them. Have created the pat= ch to exclude winapi which will stop the need for the other winapi files. > The build is running now. >=20 > I think I am now close to being able to release the updated python3-cryptog= raphy. Thanks very much for the help. I have learnt a lot with this. Mainly how unpleasant the Rust eco system is for distributions? >=20 > Regards, >=20 > Adolf. >> -Michael >>> On 15 Jun 2022, at 21:02, Adolf Belka wrote: >>>=20 >>> Hi Michael, >>>=20 >>> I added the rust-indoc and rust-paste packages as explicitly defined vers= ions to deal with the requirement for an older version. After another couple = of changes I have been able to get python3-cryptography to build successfully. >>>=20 >>> However, the build ended up requiring three packages that seem totally re= dundant to me as they are related to windows but I can't figure out how to el= iminate them. Do these have to stay being included or is there a way to stop = them being required. >>>=20 >>> The packages are:- >>>=20 >>> rust-winapi >>> rust-winapi-i686-pc-windows-gnu >>> rust-winapi-x86_64-pc-windows-gnu >>>=20 >>> Regards, >>>=20 >>> Adolf >>>=20 >>>=20 >>> On 03/05/2022 23:02, Adolf Belka wrote: >>>> Hi Michael, >>>>=20 >>>> On 03/05/2022 12:32, Michael Tremer wrote: >>>>> Hello Adolf, >>>>>=20 >>>>> It looks like it is looking for a Rust package called asn1. >>>>>=20 >>>>> You can create this in a very simple way by running: >>>>>=20 >>>>> tools/download-rust-crate asn1 >>>>>=20 >>>>> That will create a new LFS file for this package and automatically down= load any sources. You will only need to add this to make.sh and build it. >>>> That is a very nice script. Worked very well. >>>>>=20 >>>>> You might need some further dependencies later on. >>>> That is an understatement. >>>> I am at the stage where python3-cryptography has required asn1, ouroboro= s 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-downl= oaded as specific versions were required and not the latest version. >>>>=20 >>>> 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-py= o3 flagged up that the requirement was for indoc to be at version 0.3.6 but t= he 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. >>>>=20 >>>> I am not sure what to do now. >>>>=20 >>>> Regards, >>>> Adolf. >>>>=20 >>>>=20 >>>> Building rust-pyo3 log >>>>=20 >>>> 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=3D/usr/src install >>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 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 && e= cho "${CARGO_CONFIG}" > /usr/src/pyo3-0.15.1/.cargo/config && rm -f Cargo.lock >>>> cd /usr/src/pyo3-0.15.1 && CARGOPATH=3D/usr/src/pyo3-0.15.1/.cargo RUSTC= _BOOTSTRAP=3D1 cargo --offline build --release -Z avoid-dev-deps -j6 >>>> error: failed to select a version for the requirement `indoc =3D "^0.3.6= "` >>>> candidate versions found which didn't match: 1.0.3 >>>> location searched: directory source `/usr/share/cargo/registry` (which i= s 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 >>>>=20 >>>>=20 >>>>=20 >>>>>=20 >>>>> -Michael >>>>>=20 >>>>>> On 10 Apr 2022, at 12:32, Adolf Belka wrote: >>>>>>=20 >>>>>> Hi All, >>>>>>=20 >>>>>>=20 >>>>>> I have gone through and updated all python3 modules that I found with = a new version. Everything built fine except for python3-cryptography. >>>>>>=20 >>>>>> I have gone through the log info and it seems to me, but I might be wr= ong, that wants pyasnl1 but it seems to be looking for asnl1. >>>>>>=20 >>>>>> However I have not been able to figure out where it should be changed = to correct this, if my interpretation is even right. >>>>>>=20 >>>>>>=20 >>>>>> I would appreciate any guidance/suggestions of what to look for. >>>>>>=20 >>>>>>=20 >>>>>> Log feedback for the build of cryptography is attached below. >>>>>>=20 >>>>>>=20 >>>>>> Regards, >>>>>>=20 >>>>>> Adolf. >>>>>> <_build.ipfire.log> >>>>>=20 --===============6608303897953047283==--