Unable to emerge cryptography-40.0.1 #1759

New Issue

RayOfLight · 2023-07-25T12:32:57+02:00

RayOfLight commented

2023-07-25 12:32:57 +02:00

I post 40.0.1 error below, It seems that dev-python/cryptography-40.0.2-r2::gentoo is able to be merged, with this error, I can't emerge homeassistant-min-2023.5.4 yet

/usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'cryptography.hazmat.bindings._rust' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'cryptography.hazmat.bindings._rust' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'cryptography.hazmat.bindings._rust' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'cryptography.hazmat.bindings._rust' to be distributed and are
        already explicitly excluding 'cryptography.hazmat.bindings._rust' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'cryptography.hazmat.bindings._rust.openssl' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'cryptography.hazmat.bindings._rust.openssl' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'cryptography.hazmat.bindings._rust.openssl' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'cryptography.hazmat.bindings._rust.openssl' to be distributed and are
        already explicitly excluding 'cryptography.hazmat.bindings._rust.openssl' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
2023-07-25 12:02:02,128 root INFO copying src/cryptography/py.typed -> build/lib.linux-x86_64-cpython-311/cryptography
2023-07-25 12:02:02,129 root INFO creating build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust
2023-07-25 12:02:02,129 root INFO copying src/cryptography/hazmat/bindings/_rust/__init__.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust
2023-07-25 12:02:02,130 root INFO copying src/cryptography/hazmat/bindings/_rust/_openssl.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust
2023-07-25 12:02:02,131 root INFO copying src/cryptography/hazmat/bindings/_rust/asn1.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust
2023-07-25 12:02:02,132 root INFO copying src/cryptography/hazmat/bindings/_rust/ocsp.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust
2023-07-25 12:02:02,132 root INFO copying src/cryptography/hazmat/bindings/_rust/pkcs7.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust
2023-07-25 12:02:02,133 root INFO copying src/cryptography/hazmat/bindings/_rust/x509.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust
2023-07-25 12:02:02,134 root INFO creating build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust/openssl
2023-07-25 12:02:02,134 root INFO copying src/cryptography/hazmat/bindings/_rust/openssl/__init__.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust/openssl
2023-07-25 12:02:02,135 root INFO copying src/cryptography/hazmat/bindings/_rust/openssl/x25519.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust/openssl
2023-07-25 12:02:02,144 root WARNING warning: build_py: byte-compiling is disabled, skipping.

2023-07-25 12:02:02,144 root INFO running build_ext
2023-07-25 12:02:02,145 root INFO running build_rust
cargo rustc --lib --message-format=json-render-diagnostics --manifest-path src/rust/Cargo.toml --release -v --features pyo3/extension-module pyo3/abi3-py36 --crate-type cdylib --
error: failed to select a version for the requirement `asn1 = "^0.13.0"` (locked to 0.13.0)
candidate versions found which didn't match: 0.12.2
location searched: directory source `/var/tmp/portage/dev-python/cryptography-40.0.1/work/cargo_home/gentoo` (which is replacing registry `crates-io`)
required by package `cryptography-rust v0.1.0 (/var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1/src/rust)`
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.

    =============================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.11.4
    platform: Linux-6.4.3-gentoo-x86_64-Intel-R-_Core-TM-_i7-3517U_CPU_@_1.90GHz-with-glibc2.37
    pip: 23.0.1
    setuptools: 67.8.0
    setuptools_rust: 1.6.0
    rustc: 1.69.0 (84c898d65 2023-04-16) (gentoo)
    =============================DEBUG ASSISTANCE=============================

