issue_comments: 263244991
This data as json
| html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| https://github.com/pydata/xarray/pull/1134#issuecomment-263244991 | https://api.github.com/repos/pydata/xarray/issues/1134 | 263244991 | MDEyOklzc3VlQ29tbWVudDI2MzI0NDk5MQ== | 950575 | 2016-11-28T11:11:24Z | 2016-11-28T11:11:24Z | CONTRIBUTOR | TL;DR you may consider making this change permanent. @fmaussion the problem is that latest conda-forge's hdf4 does ship with libmfhdf.so.0 but either defaults' version does not or an old version in conda-forge is broken. (I am traveling but I'll confirm that as soon as I get back.) Adding hdf4 at the env creation forces the solver to get the latest version/build number and prevented the downgrade in the subsequent conda install call. So you should probably leave hdf4 there even if it is over specifying deps because the issue may resurface. I say that b/c, if the bad version is in conda-forge we can remove it. But if it is in defaults we have no control. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
191822204 |