FS#58974 - [borg] msgpack-python incompatible
Attached to Project:
Community Packages
Opened by Stephan Eisvogel (bsdice) - Monday, 11 June 2018, 19:15 GMT
Last edited by Eli Schwartz (eschwartz) - Tuesday, 12 June 2018, 17:23 GMT
Opened by Stephan Eisvogel (bsdice) - Monday, 11 June 2018, 19:15 GMT
Last edited by Eli Schwartz (eschwartz) - Tuesday, 12 June 2018, 17:23 GMT
|
Details
Description:
Package broken as of today's 1.1.6-1 update. # borg Traceback (most recent call last): File "/usr/bin/borg", line 6, in <module> from pkg_resources import load_entry_point File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3095, in <module> @_call_aside File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3079, in _call_aside f(*args, **kwargs) File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3108, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 570, in _build_master ws.require(__requires__) File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 888, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 774, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'msgpack-python!=0.5.0,!=0.5.1,!=0.5.2,!=0.5.3,!=0.5.4,!=0.5.5,<=0.5.6,>=0.4.6' distribution was not found and is required by borgbackup Additional info: # pacman -Q |grep msgpack python-msgpack 0.5.6-1 |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Tuesday, 12 June 2018, 17:23 GMT
Reason for closing: Fixed
Additional comments about closing: borg 1.1.6-2
Tuesday, 12 June 2018, 17:23 GMT
Reason for closing: Fixed
Additional comments about closing: borg 1.1.6-2
$ pip install msgpack-python
See also: https://github.com/borgbackup/borg/issues/3889
I am not sure where those specific versions are coming from.
borg's PKGBUILD does the following only:
sed -i "s/msgpack-python>=.*/msgpack',/g" setup.py
This is hardly critical.
So our fix no longer applied once the format of the setup.py changed again...