15348 2024-01-17 01:31:19 +0000 layerindex: update_layer.py remove use of deprecated pkg_resources 2024-02-01 02:35:41 +0000 1 1 6 Yocto Project Subprojects Layer Index Layer Index 5.0 x86 Multiple RESOLVED FIXED Medium normal 5.0 M3 1 tim.orling tim.orling apoorvsangal --- --- Don't know oldest_to_newest 97805 0 tim.orling 2024-01-17 01:31:19 +0000 /opt/layerindex/layerindex/update_layer.py:22: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html from pkg_resources import parse_version 97884 1 tim.orling 2024-01-18 01:54:46 +0000 https://patchwork.yoctoproject.org/project/yocto/patch/20240118014528.564270-1-tim.orling@konsulko.com/ 97941 2 tim.orling 2024-01-22 20:19:28 +0000 packaging.version.parse() seemed like a good replacement, but it cannot handle versions like autotools (2.72d) since it does not match the PEP-440 patterns for allowed Python package versions. https://github.com/pypa/packaging/issues/631 https://packaging.python.org/en/latest/specifications/version-specifiers/#summary-of-differences-from-pkg-resources-parse-version "This specification purposely restricts the syntax which constitutes a valid version while pkg_resources.parse_version attempts to provide some meaning from any arbitrary string." Which means that any Python which has "packaging" >= 22 will no longer parse LegacyVersion() and it throws an InvalidVersion exception with "packaging" == 21 Invalid version: '2.72e' Probably better off using the vercmp code from lib/bb/utils.py. 97948 3 tim.orling 2024-01-23 01:08:32 +0000 pypi.org has a similar problem of needing the LegacyVersion behavior, so we use their packaging_legacy instead in v2: https://patchwork.yoctoproject.org/project/yocto/patch/20240123001125.1470142-1-tim.orling@konsulko.com/ 98078 4 tim.orling 2024-02-01 02:35:41 +0000 Merged: https://git.yoctoproject.org/layerindex-web/commit/?id=83378f2f9c881505027220a98514bcb933d82682 and deployed.