Hi All,
I now observe some of the gate jobs are failing[1] because of broken pip[2], and it guess that we need to pin pip to avoid the error atm.
[1] https://81b633e2c5fe858f8400-d324a81a71d524d51ede3dc5aee27774.ssl.cf5.rackcd... [2] https://github.com/pypa/pip/issues/7217
May I ask for some help to set that pinning ? I couldn't find the correct way to pin pip after several investigation ...
Thank you, Takashi
Hi,
It seems they fixed it
https://github.com/pypa/pip/issues/7217
Eyal
On Tue, 21 Jan 2020 at 15:03, Takashi Kajinami tkajinam@redhat.com wrote:
Hi All,
I now observe some of the gate jobs are failing[1] because of broken pip[2], and it guess that we need to pin pip to avoid the error atm.
[1] https://81b633e2c5fe858f8400-d324a81a71d524d51ede3dc5aee27774.ssl.cf5.rackcd... [2] https://github.com/pypa/pip/issues/7217
May I ask for some help to set that pinning ? I couldn't find the correct way to pin pip after several investigation ...
Thank you, Takashi
--
Takashi Kajinami Software Maintenance Engineer Customer Experience and Engagement Red Hat e-mail: tkajinam@redhat.com
Looks like pip fixed itself in 20.0.1 https://pypi.org/project/pip/#history
-yoctozepto
wt., 21 sty 2020 o 14:09 Takashi Kajinami tkajinam@redhat.com napisał(a):
Hi All,
I now observe some of the gate jobs are failing[1] because of broken pip[2], and it guess that we need to pin pip to avoid the error atm.
[1] https://81b633e2c5fe858f8400-d324a81a71d524d51ede3dc5aee27774.ssl.cf5.rackcd... [2] https://github.com/pypa/pip/issues/7217
May I ask for some help to set that pinning ? I couldn't find the correct way to pin pip after several investigation ...
Thank you, Takashi
--
Takashi Kajinami Software Maintenance Engineer Customer Experience and Engagement Red Hat e-mail: tkajinam@redhat.com
participants (3)
-
Eyal B
-
Radosław Piliszek
-
Takashi Kajinami