-
-
Notifications
You must be signed in to change notification settings - Fork 15.4k
lumo 1.9.0 -> 1.10.1 plus darwin support #59414
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
Conversation
rebased and merge conflict resolved. Can this be merged @markuskowa ? |
I will have a look, once it gets updated. |
I ran into #79781 and can confirm that when using lumo from this branch it does work. Seems like this PR needs a rebase, though? |
Because of not being rebased, it will work. I'm finishing work now. I think pkgs.clojure needs a patch or older version provided. Will update in ~2 hours. |
the branch is rebased now, but and the bug is there. Will try few things out, starting with simplest solutions. |
The problem seems to be purely due to clojure, adding this check to interpreters/clojure/default.nix
causes
I think the best way to solve it is by providing the clojure binary an environment where it has access to all its runtime jar deps. This is easy to do, and they do provide deps.edn which clojure reads from on each invocation. |
after #79868 gets merged, Lumo should work fine, with or without this bump (tough I'd love to see this merged since it's been stale for almost a year). |
@@ -363,7 +354,7 @@ let | |||
|
|||
npm ${forceOfflineFlag} --nodedir=${nodeSources} ${npmFlags} ${stdenv.lib.optionalString production "--production"} rebuild | |||
|
|||
if [ "''${dontNpmInstall-}" != "1" ] | |||
if [ "$dontNpmInstall" != "1" ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should stay!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no recollection from this change. Most likely the generated data from 1.6.1. You mean this should stay, the change or the original? (I assume the original, in which case regenerating with right version should fix it).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is a bug in node2nix itself: svanderburg/node2nix#174
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to keep the current line.
@@ -1,4 +1,4 @@ | |||
# This file has been generated by node2nix 1.7.0. Do not edit! | |||
# This file has been generated by node2nix 1.6.1. Do not edit! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is weird that this was now regenerated using an older version of node2nix. Did you generated it from an up-to-date nixpkgs repository?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah, yes I have older version managed by npm -g, I should ofc install it via nix (but there were some bugs fixed upstream that I needed for something sometime).
Will fix after work
@Mic92 I finally got around fixing the comments, the build was also failing, for the same reason the current Lumo build is failing. So I added 2 extra patches and the build goes trough. It would be nice if this could ship with the next release, because as far as I see, Lumo would otherwise get a broken status. I guess for that I'd need to change base? |
branch is still working for me 😄 👍 |
Motivation for this change
New release, also some requests for adding darwin support which I implemented by adding two missing buildDependencies.
Things done
Removed and added some npm packages, rebuilt the node10 packages files. Tested in on my linux and on MacOs Sierra in VirtualBox.
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)