-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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.
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
cherry-pick PR #3406 for v1.1 #4241
Conversation
Add PyPI registry correctly to pool depending on other sources (#3406) In the event where we defined sources that were set as secondary = True, we would end up with PyPI being after this source when it should have acted as default in that case. The main issue stems from the fact that it's not because you have sources configured that PyPI should not be a default. Instead, PyPI should be default if there are no sources with secondary = False and not default if there are sources with secondary = True.
It's not clear to me why the CI fails with
Seems like the random error from #3010. The tests seem to work fine locally. |
@sdispater Since you merged the original PR, could you have a look at this cherry-pick for v1.1? Thanks a lot! |
Kudos, SonarCloud Quality Gate passed! |
@jstriebel approving and merging this one. However, please note that we do not at present have a plan for another |
But it is a broken feature, shouldn't broken features be patched? Especially for those who won't upgrade to the next major/minor? PS: Not pushing a patch for this bug is a minor mistake |
@abn Thanks for merging!
Understandable, however it would be very useful, especially considering that |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This cherry-picks #3406 for v1.1 for a new patch-release. From the original PR:
Pull Request Check List
Related to PR #3406, resolves #2339, resolves #3306, resolves #3238 for v1.1