FS#56982 - [borg] [python-msgpack] fails to start with python-msgpack 0.5.0-1

Attached to Project: Community Packages
Opened by Sebastiaan Lokhorst (lonaowna) - Saturday, 06 January 2018, 22:58 GMT
Last edited by Eli Schwartz (eschwartz) - Sunday, 07 January 2018, 21:36 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Johannes Löthberg (demize)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

After updating to python-msgpack 0.5.0-1, borg fails with the following message:

pkg_resources.DistributionNotFound: The 'msgpack-python>=0.4.6' distribution was not found and is required by borgbackup
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Sunday, 07 January 2018, 21:36 GMT
Reason for closing:  Fixed
Additional comments about closing:  python-msgpack 0.5.0-2 fixes this for all consumers, not just borg. Upstreams can migrate when they get the chance.
Comment by Alex (gotovo) - Sunday, 07 January 2018, 00:17 GMT
Previous python-msgpack version fixes the borg problem:

sudo pacman -U https://archive.archlinux.org/packages/p/python-msgpack/python-msgpack-0.4.8-2-x86_64.pkg.tar.xz
Comment by Eli Schwartz (eschwartz) - Sunday, 07 January 2018, 02:31 GMT
https://github.com/borgbackup/borg/issues/3515
Comment by Eli Schwartz (eschwartz) - Sunday, 07 January 2018, 02:33 GMT
Actually, maybe we should just package this msgpack dummy together with msgpack: https://github.com/msgpack/msgpack-python/commit/9f4c12f29ce7a6d62423311ab12a031dc79c458a
Comment by Panayotis (teras) - Sunday, 07 January 2018, 12:34 GMT
Newbie question here: The command that temporarily fixes the problem, fails with this error, please advise!

error: '/var/cache/pacman/pkg/python-msgpack-0.4.8-2-x86_64.pkg.tar.xz': package missing required signature
Comment by Alex (gotovo) - Sunday, 07 January 2018, 16:58 GMT
@teras: Maybe try refreshing the signing keys like this:

sudo pacman-key --refresh-keys

Then retry the downgrade command (pacman -U).

More info at https://wiki.archlinux.org/index.php/Pacman/Package_signing
Comment by Eli Schwartz (eschwartz) - Sunday, 07 January 2018, 17:12 GMT
It has nothing to do with the signing keys, pacman has been told to download a remote package which it wants to check for signatures, but it has found a cached version where it intended to download the package.

As a result, it doesn't bother to download the signature file (and fails when it is missing)... but you really should use pacman -U /var/cache/pacman/pkg/python-msgpack-0.4.8-2-x86_64.pkg.tar.xz instead.
Comment by Sebastiaan Lokhorst (lonaowna) - Sunday, 07 January 2018, 20:08 GMT
Fixed in python-msgpack 0.5.0-2. Thanks! :)

Loading...