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.

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

build_requires and private when already in graph #4937

Conversation

Projects
None yet
2 participants
@memsharded
Copy link
Contributor

commented Apr 9, 2019

Changelog: Bugfix: build-requires and private requirements that resolve to a dependency that is already in the graph won't span a new node, nor will be build-requires or private. They can conflict too.
Docs: Omit

Close #4931

@tags: slow

@ghost ghost assigned memsharded Apr 9, 2019

@ghost ghost added the stage: review label Apr 9, 2019

@memsharded memsharded added this to the 1.14.2 milestone Apr 9, 2019

@memsharded memsharded assigned lasote and unassigned memsharded Apr 9, 2019

@lasote

lasote approved these changes Apr 9, 2019

@lasote lasote closed this Apr 11, 2019

@ghost ghost removed the stage: review label Apr 11, 2019

@lasote lasote modified the milestones: 1.14.2, 1.14.3 Apr 11, 2019

@himikof himikof referenced this pull request Apr 12, 2019

Closed

Regression in private dependency handling in 1.14.3 #4970

3 of 3 tasks complete

@memsharded memsharded deleted the memsharded:fix/build_requires_conflicts branch Apr 16, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.