`borg create` and other commands fail with the following traceback. The commands succeed after installing dev-python/packaging. Traceback (most recent call last): ... File "/usr/lib/python3.9/site-packages/borg/__init__.py", line 1, in <module> from packaging.version import parse as parse_version ModuleNotFoundError: No module named 'packaging'
From the changelog: "1.1.17 install_requires the “packaging” pypi package now." https://borgbackup.readthedocs.io/en/stable/changes.html#changelog
Confirmed. Without packaging, borg does not work, as stated on the website.
I can confirm this issue as well. https://github.com/borgbackup/borg/commit/65ea375968005984caee045d534bd139f3d7afda#diff-60f61ab7a8d1910d86d9fda2261620314edcae5894d5aaa236b821c7256badd7
Thanks everyone. I'll look into it.
(In reply to Thomas Arnett from comment #0) > `borg create` and other commands fail with the following traceback. The > commands succeed after installing dev-python/packaging. > > Traceback (most recent call last): > ... > File "/usr/lib/python3.9/site-packages/borg/__init__.py", line 1, in > <module> > from packaging.version import parse as parse_version > ModuleNotFoundError: No module named 'packaging' Okay as a quick fix I added dev-python/packaging to DEPEND in 1.1.17-r1. I have not determined whether distutils has been completely removed, so the ebuild might need further cleanup --- removing the distutils-r1 eclass dependency. But for the time being `borg create` works. Can anyone determine for me whether a cleaner version of the ebuild is possible, ie reducing distutils-r1 to maybe just python-r1 eclass? It would save me some time. Leave this bug open until we're done with cleaning up the ebuild.
I've determined that distutils-r1 is still required, so we're done here.