error: `cargo rustc --lib --message-format=json-render-diagnostics --manifest-path src/rust/Cargo.toml --release -v --features 'pyo3/extension-module pyo3/abi3-py36' --crate-type cdylib --` failed with code 101
 * ERROR: dev-python/cryptography-40.0.1::HomeAssistantRepository failed (compile phase):
 *   Wheel build failed
 *
 * Call stack:
 *     ebuild.sh, line  136:  Called src_compile
 *   environment, line 4277:  Called distutils-r1_src_compile
 *   environment, line 2242:  Called _distutils-r1_run_foreach_impl 'distutils-r1_python_compile'
 *   environment, line  919:  Called python_foreach_impl 'distutils-r1_run_phase' 'distutils-r1_python_compile'
 *   environment, line 3895:  Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile'
 *   environment, line 3399:  Called _multibuild_run '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile'
 *   environment, line 3397:  Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'distutils-r1_python_compile'
 *   environment, line 1347:  Called distutils-r1_run_phase 'distutils-r1_python_compile'
 *   environment, line 2224:  Called distutils-r1_python_compile
 *   environment, line 2043:  Called distutils_pep517_install '/var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1-python3_11/install'
 *   environment, line 2582:  Called die
 * The specific snippet of code:
 *       [[ -n ${wheel} ]] || die "No wheel name returned";
 *
 * If you need support, post the output of `emerge --info '=dev-python/cryptography-40.0.1::HomeAssistantRepository'`,
 * the complete build log and the output of `emerge -pqv '=dev-python/cryptography-40.0.1::HomeAssistantRepository'`.
 * The complete build log is located at '/var/tmp/portage/dev-python/cryptography-40.0.1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-python/cryptography-40.0.1/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1'
 * S: '/var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1'

I post 40.0.1 error below, It seems that dev-python/cryptography-40.0.2-r2::gentoo is able to be merged, with this error, I can't emerge homeassistant-min-2023.5.4 yet ``` /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'cryptography.hazmat.bindings._rust' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cryptography.hazmat.bindings._rust' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cryptography.hazmat.bindings._rust' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cryptography.hazmat.bindings._rust' to be distributed and are already explicitly excluding 'cryptography.hazmat.bindings._rust' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'cryptography.hazmat.bindings._rust.openssl' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cryptography.hazmat.bindings._rust.openssl' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cryptography.hazmat.bindings._rust.openssl' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cryptography.hazmat.bindings._rust.openssl' to be distributed and are already explicitly excluding 'cryptography.hazmat.bindings._rust.openssl' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) 2023-07-25 12:02:02,128 root INFO copying src/cryptography/py.typed -> build/lib.linux-x86_64-cpython-311/cryptography 2023-07-25 12:02:02,129 root INFO creating build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust 2023-07-25 12:02:02,129 root INFO copying src/cryptography/hazmat/bindings/_rust/__init__.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust 2023-07-25 12:02:02,130 root INFO copying src/cryptography/hazmat/bindings/_rust/_openssl.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust 2023-07-25 12:02:02,131 root INFO copying src/cryptography/hazmat/bindings/_rust/asn1.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust 2023-07-25 12:02:02,132 root INFO copying src/cryptography/hazmat/bindings/_rust/ocsp.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust 2023-07-25 12:02:02,132 root INFO copying src/cryptography/hazmat/bindings/_rust/pkcs7.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust 2023-07-25 12:02:02,133 root INFO copying src/cryptography/hazmat/bindings/_rust/x509.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust 2023-07-25 12:02:02,134 root INFO creating build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust/openssl 2023-07-25 12:02:02,134 root INFO copying src/cryptography/hazmat/bindings/_rust/openssl/__init__.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust/openssl 2023-07-25 12:02:02,135 root INFO copying src/cryptography/hazmat/bindings/_rust/openssl/x25519.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust/openssl 2023-07-25 12:02:02,144 root WARNING warning: build_py: byte-compiling is disabled, skipping. 2023-07-25 12:02:02,144 root INFO running build_ext 2023-07-25 12:02:02,145 root INFO running build_rust cargo rustc --lib --message-format=json-render-diagnostics --manifest-path src/rust/Cargo.toml --release -v --features pyo3/extension-module pyo3/abi3-py36 --crate-type cdylib -- error: failed to select a version for the requirement `asn1 = "^0.13.0"` (locked to 0.13.0) candidate versions found which didn't match: 0.12.2 location searched: directory source `/var/tmp/portage/dev-python/cryptography-40.0.1/work/cargo_home/gentoo` (which is replacing registry `crates-io`) required by package `cryptography-rust v0.1.0 (/var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1/src/rust)` 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. =============================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.11.4 platform: Linux-6.4.3-gentoo-x86_64-Intel-R-_Core-TM-_i7-3517U_CPU_@_1.90GHz-with-glibc2.37 pip: 23.0.1 setuptools: 67.8.0 setuptools_rust: 1.6.0 rustc: 1.69.0 (84c898d65 2023-04-16) (gentoo) =============================DEBUG ASSISTANCE============================= error: `cargo rustc --lib --message-format=json-render-diagnostics --manifest-path src/rust/Cargo.toml --release -v --features 'pyo3/extension-module pyo3/abi3-py36' --crate-type cdylib --` failed with code 101 * ERROR: dev-python/cryptography-40.0.1::HomeAssistantRepository failed (compile phase): * Wheel build failed * * Call stack: * ebuild.sh, line 136: Called src_compile * environment, line 4277: Called distutils-r1_src_compile * environment, line 2242: Called _distutils-r1_run_foreach_impl 'distutils-r1_python_compile' * environment, line 919: Called python_foreach_impl 'distutils-r1_run_phase' 'distutils-r1_python_compile' * environment, line 3895: Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile' * environment, line 3399: Called _multibuild_run '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile' * environment, line 3397: Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'distutils-r1_python_compile' * environment, line 1347: Called distutils-r1_run_phase 'distutils-r1_python_compile' * environment, line 2224: Called distutils-r1_python_compile * environment, line 2043: Called distutils_pep517_install '/var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1-python3_11/install' * environment, line 2582: Called die * The specific snippet of code: * [[ -n ${wheel} ]] || die "No wheel name returned"; * * If you need support, post the output of `emerge --info '=dev-python/cryptography-40.0.1::HomeAssistantRepository'`, * the complete build log and the output of `emerge -pqv '=dev-python/cryptography-40.0.1::HomeAssistantRepository'`. * The complete build log is located at '/var/tmp/portage/dev-python/cryptography-40.0.1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-python/cryptography-40.0.1/temp/environment'. * Working directory: '/var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1' * S: '/var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1' ```

