-
Notifications
You must be signed in to change notification settings - Fork 47
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
pyrodigal issues with fresh 1.8.2 conda install #255
Comments
I reinstalled with conda from scratch once more with
my command fails with:
|
Hi @splaisan, This having said, I currently do not understand why Bakta fails to recognize Pyrodigal. Could you maybe run Bakta in |
I will first thing monday and post here. I will also rebuild a conda using the new conda version which now finally uses mamba_lib to search for packages (was about time they switched). This only has fixed another issue I had this week. |
Hi @oschwengers, I tried it once more with my existing env to confirm it fails (it did) It confirms that the new conda 23.10.0 with mamba resole did build a good environment problem solved for me I reproduce here the last failed run and list of packages as well as the new list of packages in case that can help you figure out who was guilty. I strongly suspect pyrodigal 2.3 now instead of 3.10 before ! conda previous bad env
conda 23.0.1 new working env
|
You're welcome. Glad that it's now working. FYI, upcoming Bakta |
Hi,
After updating my conda env recently, bakta stopped working and complained about some dependencies version (altair V4 not found, V5 was installed during the update for some other package update).
Based on other error reports I decided to wipe my conda env and create a fresh one from scratch.
The new env now complains not finding Pyrodigal (capital P) while pyrodigal is present (v 2.3.0 installed)
pyrodigal is installed but with small case 'p'
I tried adding a Pyrodigal symlink to pyrodigal in the conda env bin folder but it still fails with
thanks for your help
The text was updated successfully, but these errors were encountered: