-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
clangdev v16.0.0 #206
clangdev v16.0.0 #206
Conversation
…ForgeAutomergeUpdate
This reverts commit 0b6e049.
…nda-forge-pinning 2023.01.31.03.10.11
automerged PR by conda-forge/automerge-action
automerged PR by conda-forge/automerge-action
…nda-forge-pinning 2023.02.24.11.04.05
automerged PR by conda-forge/automerge-action
This reverts commit 856699f.
automerged PR by conda-forge/automerge-action
windows needs it too; remove bound now that output is versioned
@isuruf, I updated this a few days ago, could you PTAL if this is now in line with what you wanted? |
recipe/meta.yaml
Outdated
# only contains binaries, so we can trust the link check | ||
- zlib # [unix] |
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.
I don't understand this comment. Can you clarify?
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.
Ah, you mean the package only contains binaries.
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.
Yes, that's what I meant. How should I describe it to be less ambiguous?
8faf144
to
faf3d3f
Compare
Now that we correctly have clang-format-16 present after the jinja string concat shenanigans. This reverts commit f7fcf2e.
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.
LGTM, thanks for your help in cleaning up the link check.
There are some cloberring involved. Not sure why. |
Actually, now that I look again at the link check after 2667c1a, it looks completely different
Yeah, I guess something like c51e9b7 would have fit better into its own PR. But it looks like we're getting to the end of this. Thanks for your help! |
Well, you were the one who wanted to fix the link checks. 😄 |
I'm trying to fix things as I encounter them. Sometimes I have more time to spend, sometimes less, but mostly it ends up very incrementally. Glad we made a big leap forward now. 🙃 Anything else from your side here or is this now ready? |
Thanks |
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.Pending Dependency Version Updates
Here is a list of all the pending dependency version updates for this repo. Please double check all dependencies before merging.
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/cf-scripts/actions/runs/4453095908, please use this URL for debugging.