Fix pip versioning for soledad
Regarding python versioning, there's a mismatch between the debian package version for i.e. a newly built leap-mx package:
root@cat:/etc/apt/sources.list.d# apt-cache policy leap-mx
leap-mx:
Installed: 0.9.1+0~20170207164922.5631+debian.platform0.10+jessie~1.g577e403
Candidate: 0.9.1+0~20170207164922.5631+debian.platform0.10+jessie~1.g577e403
Version table:
*** 0.9.1+0~20170207164922.5631+debian.platform0.10+jessie~1.g577e403 0
999 http://deb.leap.se/gitbuildpackage/ jessie/main amd64 Packages
100 /var/lib/dpkg/status
0.9.1+0~20170118161755.55+jessie~1.gbpf8c9b9 0
999 http://deb.leap.se/experimental-platform/ jessie/main amd64 Packages
root@cat:/etc/apt/sources.list.d# pip list|grep leap.mx
leap.mx (0.8.1)
The initial groundwork is done, but for repos that produce multiple packages like soledad it needs to get fixed.
Related to #8437 (closed)