When trying to install CaPyCli system-wide on Debian Trixie, it fails due to a conflict of the old, pinned "wheel" dependency of CaPyCli with the "wheel" version pre-installed on Debian's Python:
# pip install --break-system-packages capycli
Installing collected packages: spinners, sortedcontainers, pytz, boolean.py, wheel, urllib3, tzlocal, typing-extensions, types-setuptools, termcolor, soupsieve, six, semver, rpds-py, regex, pyjwt, packageurl-python, license-expression, importlib-resources, et-xmlfile, defusedxml, colorama, cli-support, attrs, validation, requirements-parser, requests, referencing, python-dateutil, py-serializable, openpyxl, log_symbols, beautifulsoup4, sw360, jsonschema-specifications, halo, dateparser, cyclonedx-python-lib, jsonschema, capycli
Attempting uninstall: wheel
Found existing installation: wheel 0.46.1
error: uninstall-no-record-file
× Cannot uninstall wheel 0.46.1
╰─> The package's contents are unknown: no RECORD file was found for wheel.
hint: The package was installed by debian. You should check if it can uninstall the package.
Yes, I know, I should install in a venv instead of using pip for system-wide installation, but this is often handy when setting up container images.
So I checked whether we can update our dependencies to a newer "wheel" version, but found that CaPyCli doesn't use "wheel" at all, so I think we can simply drop this dependency completely.
When trying to install CaPyCli system-wide on Debian Trixie, it fails due to a conflict of the old, pinned "wheel" dependency of CaPyCli with the "wheel" version pre-installed on Debian's Python:
Yes, I know, I should install in a venv instead of using pip for system-wide installation, but this is often handy when setting up container images.
So I checked whether we can update our dependencies to a newer "wheel" version, but found that CaPyCli doesn't use "wheel" at all, so I think we can simply drop this dependency completely.