Closed idot closed 1 year ago
Thanks for reporting this!
I was not able to reproduce on my end. Can you please activate a conda environment with quarto installed and report the result of env | grep QUARTO
? I suspect this envvar is not be set in your conda environment and is therefore being calculated by the run script.
On my machine:
$ env | grep QUARTO
...
QUARTO_DENO=/home/me/.local/share/miniconda3/envs/quarto-test-29/bin/deno
...
On your machine, these vars should be set at /users/ido.tamir/.conda/envs/mamba/envs/bioinfo/etc/conda/activate.d/quarto.sh
I think I see a potential cause. /users/ido.tamir/.conda/envs/mamba/envs/bioinfo
This doesn't look right to me. mamba
should be installed in your base
conda environment, not in its own dedicated environment.
The mamba install docs provide good instructions. However, they strongly recommend against installing mamba
into a pre-existing conda install, I believe because it's easy to get in to this situation. Especially important note from that page: Installing mamba into any other environment than base is not supported.
Please let us know if we can close this issue or if you continue to experience issues after fixing the mamba
installation.
Dear Matt, thank you very much for your help. You can close this issue.
best, ido
My pleasure, Ido, thanks for taking the time to report!
Solution to issue cannot be found in the documentation.
Issue
Installing with conda both on a real computer and Singularity deno is not found when executing quarto. The script quarto expects deno in the wrong place. It is installed right there next to the quarto script. Hardcoding the deno path in line 158 fixes the problem (but is of course not what conda needs as a script).
real computer
Singularity:
Installed packages
Environment info