I think it was clearly explained here:
https://lists.fedoraproject.org/pipermail/devel/2012-February/162518.html
I did not do the research into this explanation - it looks like others have
though. I'm just the poor victim who's systems were trashed by this nasty
bug, which causes fedora update t
On Mar 25, 2014, at 9:29 AM, Neal Becker wrote:
> Well just to be clear then, without resolving this issue (which, IMO, is a
> bug in cpio that should be fixed) it
> is absolutely unsafe to ever use pip for non-local installs on fedora.
>
It might be because I’m still half asleep and trying t
Well just to be clear then, without resolving this issue (which, IMO, is a
bug in cpio that should be fixed) it
is absolutely unsafe to ever use pip for non-local installs on fedora.
On Tue, Mar 25, 2014 at 9:02 AM, Donald Stufft wrote:
>
> On Mar 25, 2014, at 8:52 AM, Neal Becker wrote:
>
> H
On Mar 25, 2014, at 8:52 AM, Neal Becker wrote:
> Has this critical pip issue been addressed?
>
> https://lists.fedoraproject.org/pipermail/devel/2012-February/162518.html
>
Not that i’m aware of, although it’s actually an issue where distutils and
setuptools supports
two different standards
Has this critical pip issue been addressed?
https://lists.fedoraproject.org/pipermail/devel/2012-February/162518.html
On Tue, Mar 25, 2014 at 7:10 AM, Donald Stufft wrote:
>
> On Mar 25, 2014, at 2:59 AM, Bohuslav Kabrda wrote:
>
> > - Original Message -
> >>> I would say this one htt
On Mar 25, 2014, at 2:59 AM, Bohuslav Kabrda wrote:
> - Original Message -
>>> I would say this one https://github.com/pypa/pip/issues/1351 is important
>>> for us
>>> as packagers. It makes me nervous/upset and sad altogether :-).
>>
>> Awesome, well that’s on the list for 1.6 so that
- Original Message -
> > I would say this one https://github.com/pypa/pip/issues/1351 is important
> > for us
> > as packagers. It makes me nervous/upset and sad altogether :-).
>
> Awesome, well that’s on the list for 1.6 so that should be the next feature
> release
> of pip.
Cool, thank
