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
Staging next #64892
Merged
Merged
Staging next #64892
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This avoids dumping -Wall warnings when they appear in framework headers. As a result, we are closer to how regular headers are included (via -isystem). Also remove ccIncludeFlag lookup, this was unused & not very useful.
Bug in tests. See pytest-dev/pytest#3460
Some tests fail according to PyPy docs: http://doc.pypy.org/en/latest/faq.html#should-i-install-numpy-or-numpypy
CoreFoundation is included by the stdenv, moving the decision of what version should be used there makes it possible to override it entirely rather then prepending flags like cf-private does which can be unreliable.
The only remaining use-case for cf-private are symbols that are not available in the opensource build. This generally solved the problem because of it's setup-hook.
Update distutils patch to the upstream changes. See: python/cpython@6c0e0d1
Hydra nixpkgs: ?compare=1530372
The archive that was used turned out to be incorrect. yaml/pyyaml#320 By now a correct tarball has been uploaded but in order to prevent issues like these we fetch now instead from GitHub.
vcunat
requested review from
Ericson2314,
FRidh,
matthewbauer,
peti and
ttuegel
as code owners
July 16, 2019 10:41
libxkbcommon breakage on darwin: #64292 (comment) |
pyyaml 5.* is fixed, however, 3.* is broken due to the libyaml 0.2.2 bump |
vcunat
added a commit
that referenced
this pull request
Jul 16, 2019
It's not completely without regressions, but I believe we can deal with the rest directly on master. This is required for Firefox security fixes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Yet another iteration of mass rebuilds getting stabilized for master.