[Slackbuilds-users] borgbackup msgpack-python problem

Andrzej Telszewski atelszewski at gmail.com
Sun Dec 9 09:01:34 UTC 2018


On 06/12/2018 18:53, Audrius Kažukauskas wrote:
> On Wed, 2018-12-05 at 17:42:27 -0800, David O'Shaughnessy wrote:
>> I'm having trouble with borgbackup on 14.2_64. Here's the error message
>> upon running borg init .
> <...>
>>> 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>
>>
>> I've tried uninstalling and reinstalling borgbackup and all
>> dependencies, but no luck yet. The msgpack-python installed is 0.5.6, so
>> that should be ok?
> 
> I was hit by this as well a week or two ago, but was too tired and
> annoyed to investigate the root of this issue, so what I've done was a
> stupid, yet effective workaround -- I commented out msgpack-python line
> in /usr/lib64/python3.6/site-packages/borgbackup-1.1.7-py3.6.egg-info/requires.txt
> file and things were functional again.
> 
> But now I got curious and looked around a bit.  Here's what I dug up:
> the problem here is that borgbackup requires msgpack-python while
> upstream of the latter switched its name to msgpack (without -python
> suffix).  borgbackup devs are aware of this change and will fix it
> eventually (if they haven't already), but what we can do right now is
> add the following to borgbackup.SlackBuild somewhere before the line
> that calls 'python3 setup.py install':
> 
>    sed -i 's/msgpack-python/msgpack/' setup.py
> 

I've just pushed an updated version.
Unfortunately, upstream have not yet fixed the problem.

All this being said, I included a patch to fix the msgpack rename problem.

In my limited testing, borg works as expected again.

Thanks Audrius for the hint.

-- 
Best regards / Pozdrawiam,
Andrzej Telszewski


More information about the SlackBuilds-users mailing list