-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Ovito is broken [no Qt] #53421
Comments
This one is a common problem (#24256). A workaround, that I usually use, is to do |
@HaoZeke thank you for raising this issue. I was the one that packaged ovito for nixpkgs #46846. I wish that ovito was built on hydra but it was stated that it takes too long to builld. Hopefully this changes with enough people voicing that they need the package. I could not reproduce the issue that you had meaning that it most likely is the issue stated above with qt.
I ran on commit |
Thanks for packaging it! @costrouc. However I made a bit of a mistake in my bug report. The bug is when the package is run in a pure environment. Namely, the error is when you do: nix-shell -p ovito --pure The fix is also correspondingly trivial, I will add a pull request to get the exact dependencies listed. |
@verprbl I can't seem to run that command. nix-env -iA qt5.qtcore
error: attribute 'qt5' in selection path 'qt5.qtcore' not found |
@HaoZeke Sorry, I meant |
In that case, the issue needs further investigation. I cannot seem to get ovito to work in a pure environment, though it does build when I install qt systemwide. |
We should be able to fix this using #54525 |
Closing as a duplicate of #42893. |
Issue description
The Ovito package
nixpkgs.python37Packages.ovito
is broken. This is likely not meant to be built in thepythonPackages
portion ofnix
in any case, and I notice it is also not meant to run on hydra.The Error
Steps to reproduce
nix-env -i ovito # Check commands above
An alternate way to reproduce this is with the following
shell.nix
file:Then simply run:
nix-shell shell.nix --run 'bash'
Technical details
The text was updated successfully, but these errors were encountered: