Bump of packaging-21.3 to packaging-22.0 breaks cyclonedx-python

Traceback (most recent call last):
  File "sources/env/bin/cyclonedx-py", line 5, in <module>
    from cyclonedx_py.client import main
  File "sources/env/lib/python3.10/site-packages/cyclonedx_py/client.py", line 37, in <module>
    from .parser.requirements import RequirementsParser
  File "sources/env/lib/python3.10/site-packages/cyclonedx_py/parser/requirements.py", line 31, in <module>
    from pip_requirements_parser import RequirementsFile  # type: ignore
  File "sources/env/lib/python3.10/site-packages/pip_requirements_parser.py", line 73, in <module>
    from packaging.version import LegacyVersion
ImportError: cannot import name 'LegacyVersion' from 'packaging.version' (sources/env/lib/python3.10/site-packages/packaging/version.py)

[jkowalleck]

thank you all for the input and your work.

a fix was released via v3.7.3

[jkowalleck]

re: https://github.com/CycloneDX/cyclonedx-python/issues/449#issuecomment-1345420178

why upgrade pip-requirements-parser==32.0.0? This project clearly defines:

install_requires = \
['cyclonedx-python-lib>=2.0.0,<4.0.0',
 'packageurl-python>=0.9',
 'pip-requirements-parser>=31.2.0,<32.0.0',
 'setuptools>=47.0.0',
 'toml>=0.10.0,<0.11.0']

This package here is one of many downstream users of pip-requirements-parser. If pip-requirements-parser had errors, then they need to fix their own dependencies in a 31.X.Y release - where they missed their dependency goals. Go to https://github.com/nexB/pip-requirements-parser/issues and ask to the needed backport of the pinning to a new patched version 31.2.1.

anyways, i will try to prep a version that works with pip-requirements-parser: ^32