-
-
Notifications
You must be signed in to change notification settings - Fork 15.5k
staging-next: another iteration #56200
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
Conversation
lzma is part of the stdenv but not during bootstrapping?
... into staging-next.
See cherrypy/cherrypy#1306 for the upstream discussion.
@@ -14,24 +15,35 @@ buildPythonPackage rec { | |||
|
|||
CXXFLAGS = stdenv.lib.optionalString stdenv.cc.isClang "-std=c++11"; | |||
|
|||
nativeBuildInputs = [ | |||
gdal # for gdal-config |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@FRidh Just wanted to let you know that I believe this is a situation where a package needs to be in nativeBuildInputs
as well as buildInputs
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably yes. gdal-config
requires it to be in nativeBuildInputs
, but we also build against it so also in buildInputs
.
Python failure of |
and cleanup broken tests
Fixes several broken python packages for python-unstable
This won't magically be ready in the next hour, will it? :/ I guess we'll have to rebase it into the release branch after the fact. :( |
I think this can go in. Aarch64 is currently broken, but that can be fixed up. |
@vcunat @lheckemann how to proceed to get this into |
I've merged staging-next into both master and staging-19.03. |
This might be the last iteration before forking 19.03, so let me /cc @lheckemann.