-
Notifications
You must be signed in to change notification settings - Fork 4
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
Problems installing wsclean #258
Comments
Thanks for the issue @JSKenyon. Can you please provide output of |
|
Somehow I cannot reproduce this error. Also make sure that the restricted and multiverse: |
I already have both of those - maybe something strange has happened. I find it odd that I ran into this on my old system too. Completely possible that the error is on my end. I already went ahead an installed from source so this isn't blocking me. Just strange that this and only this seems to give me problems. |
What error do you get if you apt-get install libwsclean2 |
|
And what happens if you install libidg0-api0 manually? Follow the trail |
Ah, it is the image domain gridding stuff. It wants cuda related dependencies. Perhaps because I have a GPU?
|
I can follow along further - just shout if you think it is needed. |
yeah please follow. it looks like it can't install nvidia drivers and cuda. is your system up-to-date using |
Looks like that last one was the problem. I manually installed |
This rings a bell. The last time I've experienced this it was solved by updating the system and clearing cache.
|
I cannot really say. I do know that installation failed literally just after I did a fresh Ubuntu install, so I wouldn't have thought there could be any state to cause problems. |
I can confirm this is still a problem @gijzelaerr @Athanaseus.
Why is there a hard dependency on |
This is due to the hard dependency on |
Yes please! |
i just tried this in a fresh focal linux/amd64 docker container, and I can't replicate this issue (kern-7 wsclean and ids install, nvidia libs install from multiverse). Please make sure you have:
|
Does your container have/see a GPU? I suspect that that is the crucial point. |
The packages should install without issues even if you dont have a Cuda
card installed.
On Mon, 15 Aug 2022 at 13:27, JSKenyon ***@***.***> wrote:
i just tried this in a fresh focal linux/amd64 docker container, and I
can't replicate this issue (kern-7 wsclean and ids install, nvidia libs
install from multiverse).
Please make sure you have:
* restricted and multiverse repo enabled
* run apt-get update before you install any other packages.
Does you container have/see a GPU? I suspect that that is the crucial
point.
—
Reply to this email directly, view it on GitHub
<#258 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACPVJDMPTXHCXZ6I2IRPKLVZISRBANCNFSM5RJ74RYA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Gijs Molenaar
http://pythonic.nl
|
@gijzelaerr on nodes without a GPU, there is no issue because it sneakily installs |
ah yes, that makes more sense. What driver do you install how? You can't mix kernsuite with non-ubuntu GPU driver repos unless we remove the cuda depending package from kern. If you say in practice nobody uses GPU support with wsclean I guess we can just do that. |
Using the official NVIDIA repo:
There'sa bit of a wrinkle because our Tesla cards are now considered "legacy", so the driver version can't go above 470 (or CUDA above 11.4). But that's not the current problem anyway.
Not at the moment, but why not make it optional like @Athanaseus suggests? |
I think that @Athanaseus's idea was sound - make two packages. I don't think we want to completely cut off the option of using IDG with GPU support. |
ok, i think the easiest way is to just clone the https://github.com/kernsuite-debian/wsclean repo to https://github.com/kernsuite-debian/wsclean-idg and then update the packages accordingly. |
KERN-7
|
On Ubuntu 20.04 using KERN-7,
wsclean
fails to install with messages like:I have verified that I have no held packages and I believe that I ran into the same issue on my previous PopOS install.
The text was updated successfully, but these errors were encountered: