-
Notifications
You must be signed in to change notification settings - Fork 5
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
Fix conda version conflict #958
Comments
If we move the installation of package See the output of
|
The assumption above was incorrect. |
Inverting the order of conda installation and pinning , exasol/script-languages#451, results in a successful build.
|
Changelist: - #944: Removed exaudfclient_bin_py3 (#975) - #967: Added ctpg script options parser (#968) - #972 and #973: Refactorings for Script Options parser (#976) - #977: Fixed Trivy update cache workflow (#978) - #969: Use new CTPG parser in java vm (#970) - #980: Moved flavor template-Exasol-all-java-17 to script-languages repo (#984) - #971: Removed dead code in Java VM (#985) - Refactorings in ScriptOptions parser (#987) - #988: Adapted Java integration tests for new ScriptOptions parser (#995) - #997: Added documentation for Rollback of Script-Languages-Container (#999) - #878: Fixed jvmoption and parameters containing a space (#1001) - #1002: Use ECR fallback repository for Trivy caching (#1004) - #1006: Updated Dependencies on top of 8.4.0 (#1007) - #958: Fix conda version conflict (#1010) - #1009: Removed NVIDIA GPU Driver Libraries from template-CUDA SLC (#1012) - Bumped version to 9.0.0 (#1013) - #1014: Fixed Push Docker Test Container workflow (#1015)
Background
In exasol/script-languages#450 we removed the dependency in the cuda flavor to:
gxx_linux-64==12.4.0
gcc_linux-64==12.4.0
because the conda package
cuda-toolkit
had a newer version of both packages installed in a previous build step.We should investigate the behavior of mamba.
The text was updated successfully, but these errors were encountered: