staging-next 2023-08-22 #250778
Merged
staging-next 2023-08-22 #250778
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
...into staging
...into staging
Co-authored-by: K900 <me@0upti.me>
Co-authored-by: K900 <me@0upti.me>
Co-authored-by: K900 <me@0upti.me>
Upstream's recommended "python -m build" way of invoking build fails when the working directory contains a file named "build.py". This is common for poetry projects that build C extensions.
… own file As we continue iterating on Python infrastructure for Python 3, some code is starting to diverge for Python 2. If we copy the current state of mk-python-derivation.nix and freeze it for Python 2, we can iterate on it for Python 3 with more freedom.
While installer is built using bootstrap packages, none of its test dependencies should be, so we must move out of the derivation.
While pyproject-hooks is built using bootstrap packages, none of its test dependencies should be, so we must move out of the derivation.
While build is built using bootstrap packages, none of its test dependencies should be, so we must move out of the derivation.
…s and wheel We can do this automatically for packages we know cannot use the conflict check hook when it would lead to infinite recursion.
The usage of wheel should be restricted to the hook. I discovered this when trying to remove wheel from the Python bootstrap. Some packages that needed wheel did not need it added explicitly because they use this hook. This implicit change to the dependency tree shouldn't happen (even though it is mostly harmless).
In this new version of wheel, the build backend changed from setuptools to flit-core. This is nice because it breaks a cycle between setuptools and wheel.
Co-authored-by: adisbladis <adisbladis@gmail.com>
We need to clarify these or else the wrong build system gets added and we find ourselves with an infinite recursion.
This version update is needed to be compatible with pip 23.2.
12 tasks
python310Packages.patool: fix tests to be compatible with file 5.45
12 tasks
glog: disable logging tests on aarch64-darwin
12 tasks
12 tasks
12 tasks
12 tasks
12 tasks
molecule: add missing build dependencies
python310Packages.vega: fully switch to poetry-core
python310Packages.opentsne: add missing build dependencies
python310Packages.typecode: disable tests that fail against file 5.45
python310Packages.fe25519: remove patch leftover from merge
[staging-next] python3Packages.python3-saml: skip (more) tests with expired test data
|
This seems to have broken tpm2-pytss, see #252023 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Helpful links
https://hydra.nixos.org/job/nixpkgs/staging-next/unstable#tabs-constituents
https://hydra.nixos.org/job/nixos/staging-next-small/tested
https://hydra.nixos.org/jobset/nixpkgs/staging-next
https://hydra.nixos.org/jobset/nixos/staging-next-small
Mass breakages
(will be edited based on progress)