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
pillow v9.0.0 #104
pillow v9.0.0 #104
Conversation
…nda-forge-pinning 2022.01.02.17.59.50
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 ( |
@conda-forge/pillow I was just wondering about the following:
should we not add the respective libraries to get support complete? Any reasons this wasn't done in the past (except perhaps unavailability of the libs in conda-forge)? I'm also thinking to try running the upstream test suite here, though this might obviously uncover some sleeping bugs and could be decoupled from the bump here. |
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.
This should now be ready in principle, however, I want to make sure we pick up any necessary changes for supporting pillow-simd (see this comment ff.) into the first builds for 9.0.0, as pillow apparently has a 18 month cadence for major releases, and having such a change at a major version boundary makes a bunch of things easier on the infra & resolver level.
Yeah. Probably. To be honest I don't remeber.
Sure. Let's go for it. I'm on a "break" from conda-forge to focus on the day job a bit so I won't work on this anytime soon but I will be happy to review/merge anything if you need me. |
@radarhere @hugovk
There's one other failure that is also a bit cryptic for me:
Note, the test suite wasn't run here until now, so it's not strictly necessary and we can also skip however many tests we want (in principle). Still, I consider it best practice to run the full test suite to verify that the packaging has gone smoothly. |
The images you mention are located at https://github.com/python-pillow/pillow-depends/tree/main/test_images We removed them from our main repository because antivirus software on users' computers was flagging them as problematic - which of course is exactly why we were testing them, but the antivirus software did not realise that the installed version of Pillow had fixes for them. In our CI, we copy these images in.
|
The The image viewers we look for on Linux are |
Thanks a lot for the quick responses. I'll try to see if I can get the extra images to run here, but if it doesn't work, we'll just skip them. For the viewers, I think the best is just to skip that one test, rather than try to shoehorn a viewer into the CI (might need yum_requirements, which I'd prefer to avoid as they could affect build time). |
73a889b
to
50f650b
Compare
The Since |
I think it would be fine for now to skip this test, WDYT? |
@radarhere, thanks a lot for the patch, the test is now passing! :) While I think this would be good enough to release, I'm still trying to get raqm packaged for conda-forge, and was wondering if we you see a chance that we figure out the failing library detection on windows:
LIBIMAGEQUANT / WEBPMUX / XCB should all be there, but it's not being picked up. |
If I run searches for imagequant.dll, when Pillow is about to be installed, it is absent. It appears in another search later on, but by then it is too late. Here is the full log. This suggests to me that the order of operations needs to be rearranged so that libimagequant is installed before Pillow, rather than after. |
8bcb7da
to
fe8a9f2
Compare
@radarhere
|
If you look further up in
|
I don't really think this is a problem with Pillow detecting files. I think this is a problem with files not being there in the first place.
|
OK, I propose to merge this as is @conda-forge/pillow. The other bindings can be improved incrementally. PS. If desired, I can clean up the commit-history. |
Fine with me.
That is fine. No need to clean it. Can you lift the "change request" so we cam merge? PS: thanks for the awesome work you did here! |
Hooray pillow 9.0.0! cleans up a number of CVEs, would be lovely to see this merged. |
@conda-forge-admin please rerender |
…nda-forge-pinning 2022.02.02.14.34.19
@conda-forge/pillow back up to ✔️ |
I guess that the "changes requested" threw me off. I usually do these reviews on mobile and I skips those that have pending things. However, it was clear that @h-vetinari was done and I missed it. Thanks again for this awesome PR @h-vetinari ! |
It is very likely that the current package version for this feedstock is out of date.
Checklist before merging this PR:
license_file
is packagedInformation about this PR:
@conda-forge-admin,
please add bot automerge
in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.bot-rerun
label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase@conda-forge-admin, please rerun bot
in a PR comment to have theconda-forge-admin
add it for you.Dependency Analysis
We couldn't run dependency analysis due to an internal error in the bot. :( Help is very welcome!
This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/autotick-bot/actions/runs/1647490976, please use this URL for debugging.