Search Criteria
Package Details: logseq-desktop 0.6.9-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/logseq-desktop.git (read-only, click to copy) |
---|---|
Package Base: | logseq-desktop |
Description: | A privacy-first, open-source platform for knowledge sharing and management. |
Upstream URL: | https://github.com/logseq/logseq |
Licenses: | AGPL3 |
Conflicts: | logseq-desktop-bin, logseq-desktop-git |
Provides: | logseq-desktop |
Submitter: | xuanwo |
Maintainer: | xuanwo (pychuang, zjuyk) |
Last Packager: | xuanwo |
Votes: | 19 |
Popularity: | 2.42 |
First Submitted: | 2021-03-28 16:28 (UTC) |
Last Updated: | 2022-05-16 14:53 (UTC) |
Dependencies (5)
- clojure (clojure-git) (make)
- git (git-git, git-vfs, git-run-command-patch-git) (make)
- nodejs-lts-gallium (make)
- npm (nodejs6-bin, nodejs-nightly) (make)
- yarn (yarn-nightly) (make)
Latest Comments
shinanqu commented on 2022-05-06 19:58 (UTC)
@ddlsak Worked perfectly, you are my hero of the week. Thank you very much!
ddlsak commented on 2022-04-29 06:09 (UTC)
@shinanqu I had the same problem. It was resolved by
See this comment.
Maybe nvm might be a possible solution to allow people to have latest nodejs installed while also satisfying the build dependencies?
shinanqu commented on 2022-04-27 13:19 (UTC) (edited on 2022-04-27 13:21 (UTC) by shinanqu)
Sadly the newest version 0.6.6-1 always leads to an error message when updating.
pychuang commented on 2022-01-11 14:09 (UTC) (edited on 2022-01-11 14:12 (UTC) by pychuang)
@ojford It's from the package
postcss
(one of Logseq's dependencies): https://github.com/postcss/postcss-safe-parser/issues/29Logseq upstream does not mention anything related to this issue. The upstream dev team probably uses an older nodejs, I guess? I think Logseq dev team has to either bump the postcss version or limit the supported nodejs version to 16.
However, nodejs is just a build time dependency, not a runtime dependency. Though annoying, you can switch back to nodejs 17 after installing
logseq-desktop
...OJFord commented on 2022-01-10 12:19 (UTC)
@pychuang Unfortunately I need node v17. Is that a known (upstream?) issue, or a just a suggestion to try? If so is there a better way of expressing the nodejs dependency so that it excludes stable & nightly?
pychuang commented on 2022-01-04 13:10 (UTC)
@ojford Try replacing
nodejs
withnodejs-lts-gallium
.OJFord commented on 2021-12-29 17:20 (UTC) (edited on 2021-12-29 17:20 (UTC) by OJFord)
The v0.5.6 bump seems to have missed .SRCINFO, so the package details here are still for
0.5.5-2
.Also, I'm seeing:
Which causes it to fail.
pychuang commented on 2021-12-27 16:32 (UTC)
@xuanwo The PKGBUILD failed due to the wrong folder path in
package()
. I pushed a new commit that should fix the issue. The build process worked fine now on my machine. However, I did not test whether the installed Logseq worked as expected.xuanwo commented on 2021-12-27 02:20 (UTC)
0.5.5-1 is a draft to support build from source.
And I met some network issues like "RequestError: socket hang up", so I can't test the build by myself.
Please leave comments to give me some help, thanks!
xuanwo commented on 2021-12-12 15:59 (UTC)
I have to admit that it's so complicated for me to maintain a pkgbuild for logseq-desktop. I'm looking for a co-maintainer(s) to finish this migration.
If you are interested, please leave comments to let me know!
pychuang commented on 2021-12-11 05:31 (UTC)
I'm maintaining
logseq-desktop-git
, which is built from the source (the latest git commit). The build process of released versions is probably similar to building from GitHub source. Just for your reference.xuanwo commented on 2021-12-11 05:26 (UTC)
As requested by the comments, I will maintain a new package called logseq-desktop-bin.
Here is the plan:
xuanwo commented on 2021-12-09 07:19 (UTC)
@abhinav, thanks for your information.
But v0.5.2 is a pre-release and the SHA will be changed after it has been finally released. So this package will only track the latest release. I will update the package once the release is ready.
abhinav commented on 2021-12-09 05:24 (UTC)
FYI 0.5.2 is now available. SHA: 71bd580e578cef9fbf28af070d7569473eba5cf74eba5d50113644e6085dd3a9.
rrenn commented on 2021-12-02 10:07 (UTC)
This AUR package don't build from source, please rename package name to logseq-desktop-bin.
xuanwo commented on 2021-11-25 09:02 (UTC)
From upstream:
sardaukar commented on 2021-10-11 19:28 (UTC)
Please update the SHA-256 for logseq-linux-x64-0.4.3.zip from
6c559b42eb227457e528006e4ff9de4405d9e12fefdf79d5f55063e58393e78e
tobb76a263f1050f96bdf796a4a05bab6ea5b91edd825db983d6e9dc301fbfb2b1
dmz.madrid commented on 2021-09-15 21:35 (UTC)
Please update the SHA-256 for
logseq-linux-x64-0.3.9.zip
from82061e862e0e5f39be14f2c8a2a47d2a48d1cffc69b900532183e2fe1e5f536c
tod541a903b16f0216734547b2c465cc3c563c16c3bcb15288209331099cc7d902
xuanwo commented on 2021-07-31 05:04 (UTC)
0.2.8 confirmed to have bugs that led to data lose, please upgrade to 0.3.0 ASAP.
xuanwo commented on 2021-06-16 01:33 (UTC)
0.1.7 confirmed to have many bugs, please upgrade to 0.1.8 ASAP.
xuanwo commented on 2021-05-25 00:31 (UTC)
The database could be broken after an upgrade from 0.20.0 to 0.1.0.
This could be fixed by remove logseq's cache:
xuanwo commented on 2021-04-22 04:18 (UTC)
@newzubakhin The indentation has been removed!
xuanwo commented on 2021-04-22 04:16 (UTC)
@liul85 The icon has been added!
liul85 commented on 2021-04-22 00:33 (UTC)
Hi @xuanwo,
Can you update the
PKGBUILD
file with changes below to give it an icon, thanks! the current one doesn't work, there is no icon for this app.my desktop environment -> GNOME40.0
git diff
Thanks!
newzubakhin commented on 2021-04-21 22:17 (UTC)
Please remove the identation from .desktop file
commented on 2021-03-17 17:03 (UTC)
@pychuang thanks for letting me know! updated it as you said. (I actually had it as
logseq-desktop-bin
!)thanks for maintaining!
pychuang commented on 2021-03-17 16:32 (UTC)
Hi, I created a git version of logseq: https://aur.archlinux.org/packages/logseq-desktop-git/. The git version and this binary version should have the same
provides
and conflict with each other. Should we agree on the name to put inprovides
? I personally prefer simplylogseq-desktop
. Thanks!