-
-
Notifications
You must be signed in to change notification settings - Fork 15.2k
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
[23.11] logseq 0.9.20 -> 0.10.6 #285583
[23.11] logseq 0.9.20 -> 0.10.6 #285583
Conversation
https://github.com/logseq/logseq/releases/tag/0.10.0 (cherry picked from commit d4f0515)
https://github.com/logseq/logseq/releases/tag/0.10.1 (cherry picked from commit 9df6d12)
https://github.com/logseq/logseq/releases/tag/0.10.3 (cherry picked from commit 733f8a3)
https://github.com/logseq/logseq/releases/tag/0.10.4 (cherry picked from commit fda9be3)
https://github.com/logseq/logseq/releases/tag/0.10.5 (cherry picked from commit 9b95e75)
@GrahamcOfBorg build logseq |
FYI logseq 0.10.6 is now released and available in unstable (#286593). |
(cherry picked from commit 28ad44d)
Thx, also includng a backport for #286593 now. |
I noted some graphics accelleration error messages in the logs when starting logseq-0.10.6, but the application itself works fine.
Unfortunately that seems to be a common Electron thing (especially with bundles), see #270699. An |
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/prs-already-reviewed/2617/1451 |
@schmittlauch I had the same messages in terminal after updating my 23.11 system while the logseq package stayed the same (0.10.5 from unstable), but only on the first start of logseq after the update. When i updated logseq from unstable, i did not see the messages again. So it seem rather related to system components than logseq itself. Full log
And the application did also work for we without additional errors despite the messages. I did not have to remove anything manually. Maybe the cache is cleared on the next start automatically. The only issues i noticed when updating from 0.10.5 to .6 was logseq/logseq#11042 and logseq/logseq#3373, but the developers say the right sidebar is not supposed to be persistent. I might do a test of 0.9.20 -> 0.10.6 later. |
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.
Change looks good
I downgraded the package to the versions of NixOS 23.05 (0.9.6) and updated to 23.11 version (0.9.20) and at the end to version from this PR (0.10.6). I did a re-index and restart every time and did not notice any issue.
I used a graph that i had used with 0.10.6 before, so the test might not be 100% accurate.
Keep in mind that this software is known for loosing data (especially with their sync), so i recommend to create a backup before updating and check if changed are saved to file after an update! (i did not have any data loss so far; using syncthing for sync)
Description of changes
Backports several updates of logseq to unbreak it in 23.11 stable. The current version there is marked as insecure due to depending on electron-25.9.0.
Backports the following PRs: #272126 #273570 #274180 #281751 #282003
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.