v5.9.6

[thewchan]

Checklist

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

[conda-forge-webservices]

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.

[thewchan]

@conda-forge-admin, please rerender

[thewchan]

@jakirkham here

[jakirkham]

Thanks Matt! 🙏

Could you please cherry-pick this commit ( 3e57a0c )? That should fix the macOS build failures

[thewchan]

@conda-forge-admin, please rerender

[thewchan]

@jakirkham now only failing on this pypy-win build

[jakirkham]

Thanks Matt! 🙏

Glad to see that worked 😄

Looking upstream issue ( giampaolo/psutil#2325 ) appears relevant. If so, this upstream patch might be useful to add (note that is just upstream commit giampaolo/psutil@ccdb775 rendered as a patch)

[thewchan]

@jakirkham I might need a little more handholding here I apologize; I'm not sure what exactly to do here? Do I copy and paste the code you noted as a patch? And apply just to pypy 3.9 for windows?

[jakirkham]

Yeah would just download that patch into the recipe directory, add it to this list, and commit those changes together

[thewchan]

okay I'll give it a shot

[thewchan]

@conda-forge-admin, please rerender

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/psutil-feedstock/actions/runs/7822055889.

[jakirkham]

Thanks Matt! 🙏

Added a small change below. Will add automerge so it merges after CI passes

[thewchan]

@jakirkham I added the selector because it seems every cpython build is failing but they were passing previously

[thewchan]

@jakirkham wait... never mind something else is going on here

[github-actions]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!

[jakirkham]

Going to try restarting. The error looked a little weird. Something about being unable to get the source?

[jakirkham]

Ok think I understand what is happening

Am seeing the following in the CI log:

checking file HISTORY.rst
Hunk #1 FAILED at 10.
1 out of 1 hunk FAILED

Think this means the patch is conflicting when applied. Would suggest we just drop that part of the patch as we don't need it. Have indicated the lines below

That should fix the issue

[jakirkham]

Thanks Matt! 🙏

[thewchan]

Thank YOU @jakirkham for all you help!

[jakirkham]

Happy to help 🙂