Closed stuarteberg closed 3 months ago
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 (recipe
) and found it was in an excellent condition.
@conda-forge-admin, please rerender
@conda-forge/boost Can anyone tell me why this feedstock isn't using conda-forge-pinning
to determine it's boost
version?
conda-forge-pinning
, we should all be using boost-1.82.This is because it has passed the migrator, which you merged in #119. Once the migrator is closed out, I think the global pin will be updated.
@zklaus Thank you! Jeez, I completely forgot that I did that...
I still want to remove the maxpin
constraint for libcxx
, so I'm reopening this.
~I'll also use this PR to understand a different issue: Why is our rendered feedstock using boost-1.84 instead of 1.82?~
The libcxx
maxpin
constraint shouldn't be needed any more. It makes graph-tool harder to install than necessary.Checklist
0
(if the version changed)conda-smithy
(Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)