-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
declare libjpeg dep #19
Conversation
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe:
|
@conda-forge-admin please rerender |
…nda-forge-pinning 2023.03.29.16.02.14
The linter failure is expected, due to open bug: conda-forge/conda-smithy#1726. |
@conda-forge-admin please rerender |
…nda-forge-pinning 2023.03.29.16.02.14
Seeing clobber warnings both from this build (seems like vendoring deps) and from |
@conda-forge-admin please rerender |
…nda-forge-pinning 2023.03.29.16.02.14
@conda-forge-admin please rerender |
…nda-forge-pinning 2023.03.29.16.02.14
copy in the migration file for jpeg9->jpeg turbo. it adds a stricter pin on turbo with the exclusion |
The transition isn't super easy... yet, see final point conda-forge/conda-forge.github.io#673 (comment) |
@conda-forge-admin please rerender |
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/r-cairo-feedstock/actions/runs/4612439208. |
@hmaarrfk thanks for the quick reply! Where should I copy it to? I tried |
Try: mfansler#1 |
lets see what happens in #20 |
Adds explicitly
libjpeg
dependency. Sincer-base=4.1
has not yet migrated, we split the declaration via variants.Checklist
conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)Partially addresses #18.