Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Pip failed to start and download any package on ReactOS #5067

Closed
AS383 opened this issue Mar 15, 2018 · 3 comments
Closed

Pip failed to start and download any package on ReactOS #5067

AS383 opened this issue Mar 15, 2018 · 3 comments
Labels
auto-locked Outdated issues that have been locked by automation project: vendored dependency Related to a vendored dependency resolution: no action When the resolution is to not do anything

Comments

@AS383
Copy link

AS383 commented Mar 15, 2018

Description:

An issues in ReactOS bug-tracker: CORE-13775

Note: ReactOS network stack does not support async connect features (related python tests failed or wait forever). This could be a key to second problem.
@pradyunsg
Copy link
Member

@AS383 If you could bring in the relevant details here in the tracker, that would be helpful.

From what I gather, this is a bug in lockfile (which pip vendors as pip._vendor.lockfile). You should report the issue upstream. Also note that pip intends to swap the use of lockfile -- #4766.

@pradyunsg pradyunsg added S: awaiting response Waiting for a response/more information S: needs triage Issues/PRs that need to be triaged labels May 10, 2018
@AS383
Copy link
Author

AS383 commented May 11, 2018

I see, all issues are upstream.

@AS383 AS383 closed this as completed May 11, 2018
@pradyunsg pradyunsg added project: vendored dependency Related to a vendored dependency resolution: wrong project Should be reported elsewhere resolution: no action When the resolution is to not do anything and removed S: awaiting response Waiting for a response/more information S: needs triage Issues/PRs that need to be triaged resolution: wrong project Should be reported elsewhere labels May 11, 2018
@lock
Copy link

lock bot commented Jun 2, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 2, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
auto-locked Outdated issues that have been locked by automation project: vendored dependency Related to a vendored dependency resolution: no action When the resolution is to not do anything
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pradyunsg @AS383