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
Python packages set: patch updates #101636
Conversation
@@ -13,11 +13,11 @@ | |||
|
|||
buildPythonPackage rec { | |||
pname = "boto3"; | |||
version = "1.15.9"; # N.B: if you change this, change botocore too | |||
version = "1.15.18"; # N.B: if you change this, change botocore too |
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.
version = "1.15.18"; # N.B: if you change this, change botocore too | |
version = "1.15.18"; # N.B: if you change this, change boto3 and awscli to a matching version |
Did you use a script to do this? Can I find it somewhere? |
|
84fefff
to
bdc6028
Compare
The zipgy updates collide with #101557 and I'd like the maintainer to work on test integration in that pull request. They also require an update to home-assistants |
https://github.com/willu47/amply/blame/v0.1.4/tests/test_amply.py#L4 |
bdc6028
to
7a753df
Compare
fridh, your pip reproducible patch isn't included in here. many packages are failing |
eba59fc
to
fb67994
Compare
@FRidh I rebased this on top of the latest to bringing your fixes for builds affected by the pip reproducibility patch. Unfortunately, I'm still affected by OpenMathLib/OpenBLAS#2970 and unable to build numpy (without disabling tests). So, I'll need to wait for hydra to build it for me to progress much further EDIT: actually, I'll just disable numpy tests locally and continue on with stabilizing |
this is probably more stable than master at this point |
The pytest-testmon 1.0.2 -> 1.0.3 included in this change appears to fail consistently. I'm no python programmer, but indeed looking at the PyPI package, I don't see any tests in the source repo at https://github.com/tarpas/pytest-testmon, though, so it's unclear to me where these tests actually come from... |
It seems the tests are expecting master instead of 1.0.3 (tarpas/pytest-testmon#158), let's skip them for now (#103786) |
Pyspark switched to pinning py4j==0.10.9 with v3.0.0 - see this commit: https://github.com/apache/spark/\ commit/fc4e56a54c15e20baf085e6061d3d83f5ce1185d This meant that since the bump to pyspark v3.0.0 - in this commit: https://github.com/NixOS/nixpkgs/\ commit/5181547ae6624b462919a806c4d0888e6e4630f4 - the patch was no longer matching on the 'py4j==0.10.7' string that was working previously. The failing patch went unnoticed previously because the version of py4j pinned by pyspark>=3.0.0 was the same as the py4j provided by nixpkgs. However, a recent PR (NixOS#101636) bumped the version of py4j to 0.10.9.1 in this commit: https://github.com/NixOS/nixpkgs/\ commit/43a91282d66223c5cb978d53fbe1033f56dd7f2b which caused the version pinned by pyspark to no longer match the version provided by nixpkgs. FWIW, @jonringer flagged this issue on another PR that tried to bump py4j: NixOS#100623. My solution here was to upgrade the patch's target string to match the version found in pyspark's current setup.py.
Pyspark switched to pinning py4j==0.10.9 with v3.0.0 - see this commit: https://github.com/apache/spark/\ commit/fc4e56a54c15e20baf085e6061d3d83f5ce1185d This meant that since the bump to pyspark v3.0.0 - in this commit: https://github.com/NixOS/nixpkgs/\ commit/5181547ae6624b462919a806c4d0888e6e4630f4 - the patch was no longer matching on the 'py4j==0.10.7' string that was working previously. The failing patch went unnoticed previously because the version of py4j pinned by pyspark>=3.0.0 was the same as the py4j provided by nixpkgs. However, a recent PR (#101636) bumped the version of py4j to 0.10.9.1 in this commit: https://github.com/NixOS/nixpkgs/\ commit/43a91282d66223c5cb978d53fbe1033f56dd7f2b which caused the version pinned by pyspark to no longer match the version provided by nixpkgs. FWIW, @jonringer flagged this issue on another PR that tried to bump py4j: #100623. My solution here was to upgrade the patch's target string to match the version found in pyspark's current setup.py.
This was marked broken in NixOS#101636, which was merged into the staging branch. Later, the package was updated and fixed in NixOS#101801. When the staging branch was then merged into master, the package was marked as broken while actually being fixed.
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)