opened
jakirkham
username_0
Previously this script was able to update recipes with outdated pins. However, fixes made to the script to avoid partial dependency name matches, have had an adverse effect on updating outdated dependency pinnings. A simple fix would be to just split the pinning from the dependency's name and compare the name alone as we do here. This should still avoid partial name matches, but should also update old dependency pins. There are some subtle pinnings that we don't handle with this strategy. That being said, we haven't tended to use those particular forms of pinnings yet. If we do, we might want to take a closer look at `conda` or `conda-build` to find something more robust for this sort of parsing and comparison.

cc @krischer @username_1

xref: https://github.com/conda-forge/conda-forge.github.io/commit/483127828ea72dd4e7ed4def7a3c13211762171b#commitcomment-20474240
Update outdated pins
issue
created
jakirkham
username_0
Like the one mentioned in this [comment]( https://github.com/conda-forge/conda-forge.github.io/commit/483127828ea72dd4e7ed4def7a3c13211762171b#commitcomment-20498340 )? I'm not sure. If you know how to fix it, I'd be happy to try something. TBH though I'm not really sure what that is doing for us.
comment
created
croth1
username_1
The change should help us in this contrived example: let's say a package depends on boost and boost-cpp

```
- boost-cpp 1.63.*
- boost
```

our previous updating would've replaced the first hit of `- boost` by the pinned version which would've resulted in this:

```
- boost 1.63.*-cpp 1.63.*
- boost
```

But now that I spent more time thinking about it, I think it will fail to recognize the update if a line ends with a selector and/or comment.
comment
created
jakirkham
username_0
Superceded by PR ( https://github.com/conda-forge/conda-forge.github.io/pull/442 ). Thanks @jschueller.
comment