Tatsh commented

2023-07-28 09:53:03 +02:00

I am assuming you have LTO enabled. Try turning it off with package.env.

/etc/portage/env/no-lto

CFLAGS="-O2 -march=native -mtune=native -pipe"
CXXFLAGS="${CFLAGS}"
USE="${USE} -lto"

/etc/portage/package.env/no-lto

dev-python/cryptography no-lto

I am assuming you have LTO enabled. Try turning it off with `package.env`. `/etc/portage/env/no-lto` ```shell CFLAGS="-O2 -march=native -mtune=native -pipe" CXXFLAGS="${CFLAGS}" USE="${USE} -lto" ``` `/etc/portage/package.env/no-lto` ``` dev-python/cryptography no-lto ```

RayOfLight commented

2023-07-28 14:41:31 +02:00

Is this test valid?

% pwd
/var/lib/layman/HomeAssistantRepository/dev-python/cryptography

% sudo CFLAGS="-O2 -march=native -mtune=native -pipe" CXXFLAGS="${CFLAGS}" USE="${USE} -lto" ebuild cryptography-40.0.1.ebuild merge

[...]

>>> Compiling source in /var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1 ...
* python3_11: running distutils-r1_run_phase distutils-r1_python_compile
* A 'build' directory exists already.  Artifacts from this directory may
* be picked up by setuptools when building for another interpreter.
* Please remove this directory prior to building.
*   Building the wheel for cryptography-40.0.1 via setuptools.build_meta
gpep517 build-wheel --backend setuptools.build_meta --output-fd 3 --wheel-dir /var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1-python3_11/wheel
2023-07-28 14:29:52,952 gpep517 INFO Building wheel via backend setuptools.build_meta
2023-07-28 14:29:53,935 root INFO running bdist_wheel
2023-07-28 14:29:54,158 root INFO running build
2023-07-28 14:29:54,158 root INFO running build_py
2023-07-28 14:29:54,254 root INFO running egg_info
2023-07-28 14:29:54,406 root INFO writing src/cryptography.egg-info/PKG-INFO
2023-07-28 14:29:54,407 root INFO writing dependency_links to src/cryptography.egg-info/dependency_links.txt
2023-07-28 14:29:54,408 root INFO writing requirements to src/cryptography.egg-info/requires.txt
2023-07-28 14:29:54,408 root INFO writing top-level names to src/cryptography.egg-info/top_level.txt
2023-07-28 14:29:54,660 setuptools_scm.file_finder_git ERROR listing git files failed - pretending there aren't any
2023-07-28 14:29:54,669 root INFO reading manifest file 'src/cryptography.egg-info/SOURCES.txt'
2023-07-28 14:29:54,677 root INFO reading manifest template 'MANIFEST.in'
2023-07-28 14:29:54,778 root WARNING no previously-included directories found matching 'docs/_build'
2023-07-28 14:29:54,805 root WARNING warning: no previously-included files found matching 'vectors'
2023-07-28 14:29:54,807 root WARNING warning: no previously-included files matching '*' found under directory 'vectors'
2023-07-28 14:29:54,809 root WARNING warning: no previously-included files matching '*' found under directory '.github'
2023-07-28 14:29:54,810 root WARNING warning: no previously-included files found matching 'release.py'
2023-07-28 14:29:54,811 root WARNING warning: no previously-included files found matching '.readthedocs.yml'
2023-07-28 14:29:54,813 root WARNING warning: no previously-included files found matching 'ci-constraints-requirements.txt'
2023-07-28 14:29:54,814 root WARNING warning: no previously-included files found matching 'mypy.ini'
2023-07-28 14:29:54,815 root INFO adding license file 'LICENSE'
2023-07-28 14:29:54,815 root INFO adding license file 'LICENSE.APACHE'
2023-07-28 14:29:54,815 root INFO adding license file 'LICENSE.BSD'
2023-07-28 14:29:54,815 root INFO adding license file 'LICENSE.PSF'
2023-07-28 14:29:54,840 root INFO writing manifest file 'src/cryptography.egg-info/SOURCES.txt'
/usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'cryptography.hazmat.bindings._rust' is absent from the `packages` configuration.
!!

********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'cryptography.hazmat.bindings._rust' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.

This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'cryptography.hazmat.bindings._rust' is explicitly added
to the `packages` configuration field.

Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).

You can read more about "package discovery" on setuptools documentation page:

- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

If you don't want 'cryptography.hazmat.bindings._rust' to be distributed and are
already explicitly excluding 'cryptography.hazmat.bindings._rust' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.

You can read more about "package data files" on setuptools documentation page:

- https://setuptools.pypa.io/en/latest/userguide/datafiles.html


[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************

!!
check.warn(importable)
/usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'cryptography.hazmat.bindings._rust.openssl' is absent from the `packages` configuration.
!!

********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'cryptography.hazmat.bindings._rust.openssl' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.

This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'cryptography.hazmat.bindings._rust.openssl' is explicitly added
to the `packages` configuration field.

Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).

You can read more about "package discovery" on setuptools documentation page:

- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

If you don't want 'cryptography.hazmat.bindings._rust.openssl' to be distributed and are
already explicitly excluding 'cryptography.hazmat.bindings._rust.openssl' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.

You can read more about "package data files" on setuptools documentation page:

- https://setuptools.pypa.io/en/latest/userguide/datafiles.html


[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************

!!
check.warn(importable)
2023-07-28 14:29:54,872 root WARNING warning: build_py: byte-compiling is disabled, skipping.

2023-07-28 14:29:54,873 root INFO running build_ext
2023-07-28 14:29:54,873 root INFO running build_rust
cargo rustc --lib --message-format=json-render-diagnostics --manifest-path src/rust/Cargo.toml --release -v --features pyo3/extension-module pyo3/abi3-py36 --crate-type cdylib --
error: failed to select a version for the requirement `asn1 = "^0.13.0"` (locked to 0.13.0)
candidate versions found which didn't match: 0.12.2
location searched: directory source `/var/tmp/portage/dev-python/cryptography-40.0.1/work/cargo_home/gentoo` (which is replacing registry `crates-io`)
required by package `cryptography-rust v0.1.0 (/var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1/src/rust)`
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.

=============================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.11.4
platform: Linux-6.4.3-gentoo-x86_64-Intel-R-_Core-TM-_i7-3517U_CPU_@_1.90GHz-with-glibc2.37
pip: 23.0.1
setuptools: 67.8.0
setuptools_rust: 1.6.0
rustc: 1.69.0 (84c898d65 2023-04-16) (gentoo)
=============================DEBUG ASSISTANCE=============================

error: `cargo rustc --lib --message-format=json-render-diagnostics --manifest-path src/rust/Cargo.toml --release -v --features 'pyo3/extension-module pyo3/abi3-py36' --crate-type cdylib --` failed with code 101
* ERROR: dev-python/cryptography-40.0.1::HomeAssistantRepository failed (compile phase):
*   Wheel build failed
*
* Call stack:
*     ebuild.sh, line  136:  Called src_compile
*   environment, line 4277:  Called distutils-r1_src_compile
*   environment, line 2242:  Called _distutils-r1_run_foreach_impl 'distutils-r1_python_compile'
*   environment, line  919:  Called python_foreach_impl 'distutils-r1_run_phase' 'distutils-r1_python_compile'
*   environment, line 3895:  Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile'
*   environment, line 3399:  Called _multibuild_run '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile'
*   environment, line 3397:  Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'distutils-r1_python_compile'
*   environment, line 1347:  Called distutils-r1_run_phase 'distutils-r1_python_compile'
*   environment, line 2224:  Called distutils-r1_python_compile
*   environment, line 2043:  Called distutils_pep517_install '/var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1-python3_11/install'
*   environment, line 2582:  Called die
* The specific snippet of code:
*       [[ -n ${wheel} ]] || die "No wheel name returned";
*
* If you need support, post the output of `emerge --info '=dev-python/cryptography-40.0.1::HomeAssistantRepository'`,
* the complete build log and the output of `emerge -pqv '=dev-python/cryptography-40.0.1::HomeAssistantRepository'`.
* The complete build log is located at '/var/tmp/portage/dev-python/cryptography-40.0.1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-python/cryptography-40.0.1/temp/environment'.
* Working directory: '/var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1'
* S: '/var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1'

* Messages for package dev-python/cryptography-40.0.1:

* ERROR: dev-python/cryptography-40.0.1::HomeAssistantRepository failed (compile phase):
*   Wheel build failed
*
* Call stack:
*     ebuild.sh, line  136:  Called src_compile
*   environment, line 4277:  Called distutils-r1_src_compile
*   environment, line 2242:  Called _distutils-r1_run_foreach_impl 'distutils-r1_python_compile'
*   environment, line  919:  Called python_foreach_impl 'distutils-r1_run_phase' 'distutils-r1_python_compile'
*   environment, line 3895:  Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile'
*   environment, line 3399:  Called _multibuild_run '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile'
*   environment, line 3397:  Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'distutils-r1_python_compile'
*   environment, line 1347:  Called distutils-r1_run_phase 'distutils-r1_python_compile'
*   environment, line 2224:  Called distutils-r1_python_compile
*   environment, line 2043:  Called distutils_pep517_install '/var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1-python3_11/install'
*   environment, line 2582:  Called die
* The specific snippet of code:
*       [[ -n ${wheel} ]] || die "No wheel name returned";
*
* If you need support, post the output of `emerge --info '=dev-python/cryptography-40.0.1::HomeAssistantRepository'`,
* the complete build log and the output of `emerge -pqv '=dev-python/cryptography-40.0.1::HomeAssistantRepository'`.
* The complete build log is located at '/var/tmp/portage/dev-python/cryptography-40.0.1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-python/cryptography-40.0.1/temp/environment'.
* Working directory: '/var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1'
* S: '/var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1'

Is this test valid? ``` % pwd /var/lib/layman/HomeAssistantRepository/dev-python/cryptography ``` ``` % sudo CFLAGS="-O2 -march=native -mtune=native -pipe" CXXFLAGS="${CFLAGS}" USE="${USE} -lto" ebuild cryptography-40.0.1.ebuild merge ``` [...] ``` >>> Compiling source in /var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1 ... * python3_11: running distutils-r1_run_phase distutils-r1_python_compile * A 'build' directory exists already. Artifacts from this directory may * be picked up by setuptools when building for another interpreter. * Please remove this directory prior to building. * Building the wheel for cryptography-40.0.1 via setuptools.build_meta gpep517 build-wheel --backend setuptools.build_meta --output-fd 3 --wheel-dir /var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1-python3_11/wheel 2023-07-28 14:29:52,952 gpep517 INFO Building wheel via backend setuptools.build_meta 2023-07-28 14:29:53,935 root INFO running bdist_wheel 2023-07-28 14:29:54,158 root INFO running build 2023-07-28 14:29:54,158 root INFO running build_py 2023-07-28 14:29:54,254 root INFO running egg_info 2023-07-28 14:29:54,406 root INFO writing src/cryptography.egg-info/PKG-INFO 2023-07-28 14:29:54,407 root INFO writing dependency_links to src/cryptography.egg-info/dependency_links.txt 2023-07-28 14:29:54,408 root INFO writing requirements to src/cryptography.egg-info/requires.txt 2023-07-28 14:29:54,408 root INFO writing top-level names to src/cryptography.egg-info/top_level.txt 2023-07-28 14:29:54,660 setuptools_scm.file_finder_git ERROR listing git files failed - pretending there aren't any 2023-07-28 14:29:54,669 root INFO reading manifest file 'src/cryptography.egg-info/SOURCES.txt' 2023-07-28 14:29:54,677 root INFO reading manifest template 'MANIFEST.in' 2023-07-28 14:29:54,778 root WARNING no previously-included directories found matching 'docs/_build' 2023-07-28 14:29:54,805 root WARNING warning: no previously-included files found matching 'vectors' 2023-07-28 14:29:54,807 root WARNING warning: no previously-included files matching '*' found under directory 'vectors' 2023-07-28 14:29:54,809 root WARNING warning: no previously-included files matching '*' found under directory '.github' 2023-07-28 14:29:54,810 root WARNING warning: no previously-included files found matching 'release.py' 2023-07-28 14:29:54,811 root WARNING warning: no previously-included files found matching '.readthedocs.yml' 2023-07-28 14:29:54,813 root WARNING warning: no previously-included files found matching 'ci-constraints-requirements.txt' 2023-07-28 14:29:54,814 root WARNING warning: no previously-included files found matching 'mypy.ini' 2023-07-28 14:29:54,815 root INFO adding license file 'LICENSE' 2023-07-28 14:29:54,815 root INFO adding license file 'LICENSE.APACHE' 2023-07-28 14:29:54,815 root INFO adding license file 'LICENSE.BSD' 2023-07-28 14:29:54,815 root INFO adding license file 'LICENSE.PSF' 2023-07-28 14:29:54,840 root INFO writing manifest file 'src/cryptography.egg-info/SOURCES.txt' /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'cryptography.hazmat.bindings._rust' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cryptography.hazmat.bindings._rust' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cryptography.hazmat.bindings._rust' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cryptography.hazmat.bindings._rust' to be distributed and are already explicitly excluding 'cryptography.hazmat.bindings._rust' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'cryptography.hazmat.bindings._rust.openssl' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cryptography.hazmat.bindings._rust.openssl' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cryptography.hazmat.bindings._rust.openssl' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cryptography.hazmat.bindings._rust.openssl' to be distributed and are already explicitly excluding 'cryptography.hazmat.bindings._rust.openssl' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) 2023-07-28 14:29:54,872 root WARNING warning: build_py: byte-compiling is disabled, skipping. 2023-07-28 14:29:54,873 root INFO running build_ext 2023-07-28 14:29:54,873 root INFO running build_rust cargo rustc --lib --message-format=json-render-diagnostics --manifest-path src/rust/Cargo.toml --release -v --features pyo3/extension-module pyo3/abi3-py36 --crate-type cdylib -- error: failed to select a version for the requirement `asn1 = "^0.13.0"` (locked to 0.13.0) candidate versions found which didn't match: 0.12.2 location searched: directory source `/var/tmp/portage/dev-python/cryptography-40.0.1/work/cargo_home/gentoo` (which is replacing registry `crates-io`) required by package `cryptography-rust v0.1.0 (/var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1/src/rust)` 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. =============================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.11.4 platform: Linux-6.4.3-gentoo-x86_64-Intel-R-_Core-TM-_i7-3517U_CPU_@_1.90GHz-with-glibc2.37 pip: 23.0.1 setuptools: 67.8.0 setuptools_rust: 1.6.0 rustc: 1.69.0 (84c898d65 2023-04-16) (gentoo) =============================DEBUG ASSISTANCE============================= error: `cargo rustc --lib --message-format=json-render-diagnostics --manifest-path src/rust/Cargo.toml --release -v --features 'pyo3/extension-module pyo3/abi3-py36' --crate-type cdylib --` failed with code 101 * ERROR: dev-python/cryptography-40.0.1::HomeAssistantRepository failed (compile phase): * Wheel build failed * * Call stack: * ebuild.sh, line 136: Called src_compile * environment, line 4277: Called distutils-r1_src_compile * environment, line 2242: Called _distutils-r1_run_foreach_impl 'distutils-r1_python_compile' * environment, line 919: Called python_foreach_impl 'distutils-r1_run_phase' 'distutils-r1_python_compile' * environment, line 3895: Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile' * environment, line 3399: Called _multibuild_run '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile' * environment, line 3397: Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'distutils-r1_python_compile' * environment, line 1347: Called distutils-r1_run_phase 'distutils-r1_python_compile' * environment, line 2224: Called distutils-r1_python_compile * environment, line 2043: Called distutils_pep517_install '/var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1-python3_11/install' * environment, line 2582: Called die * The specific snippet of code: * [[ -n ${wheel} ]] || die "No wheel name returned"; * * If you need support, post the output of `emerge --info '=dev-python/cryptography-40.0.1::HomeAssistantRepository'`, * the complete build log and the output of `emerge -pqv '=dev-python/cryptography-40.0.1::HomeAssistantRepository'`. * The complete build log is located at '/var/tmp/portage/dev-python/cryptography-40.0.1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-python/cryptography-40.0.1/temp/environment'. * Working directory: '/var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1' * S: '/var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1' * Messages for package dev-python/cryptography-40.0.1: * ERROR: dev-python/cryptography-40.0.1::HomeAssistantRepository failed (compile phase): * Wheel build failed * * Call stack: * ebuild.sh, line 136: Called src_compile * environment, line 4277: Called distutils-r1_src_compile * environment, line 2242: Called _distutils-r1_run_foreach_impl 'distutils-r1_python_compile' * environment, line 919: Called python_foreach_impl 'distutils-r1_run_phase' 'distutils-r1_python_compile' * environment, line 3895: Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile' * environment, line 3399: Called _multibuild_run '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile' * environment, line 3397: Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'distutils-r1_python_compile' * environment, line 1347: Called distutils-r1_run_phase 'distutils-r1_python_compile' * environment, line 2224: Called distutils-r1_python_compile * environment, line 2043: Called distutils_pep517_install '/var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1-python3_11/install' * environment, line 2582: Called die * The specific snippet of code: * [[ -n ${wheel} ]] || die "No wheel name returned"; * * If you need support, post the output of `emerge --info '=dev-python/cryptography-40.0.1::HomeAssistantRepository'`, * the complete build log and the output of `emerge -pqv '=dev-python/cryptography-40.0.1::HomeAssistantRepository'`. * The complete build log is located at '/var/tmp/portage/dev-python/cryptography-40.0.1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-python/cryptography-40.0.1/temp/environment'. * Working directory: '/var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1' * S: '/var/tmp/portage/dev-python/cryptography-40.0.1/work/cryptography-40.0.1' ```

Tatsh commented

2023-07-28 16:04:59 +02:00

The real error is the lock file is not matching, so you should update the title of this ticket.

error: failed to select a version for the requirement `asn1 = "^0.13.0"` (locked to 0.13.0)

This is the same error I had and is related to #1761.

If you want you can try my patch there and it will pull in cryptography-40.0.2 from Gentoo's repository.

The real error is the lock file is not matching, so you should update the title of this ticket. ``` error: failed to select a version for the requirement `asn1 = "^0.13.0"` (locked to 0.13.0) ``` This is the same error I had and is related to #1761. If you want you can try my patch there and it will pull in cryptography-40.0.2 from Gentoo's repository.