Update to 1.2.6 - Githubissues

E3SM-Project / e3sm-unified

A metapackage for a unified anaconda environment for analyzing results from the Energy Exascale Earth System Model (E3SM).

BSD 3-Clause "New" or "Revised" License

8 stars 8 forks source link

Update to 1.2.6 #52

Closed xylar closed 5 years ago

xylar commented 5 years ago

Update packages for v1.2.6

Package changes

main packages:

e3sm_diags - 1.6.1 (py2), 1.7.1 (py3)
geometric_features - 0.1.1
mpas-analysis - 1.2.4
mpas_tools - 0.0.3
nco - 4.8.1
zstash - 0.2.0 (py2), 0.3.0 (py3)
processflow - 2.2.1 (py2)

dependencies:

output_viewer - 1.3.0
xarray - 0.11.3 (py2), 0.12.3 (py3)
dask - 2.1.0
pyproj - >=1.9.6,<2.0.0
proj4 - >=5.2.0,<6.0.0
hdf5 - 1.10.5
netcdf4 - 1.5.1.2
jigsaw - nospec
metis - nospec
pyflann - nospec
scikit-image - nospec
pyamg - nospec
ffmpeg - nospec

processflow has been moved to its own separate environment because of incompatibilities between ncl and basemap, see #51

closes #51

xylar commented 5 years ago

@rpwagner, looks like CI is failing because we've lost our access token. Care to take a look? This version of e3sm-unified is a long way from ready, so no rush.

xylar commented 5 years ago

Not ready to merge until #51 gets addressed.

rpwagner commented 5 years ago

It's failing due to a chicken and egg problem:

Solving environment: ...working... failed
PackagesNotFoundError: The following packages are not available from current channels:
  - e3sm-unified=1.2.6

I was thinking about this, and the definition file for CI shouldn't have a pinned version. That doesn't make sense. We can pin versions for releases.

xylar commented 5 years ago

@rpwagner, I see. I should have realized that the current source code isn't being used to build the package that goes into the module. I think unpinning the version is probably not a good idea, since it would likely give the misimpression that the current recipe for the conda package is building in CI, which is not the case. Instead, I think the right solution is to leave the version pinned at 1.2.5 for now and update it once the packages have been uploaded to the e3sm channel.

Thanks for the help!

xylar commented 5 years ago

@rpwagner, just FYI, the new container seems to have built successfully now that I uploaded the packages to the e3sm channel.