-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
Can we keep tag 2.4.0? Not everything works with the latest 3.x #309
Comments
The exact You can still access it there is you know what you are doing. However, there are PS: the conda-forge ecosystem is not pinned to |
Ha! Fair enough. Thanks for the quick reply. I guess it's just kind of confusing on how to get to 2.4.0...
As always, thanks for your speedy help @ocefpaf |
I personally recommend pinning to |
Okay thanks. We use https://github.com/mapbox/rasterio and it's not compatible with 3.0 yet. That's our use case anyway. I'll stick to "broken" (shudders) and hope my unit tests cover our needs. Much appreciated! |
BTW, you should not be able to install |
I actually use some gdal stuff directly so thought it best to include that as well. I was calling conda install separately as part of our build process, but maybe I just combine them a bit and use some single That seems to work much better:
Output``` Collecting package metadata: done Solving environment: done==> WARNING: A newer version of conda exists. <== Please update conda by running
Package Planenvironment location: /opt/conda added / updated specs: The following packages will be downloaded:
The following NEW packages will be INSTALLED: _libgcc_mutex pkgs/main/linux-64::_libgcc_mutex-0.1-main The following packages will be UPDATED: ca-certificates pkgs/main::ca-certificates-2019.1.23-0 --> conda-forge::ca-certificates-2019.6.16-hecc5488_0 Downloading and Extracting Packages
|
!RESOLVED!
Don't pin 2.4.0, use the latest 2.4.x by doing (more fuzzy version pinning):
conda install -y --channel conda-forge gdal=2.4
or if youre using gdal + rasterio:
conda install -y --channel conda-forge gdal=2.4 rasterio=1.0
Issue:
Conda Forge no longer has gdal tag 2.4.0. This seems like bad practice. These are deployed tags, they should remain in the registry so sub dependents don't start to fail. Lest we fall to NPM's level of package management: https://www.theregister.co.uk/2016/03/23/npm_left_pad_chaos/
Running my docker build with an updated conda:
Is there a reason why tags are unpublished?
The text was updated successfully, but these errors were encountered: