pyspark v3.2.2 - Githubissues

j-4 commented 2 years ago

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@dbast Please support multiple versions for this package by not merging to main, but rather creating a new branch v3.2.x where we can push these bugfix releases. The desire was also raised for v2.7.x and 3.0.x in issue #29. I can volunteer to create this branch as well! Thanks for your support!

Tasks done:

I used the same dependencies as in 3.2.1
I checked the sha512 with the website and then created the sha256 from that file

conda-forge-linter commented 2 years ago

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

dbast commented 2 years ago

there now are a main-{2.7, 3.0, 3.2} branches, please do the PRs against those branches instead of main to avoid confusing the bot doing updates. thanks

j-4 commented 2 years ago

Thanks @dbast for the quick action! I created PRs for all three branches, however the 2.4.8 does not build atm. Furthermore, the branch should be called main-2.4 instead of main-2.7. How about v3.1.3 (https://spark.apache.org/releases/spark-release-3-1-3.html) do we want to support it as well to have this complete?!

dbast commented 2 years ago

main-2.4 and main-3.1 are now created

conda-forge / pyspark-feedstock

pyspark v3.2.2 #37