-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
ROOT Nightly seems out-of-date #241
Comments
Dear @will-cern, Thanks for the report, and for actively using the nightly package! By its nature it is a bit unstable and since it runs on a best effort basis I try to keep it updated as often as possible but sometimes the failures drag for longer than ideal. I have just finished a few conda-build debugging sessions and the nightly package should be back again online for use. Let me know if it works for you too. I have a plan to make the package more stable, hopefully in the future there will be less interruptions. Clearly, the official ROOT releases on conda are less prone to these instabilities 👍 |
Thanks for looking into it. Should it be updating daily? It seems to be stuck on a version from May 9th at the moment. |
Hullo, Just wondering if there's been an update on this one? Thanks |
Hi! No update unfortunately, the conda build system is quite complicated and needs constant care. Right now I am busy with the official ROOT releases (open PR for 6.32.00 which will have to be followed by another for 6.32.02). I hope in a couple of weeks to be able to resume the work on the nightlies, I would like to automate this a bit through github actions, you can see a first attempt at https://github.com/root-project/root-conda-nightly. |
Solution to issue cannot be found in the documentation.
Issue
Hello,
I was following the instructions @ https://root.cern/install/nightlies/#conda-package to setup the root-nightly, but the version I get seems to have the following commit hash and date:
Has something happened to stop the nightly being updated?
Thanks
Will
Installed packages
Environment info
The text was updated successfully, but these errors were encountered: