No possibility to update virtualenv version in infra
Bug #1293591 reported by
Maksym Iarmak
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MagnetoDB |
Fix Released
|
Medium
|
Maksym Iarmak | ||
Bug Description
On the infra side the virtualenv version is 1.10.1:
https:/
He have in dependencies cassandra-driver. In its turn it has its own dependence blist, that needs setuptools version 1.1.6 or later.
But setuptools 0.9.8 version is used in current infra virtualenv. The best solution of this issue was updating virtualenv to newer version, but 1.11 will not work because of https:/
We have temporary solution here:
https:/
But we need to know, what solution can be from the infra side in such case.
Revision history for this message
| Maksym Iarmak (miarmak) wrote | #1 |
| Changed in magnetodb: | |
| milestone: | none → next |
| status: | New → Confirmed |
| Changed in magnetodb: | |
| status: | Confirmed → Fix Released |
| milestone: | next → 2.0.5 |
| Changed in magnetodb: | |
| assignee: | nobody → Maksym Iarmak (miarmak) |
To post a comment you must log in.
Updates:
Infra pinned that because of https:/
They are planning to revert https:/
So, it's mostly in the hands of the tox developers now to either decide they're okay with proposed fix or come up with an alternate solution.
Thanks to fungi (Jeremy Stanley) for his help from infra's side.
Btw, as a short-term workaround he suggested to use earlier version of that package (blist) which doesn't depend on newer setuptools. It is exactly as achudnovets suggested in his temp fix.