-
-
Notifications
You must be signed in to change notification settings - Fork 298
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
Please reactivate gnu:zile-master #828
Comments
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/fixing-a-hydra-build-of-a-gnu-project/10389/1 |
I've re-enabled https://hydra.nixos.org/jobset/gnu/zile-master. What do you mean by 'replace it with "vala"'? Add a new |
@edolstra Many thanks! Exactly, a new "zile-vala" jobset would be great, and there's no need for "zile-branch-2.4" any more. |
I've added https://hydra.nixos.org/jobset/gnu/zile-vala. It currently fails though: https://hydra.nixos.org/eval/1634155. Looks like some dependencies need to be updated. BTW the jobsets currently still use Nixpkgs 18.09, maybe it helps if we switch to 20.09. |
Thank you very much. It would be great if you could switch both jobsets to "latest stable", if that's possible. The Vala branch won't work until the future, because it requires an unreleased version of valac. |
I've changed them both to 20.09. Unfortunately we don't have a way to have a jobset use latest stable at the moment. |
Many thanks, I guess I'll need to get the Vala one updated eventually, or change the build recipe to install a sufficiently new valac; but it doesn't matter for now. Feel free to close this issue, and many thanks for your help! |
@edolstra: the build appears not to be working because of a nixos error:
https://hydra.nixos.org/jobset/gnu/zile-master#tabs-errors (Same on the |
Currently it's building on branch-2.4, which was correct, but development has moved back to master.
It would also be good if possible to disable "branch-2.4" and replace it with "vala".
The text was updated successfully, but these errors were encountered: