-
Notifications
You must be signed in to change notification settings - Fork 28
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
dammit install on bioconda #136
Comments
Hi @desmondramirez, This happens to me too sometimes. It's probably because there are A LOT of dependencies underneath. To get around, install several dependencies individually from the conda recipe for dammit, then try installing dammit with bioconda again.
Then:
Hope this helps! |
Thanks for the tip! I'm trying it right now-- still solving the environment for dammit, fingers crossed. I have never been able to get BUSCO installed through bioconda, I wonder if that's what's causing the biggest issue on my end. |
Hmm, interesting. Perhaps try installing the specific version of BUSCO separately?
|
Hi, An update-- BUSCO indeed caused the long delay. I think if you install BUSCO first and then dammit that you might not even have to install the other packages by hand. In any case, I did get it install, and will try it out soon. Thanks so much for your help! |
Hi, I tried all the suggestions here getting all dependencies individually. But it was running for hours in the solving environment. Then I tried installing specific version of BUSCO separately and it also was running overnight only in the solving environment step. Any more ideas that I can try? @ljcohen @desmondramirez Thank you, Gurlaz |
@Gurlaz, can you install other packages with conda in general? I had to leave BUSCO solving the environment at least overnight. For most of the others that @ljcohen listed to install individually, they all took less than an hour, except dammit itself, which also took a good bit of time. If you have the luxury of just letting BUSCO try to solve the environment for even longer, it might just need a little bit more time than overnight. If you can get everything else besides BUSCO, you might be able to install BUSCO yourself (not using conda) in the same directory that all the other databases get installed to. |
I also tried pip installation. It seemed that installation ran fine but when I tried to test if dammit works I got following error:
|
Conda is working for me in general. I will try BUSCO again now. |
I struggled with this error for a while as well and of course I forgot to write down how I solved it. I think getting all of the packages installed resolved the issue. If I remember what I did or find a record, I'll let you know. |
Hi, Conda did not work for me for dammit or the BUSCO. However, following version specific pip installation worked and I can use dammit now.
Thanks! Gurlaz |
Hi all. Sorry for the long delay! Updates to bioconda over the summer, and some fixes to dammit pinnings, should make the install go a lot faster now. Current version on bioconda is v1.2. |
Hi,
I'm trying to install dammit using bioconda but conda hangs on solving the environment-- I left it overnight and it hadn't progressed. I tried to install dammit with pip but got an error about not being able to load module log.
Any ideas?
Thanks,
Des
The text was updated successfully, but these errors were encountered: