-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Mingw - part 2 #134
Mingw - part 2 #134
Conversation
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 ( |
{% if cross_target_platform.startswith("win-") %} | ||
{% set runtime_suffix = "" %} | ||
{% else %} | ||
{% set runtime_suffix = "-ng" %} |
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.
Longterm it would be nice to get rid of the runtime suffix everywhere; the last respective linux builds are:
- libgcc: 5.2.0 (Aug. 2018)
- libgfortran: 3.0.0 (Aug. 2018)
- libstdcxx: never published for linux
This should be fixable with some simple run-constraints (plus keeping -ng
as a wrapper until we've switched over the strong run-exports for maybe a few years).
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:
|
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 ( |
Re d875cfd, I don't think we need to work around the smithy bug. If the red X here bothers you, we should just cut a new smithy release (I didn't push for one because of other nearly finished PRs and not considering it very urgent). |
Thanks. It'd be good to have a new release. I would've ignored a false positive, but this was failing conda-smithy, so I have to run conda-smithy locally every time. |
Hi! This is the friendly conda-forge automerge bot! I considered the following status checks when analyzing this PR:
Thus the PR was passing and merged! Have a great day! |
Hi! This is the friendly conda-forge automerge bot! Commits were made to this PR after the |
Hi! This is the friendly conda-forge automerge bot! Commits were made to this PR after the |
…nda-forge-pinning 2024.05.13.13.50.55
…nda-forge-pinning 2024.05.13.13.50.55
…nda-forge-pinning 2024.05.13.13.50.55
…nda-forge-pinning 2024.06.10.23.22.33
It should just fail the linter, not the rerender? |
Yes, I meant the linter. |
Hi! This is the friendly conda-forge automerge bot! Commits were made to this PR after the |
GCC server looks like it's down. https://gcc.gnu.org/pipermail/gcc/ is affected too. |
@conda-forge-admin, rerender.