-
-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
logseq: fix build, move to by-name #321236
Conversation
d58fb3b
to
1ea284c
Compare
1ea284c
to
8b7d6f8
Compare
Logseq is building and working. But electron 28 reached EOL. For more information on this issue: logseq/logseq#11378 Thanks @superherointj 🥇 |
I had unpinned electron (30). But then, wegank told me to pin it to upstream. Then, it is EOL. Still the process here is correctly defined now. |
Oh, that's too bad, we're not really fixing the build as both Electrons are EOL... Electron 30 does seem preferable in this case, I think. |
But then, we're not fixing the process. And there's the issue of application not working properly still. I'd favor keeping package right. @wegank What do we do? |
I appreciate the work you're doing, @superherointj . Could this explain also logseq/logseq#10851 :
? btw, in case anyone is wondering, to allow Electron 28: nixpkgs.config.permittedInsecurePackages = [
"electron-28.3.3"
]; |
I don't use
Then test it. If it works, feel free to propose a PR pinning nodejs to 18. And explain the reasoning at Update: This answer is invalid. |
logseq: fix build, move to by-name
CC @Aman9das @bclaud
Proper fix depends on upstream: