Problem updating python3-cryptography

Problem updating python3-cryptography

[Adolf Belka]

[-- Attachment #1: Type: text/plain, Size: 576 bytes --]

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.

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: _build.ipfire.log --]
[-- Type: text/x-log, Size: 17578 bytes --]


Apr  9 14:30:16: Building python3-cryptography cryptography-36.0.2.tar.gz checksum OK
+ cd /usr/src/lfs
+ make -f python3-cryptography LFS_BASEDIR=/usr/src install
====================================== Installing cryptography-36.0.2 ...
Install started; saving file list to /usr/src/lsalr ...
cd /usr/src/cryptography-36.0.2 && 	mkdir -p /usr/src/cryptography-36.0.2/.cargo && echo "${CARGO_CONFIG}" > /usr/src/cryptography-36.0.2/.cargo/config && rm -f Cargo.lock
cd /usr/src/cryptography-36.0.2 && rm -vf src/rust/Cargo.lock
removed 'src/rust/Cargo.lock'
cd /usr/src/cryptography-36.0.2 && python3 setup.py build
running build
running build_py
creating build
creating build/lib.linux-x86_64-3.10
creating build/lib.linux-x86_64-3.10/cryptography
copying src/cryptography/utils.py -> build/lib.linux-x86_64-3.10/cryptography
copying src/cryptography/fernet.py -> build/lib.linux-x86_64-3.10/cryptography
copying src/cryptography/exceptions.py -> build/lib.linux-x86_64-3.10/cryptography
copying src/cryptography/__init__.py -> build/lib.linux-x86_64-3.10/cryptography
copying src/cryptography/__about__.py -> build/lib.linux-x86_64-3.10/cryptography
creating build/lib.linux-x86_64-3.10/cryptography/x509
copying src/cryptography/x509/oid.py -> build/lib.linux-x86_64-3.10/cryptography/x509
copying src/cryptography/x509/ocsp.py -> build/lib.linux-x86_64-3.10/cryptography/x509
copying src/cryptography/x509/name.py -> build/lib.linux-x86_64-3.10/cryptography/x509
copying src/cryptography/x509/general_name.py -> build/lib.linux-x86_64-3.10/cryptography/x509
copying src/cryptography/x509/extensions.py -> build/lib.linux-x86_64-3.10/cryptography/x509
copying src/cryptography/x509/certificate_transparency.py -> build/lib.linux-x86_64-3.10/cryptography/x509
copying src/cryptography/x509/base.py -> build/lib.linux-x86_64-3.10/cryptography/x509
copying src/cryptography/x509/__init__.py -> build/lib.linux-x86_64-3.10/cryptography/x509
creating build/lib.linux-x86_64-3.10/cryptography/hazmat
copying src/cryptography/hazmat/_oid.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat
copying src/cryptography/hazmat/__init__.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat
creating build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/poly1305.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/padding.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/keywrap.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/hmac.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/hashes.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/constant_time.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/cmac.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/_serialization.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/_cipheralgorithm.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/_asymmetric.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/__init__.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives
creating build/lib.linux-x86_64-3.10/cryptography/hazmat/bindings
copying src/cryptography/hazmat/bindings/__init__.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/bindings
creating build/lib.linux-x86_64-3.10/cryptography/hazmat/backends
copying src/cryptography/hazmat/backends/interfaces.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/backends
copying src/cryptography/hazmat/backends/__init__.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/backends
creating build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/twofactor
copying src/cryptography/hazmat/primitives/twofactor/totp.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/twofactor
copying src/cryptography/hazmat/primitives/twofactor/hotp.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/twofactor
copying src/cryptography/hazmat/primitives/twofactor/__init__.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/twofactor
creating build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/serialization
copying src/cryptography/hazmat/primitives/serialization/ssh.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/serialization
copying src/cryptography/hazmat/primitives/serialization/pkcs7.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/serialization
copying src/cryptography/hazmat/primitives/serialization/pkcs12.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/serialization
copying src/cryptography/hazmat/primitives/serialization/base.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/serialization
copying src/cryptography/hazmat/primitives/serialization/__init__.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/serialization
creating build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/kdf
copying src/cryptography/hazmat/primitives/kdf/x963kdf.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/kdf
copying src/cryptography/hazmat/primitives/kdf/scrypt.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/kdf
copying src/cryptography/hazmat/primitives/kdf/pbkdf2.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/kdf
copying src/cryptography/hazmat/primitives/kdf/kbkdf.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/kdf
copying src/cryptography/hazmat/primitives/kdf/hkdf.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/kdf
copying src/cryptography/hazmat/primitives/kdf/concatkdf.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/kdf
copying src/cryptography/hazmat/primitives/kdf/__init__.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/kdf
creating build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/ciphers
copying src/cryptography/hazmat/primitives/ciphers/modes.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/ciphers
copying src/cryptography/hazmat/primitives/ciphers/base.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/ciphers
copying src/cryptography/hazmat/primitives/ciphers/algorithms.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/ciphers
copying src/cryptography/hazmat/primitives/ciphers/aead.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/ciphers
copying src/cryptography/hazmat/primitives/ciphers/__init__.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/ciphers
creating build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/x448.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/x25519.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/utils.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/types.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/rsa.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/padding.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/ed448.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/ed25519.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/ec.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/dsa.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/dh.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/__init__.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/primitives/asymmetric
creating build/lib.linux-x86_64-3.10/cryptography/hazmat/bindings/openssl
copying src/cryptography/hazmat/bindings/openssl/binding.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/bindings/openssl
copying src/cryptography/hazmat/bindings/openssl/_conditional.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/bindings/openssl
copying src/cryptography/hazmat/bindings/openssl/__init__.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/bindings/openssl
creating build/lib.linux-x86_64-3.10/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/x509.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/x448.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/x25519.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/utils.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/rsa.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/poly1305.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/hmac.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/hashes.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/encode_asn1.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/ed448.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/ed25519.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/ec.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/dsa.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/dh.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/decode_asn1.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/cmac.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/ciphers.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/backend.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/aead.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/__init__.py -> build/lib.linux-x86_64-3.10/cryptography/hazmat/backends/openssl
running egg_info
writing src/cryptography.egg-info/PKG-INFO
writing dependency_links to src/cryptography.egg-info/dependency_links.txt
writing requirements to src/cryptography.egg-info/requires.txt
writing top-level names to src/cryptography.egg-info/top_level.txt
listing git files failed - pretending there aren't any
reading manifest file 'src/cryptography.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching 'Cargo.lock' under directory 'src/rust'
no previously-included directories found matching 'docs/_build'
warning: no previously-included files found matching 'vectors'
warning: no previously-included files matching '*' found under directory 'vectors'
warning: no previously-included files matching '*' found under directory '.github'
warning: no previously-included files found matching 'release.py'
warning: no previously-included files found matching '.coveragerc'
warning: no previously-included files found matching 'codecov.yml'
warning: no previously-included files found matching '.readthedocs.yml'
warning: no previously-included files found matching 'dev-requirements.txt'
warning: no previously-included files found matching 'tox.ini'
warning: no previously-included files found matching 'mypy.ini'
warning: no previously-included files matching '*' found under directory '.circleci'
adding license file 'LICENSE'
adding license file 'LICENSE.APACHE'
adding license file 'LICENSE.BSD'
adding license file 'LICENSE.PSF'
writing manifest file 'src/cryptography.egg-info/SOURCES.txt'
copying src/cryptography/py.typed -> build/lib.linux-x86_64-3.10/cryptography
creating build/lib.linux-x86_64-3.10/cryptography/hazmat/bindings/_rust
copying src/cryptography/hazmat/bindings/_rust/__init__.pyi -> build/lib.linux-x86_64-3.10/cryptography/hazmat/bindings/_rust
copying src/cryptography/hazmat/bindings/_rust/asn1.pyi -> build/lib.linux-x86_64-3.10/cryptography/hazmat/bindings/_rust
copying src/cryptography/hazmat/bindings/_rust/ocsp.pyi -> build/lib.linux-x86_64-3.10/cryptography/hazmat/bindings/_rust
copying src/cryptography/hazmat/bindings/_rust/x509.pyi -> build/lib.linux-x86_64-3.10/cryptography/hazmat/bindings/_rust
running build_ext
generating cffi module 'build/temp.linux-x86_64-3.10/_openssl.c'
creating build/temp.linux-x86_64-3.10
running build_rust
error: no matching package found
searched package name: `asn1`
perhaps you meant:      paste, rand or syn
location searched: registry `crates-io`
required by package `cryptography-rust v0.1.0 (/usr/src/cryptography-36.0.2/src/rust)`

    =============================DEBUG ASSISTANCE=============================
    If you are seeing a compilation error please try the following steps to
    successfully install cryptography:
    1) Upgrade to the latest pip and try again. This will fix errors for most
       users. See: https://pip.pypa.io/en/stable/installing/#upgrading-pip
    2) Read https://cryptography.io/en/latest/installation/ for specific
       instructions for your platform.
    3) Check our frequently asked questions for more information:
       https://cryptography.io/en/latest/faq/
    4) Ensure you have a recent Rust toolchain installed:
       https://cryptography.io/en/latest/installation/#rust
    
    Python: 3.10.1
    platform: Linux-5.15.32-ipfire-x86_64-Intel-R-_Core-TM-_i5-8400_CPU_@_2.80GHz-with-glibc2.35
    pip: 21.2.4
    setuptools: 58.1.0
    setuptools_rust: 1.2.0
    =============================DEBUG ASSISTANCE=============================
    
Traceback (most recent call last):
  File "/usr/src/cryptography-36.0.2/setup.py", line 39, in <module>
    setup(
  File "/usr/lib/python3.10/site-packages/setuptools/__init__.py", line 153, in setup
    return distutils.core.setup(**attrs)
  File "/usr/lib/python3.10/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/usr/lib/python3.10/distutils/dist.py", line 966, in run_commands
    self.run_command(cmd)
  File "/usr/lib/python3.10/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/usr/lib/python3.10/distutils/command/build.py", line 135, in run
    self.run_command(cmd_name)
  File "/usr/lib/python3.10/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/lib/python3.10/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/usr/lib/python3.10/site-packages/cffi/setuptools_ext.py", line 144, in run
    base_class.run(self)
  File "/usr/lib/python3.10/site-packages/setuptools_rust/setuptools_ext.py", line 132, in run
    build_rust.run()
  File "/usr/lib/python3.10/site-packages/setuptools_rust/command.py", line 101, in run
    self.run_for_extension(ext)
  File "/usr/lib/python3.10/site-packages/setuptools_rust/build.py", line 112, in run_for_extension
    dylib_paths = self.build_extension(ext, self.target)
  File "/usr/lib/python3.10/site-packages/setuptools_rust/build.py", line 143, in build_extension
    target_dir = _base_cargo_target_dir(ext)
  File "/usr/lib/python3.10/site-packages/setuptools_rust/build.py", line 690, in _base_cargo_target_dir
    target_directory = ext._metadata()["target_directory"]
  File "/usr/lib/python3.10/site-packages/setuptools_rust/extension.py", line 225, in _metadata
    self._cargo_metadata = json.loads(subprocess.check_output(metadata_command))
  File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/usr/lib/python3.10/subprocess.py", line 524, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['cargo', 'metadata', '--manifest-path', 'src/rust/Cargo.toml', '--format-version', '1']' returned non-zero exit status 101.
make: *** [python3-cryptography:84: /usr/src/log/cryptography-36.0.2] Error 1

Re: Problem updating python3-cryptography

[Michael Tremer]

[-- 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>

Re: Problem updating python3-cryptography

[Adolf Belka]

[-- 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>
> 

Re: Problem updating python3-cryptography

[Adolf Belka]

[-- Attachment #1: Type: text/plain, Size: 3984 bytes --]

Hi Michael,

I added the rust-indoc and rust-paste packages as explicitly defined versions 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.

However, the build ended up requiring three packages that seem totally redundant to me as they are related to windows but I can't figure out how to eliminate them. Do these have to stay being included or is there a way to stop them being required.

The packages are:-

rust-winapi
rust-winapi-i686-pc-windows-gnu
rust-winapi-x86_64-pc-windows-gnu

Regards,

Adolf


On 03/05/2022 23:02, Adolf Belka wrote:
> 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>
>>

Re: Problem updating python3-cryptography

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 5449 bytes --]

Hello Adolf,

I ran into those problems too when I packaged the first bunch of rust packages.

The problem is, that cargo cannot easily differentiate what dependencies it actually needs. Developers of those crates can list certain dependencies for only certain platforms (e.g. Windows), and those will only be built on those 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 packages live using cargo.

What I have done in those cases is just remove those dependencies manually:

https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/patches/rust-dirs-1.0.5-fix-metadata.patch;h=0c51222127924cab1d6a85ee099c7bd05667948a;hb=HEAD
https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/patches/rust-getrandom-0.2.4-fix-metadata.patch;h=083b6d6c80a5577a349f8dbe34929b48229ca05d;hb=HEAD
https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/patches/rust-home-0.5.3-fix-metadata.patch;h=78e154af69554b3b53ab067d8f1722ef069ddf7d;hb=HEAD

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.

-Michael

> On 15 Jun 2022, at 21:02, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi Michael,
> 
> I added the rust-indoc and rust-paste packages as explicitly defined versions 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.
> 
> However, the build ended up requiring three packages that seem totally redundant to me as they are related to windows but I can't figure out how to eliminate them. Do these have to stay being included or is there a way to stop them being required.
> 
> The packages are:-
> 
> rust-winapi
> rust-winapi-i686-pc-windows-gnu
> rust-winapi-x86_64-pc-windows-gnu
> 
> Regards,
> 
> Adolf
> 
> 
> On 03/05/2022 23:02, Adolf Belka wrote:
>> 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>
>>> 

Re: Problem updating python3-cryptography

[Adolf Belka]

[-- Attachment #1: Type: text/plain, Size: 5953 bytes --]

Hi Michael,

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 packages.
> 
> The problem is, that cargo cannot easily differentiate what dependencies it actually needs. Developers of those crates can list certain dependencies for only certain platforms (e.g. Windows), and those will only be built on those 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 packages live using cargo.
> 
> What I have done in those cases is just remove those dependencies manually:
> 
> https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/patches/rust-dirs-1.0.5-fix-metadata.patch;h=0c51222127924cab1d6a85ee099c7bd05667948a;hb=HEAD
> https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/patches/rust-getrandom-0.2.4-fix-metadata.patch;h=083b6d6c80a5577a349f8dbe34929b48229ca05d;hb=HEAD
> https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/patches/rust-home-0.5.3-fix-metadata.patch;h=78e154af69554b3b53ab067d8f1722ef069ddf7d;hb=HEAD
> 
> 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 patch to exclude winapi which will stop the need for the other winapi files.
The build is running now.

I think I am now close to being able to release the updated python3-cryptography. Thanks very much for the help. I have learnt a lot with this.

Regards,

Adolf.
> 
> -Michael
> 
>> On 15 Jun 2022, at 21:02, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> Hi Michael,
>>
>> I added the rust-indoc and rust-paste packages as explicitly defined versions 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.
>>
>> However, the build ended up requiring three packages that seem totally redundant to me as they are related to windows but I can't figure out how to eliminate them. Do these have to stay being included or is there a way to stop them being required.
>>
>> The packages are:-
>>
>> rust-winapi
>> rust-winapi-i686-pc-windows-gnu
>> rust-winapi-x86_64-pc-windows-gnu
>>
>> Regards,
>>
>> Adolf
>>
>>
>> On 03/05/2022 23:02, Adolf Belka wrote:
>>> 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>
>>>>
> 

Re: Problem updating python3-cryptography

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 6232 bytes --]

Hello,

> On 16 Jun 2022, at 14:43, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi Michael,
> 
> 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 packages.
>> The problem is, that cargo cannot easily differentiate what dependencies it actually needs. Developers of those crates can list certain dependencies for only certain platforms (e.g. Windows), and those will only be built on those 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 packages live using cargo.
>> What I have done in those cases is just remove those dependencies manually:
>> https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/patches/rust-dirs-1.0.5-fix-metadata.patch;h=0c51222127924cab1d6a85ee099c7bd05667948a;hb=HEAD
>> https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/patches/rust-getrandom-0.2.4-fix-metadata.patch;h=083b6d6c80a5577a349f8dbe34929b48229ca05d;hb=HEAD
>> https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/patches/rust-home-0.5.3-fix-metadata.patch;h=78e154af69554b3b53ab067d8f1722ef069ddf7d;hb=HEAD
>> 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 patch to exclude winapi which will stop the need for the other winapi files.
> The build is running now.
> 
> I think I am now close to being able to release the updated python3-cryptography. Thanks very much for the help. I have learnt a lot with this.

Mainly how unpleasant the Rust eco system is for distributions?

> 
> Regards,
> 
> Adolf.
>> -Michael
>>> On 15 Jun 2022, at 21:02, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>> 
>>> Hi Michael,
>>> 
>>> I added the rust-indoc and rust-paste packages as explicitly defined versions 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.
>>> 
>>> However, the build ended up requiring three packages that seem totally redundant to me as they are related to windows but I can't figure out how to eliminate them. Do these have to stay being included or is there a way to stop them being required.
>>> 
>>> The packages are:-
>>> 
>>> rust-winapi
>>> rust-winapi-i686-pc-windows-gnu
>>> rust-winapi-x86_64-pc-windows-gnu
>>> 
>>> Regards,
>>> 
>>> Adolf
>>> 
>>> 
>>> On 03/05/2022 23:02, Adolf Belka wrote:
>>>> 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>
>>>>>