Navigation Menu

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

Python packages set: patch updates #101636

Merged
merged 222 commits into from Nov 6, 2020
Merged

Python packages set: patch updates #101636

merged 222 commits into from Nov 6, 2020

Conversation

FRidh
Copy link
Member

@FRidh FRidh commented Oct 25, 2020

Motivation for this change
$ maintainers/scripts/update-python-libraries --use-pkgs-prefix --commit --target=patch pkgs/development/python-modules/**/*.nix
Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@@ -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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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

@SuperSandro2000
Copy link
Member

Did you use a script to do this? Can I find it somewhere?

@FRidh
Copy link
Member Author

FRidh commented Oct 25, 2020

@SuperSandro2000

$ maintainers/scripts/update-python-libraries --use-pkgs-prefix --commit --target=patch pkgs/development/python-modules/**/*.nix

@mweinelt
Copy link
Member

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 component-packages.nix, so I'd appreciate if you could drop them here.

@mweinelt
Copy link
Member

builder for '/nix/store/zg8jl91486n45sz196s2z3zmxs74g36m-python3.8-amply-0.1.4.drv' failed with exit code 1; last 10 log lines:
  patching script interpreter paths in /nix/store/c81cvqg9yjzhvf3ff5b25kgxwzc0g8l2-python3.8-amply-0.1.4
  checking for references to /build/ in /nix/store/c81cvqg9yjzhvf3ff5b25kgxwzc0g8l2-python3.8-amply-0.1.4...
  Executing pythonRemoveTestsDir
  Finished executing pythonRemoveTestsDir
  running install tests
  Traceback (most recent call last):
    File "tests/test_amply.py", line 4, in <module>
      import pytest
  ModuleNotFoundError: No module named 'pytest'
  builder for '/nix/store/zg8jl91486n45sz196s2z3zmxs74g36m-python3.8-amply-0.1.4.drv' failed with exit code 1

https://github.com/willu47/amply/blame/v0.1.4/tests/test_amply.py#L4

@jonringer
Copy link
Contributor

fridh, your pip reproducible patch isn't included in here. many packages are failing

@jonringer
Copy link
Contributor

jonringer commented Nov 6, 2020

@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

@jonringer jonringer mentioned this pull request Nov 6, 2020
4 tasks
@jonringer
Copy link
Contributor

this is probably more stable than master at this point

@raboof
Copy link
Member

raboof commented Nov 13, 2020

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, test/test_core.py:131 expects filenames_fingerprints to contain 5 elements, but the query at testmon/testmon_core.py:267 only selects 4.

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...

@raboof
Copy link
Member

raboof commented Nov 14, 2020

The pytest-testmon 1.0.2 -> 1.0.3 included in this change appears to fail consistently.

It seems the tests are expecting master instead of 1.0.3 (tarpas/pytest-testmon#158), let's skip them for now (#103786)

jskrzypek added a commit to jskrzypek/nixpkgs that referenced this pull request Nov 23, 2020
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.
jonringer pushed a commit that referenced this pull request Nov 24, 2020
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.
Luflosi added a commit to Luflosi/nixpkgs that referenced this pull request Feb 8, 2021
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants