package rename issues with msgpack 0.5.0

[ThomasWaldmann]

borgbackup/borg#3515

I've seen the transition package you've made, but somehow it seems to not work as expected (or at least not for everybody).

[methane]

Have you seen this?

[methane]

I'm considering msgpack-python 0.5.0.1 which is clone of msgpack 0.5.
Both packages have same content, and installed later will overwrite others.

[jfolz]

pypa/pip/issues/4961

[ThomasWaldmann]

@methane no, but thanks for pointing to that. the problem is just that a lot of users do not intend to upgrade msgpack, they just intend to upgrade borg (in our case). So they'll maybe read borg upgrade notes, but not msgpack's. Let's hope the clone idea works.

[methane]

I released msgpack and msgpack-python 0.5.1.
msgpack-python is clone of msgpack this time.

[ThomasWaldmann]

I can confirm that with 0.5.1 pip install -U now works as expected and does not cause an ImportError later due to missing files. Thanks!