-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
switch to new name for libgcc #25
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 ( |
LGTM @h-vetinari . I guess by virtue of libgcc being added to ignore_list for run_exports, we are all good going forward, correct? |
Which ignore-list are you talking about? 🤔 There's nothing in this PR or on main. |
Oh sorry, I was referring to conda/conda-build#5475 (comment) where they ended up adding libgcc to the ignore list for being exported so I thought this was why we could just remove -ng as we did in this case and not have to employ a workaround like |
The conda-build discussion doesn't really apply to individual feedstocks; here you'll see in the link check whether this is used or not, but libgcc is so ubiquitous on linux (basically in every environment) that it doesn't really matter if you ignore it; you'll get it in the final environment anyway. The logs on azure have been deleted in the meantime, so let's refresh. @conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-linting service. I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please try to merge or rebase with the base branch to resolve this conflict. Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug. |
…nda-forge-pinning 2024.10.24.06.12.44
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 ( |
Thanks all! 🙏 |
Following conda-forge/ctng-compilers-feedstock#148, which finished up a long-open transition. The old naming still exists as a wrapper, but it would be better not to depend on it anymore. We should also backport this to 12.0