Package Details: logseq-desktop 0.10.9-5

Git Clone URL: https://aur.archlinux.org/logseq-desktop.git (read-only, click to copy)
Package Base: logseq-desktop
Description: Privacy-first, open-source platform for knowledge sharing and management
Upstream URL: https://github.com/logseq/logseq
Licenses: AGPL-3.0-or-later
Submitter: xuanwo
Maintainer: xiota
Last Packager: xiota
Votes: 28
Popularity: 0.29
First Submitted: 2021-03-28 16:28 (UTC)
Last Updated: 2025-01-07 17:38 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

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

replacing nodejs with nodejs-lts-gallium.

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.

$ /var/tmp/pamac-build-admin/logseq-desktop/src/logseq-0.6.6/static/node_modules/.bin/electron-forge package
✔ Checking your system
⠦ Preparing to Package Application for arch: x64WARNING: Found 'electron' but not as a devDependency, pruning anyway
✔ Preparing to Package Application for arch: x64
⠧ Preparing native dependencies: 1 / 2gyp: name 'openssl_fips' is not defined while evaluating condition 'openssl_fips != ""' in binding.gyp while trying to load binding.gyp
✖ Preparing native dependencies: 1 / 2

An unhandled error has occurred inside Forge:
node-gyp failed to rebuild '/tmp/electron-packager/linux-x64/Logseq-linux-x64/resources/app/node_modules/electron-deeplink'.
For more information, rerun with the DEBUG environment variable set to "electron-rebuild".

Error: `gyp` failed with exit code: 1


Error: node-gyp failed to rebuild '/tmp/electron-packager/linux-x64/Logseq-linux-x64/resources/app/node_modules/electron-deeplink'.
For more information, rerun with the DEBUG environment variable set to "electron-rebuild".

Error: `gyp` failed with exit code: 1


at NodeGyp.rebuildModule (/var/tmp/pamac-build-admin/logseq-desktop/src/logseq-0.6.6/static/node_modules/@electron-forge/core/node_modules/electron-rebuild/src/module-type/node-gyp.ts:129:13)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at ModuleRebuilder.rebuildNodeGypModule (/var/tmp/pamac-build-admin/logseq-desktop/src/logseq-0.6.6/static/node_modules/@electron-forge/core/node_modules/electron-rebuild/src/module-rebuilder.ts:93:5)
at ModuleRebuilder.rebuild (/var/tmp/pamac-build-admin/logseq-desktop/src/logseq-0.6.6/static/node_modules/@electron-forge/core/node_modules/electron-rebuild/src/module-rebuilder.ts:129:8)
at Rebuilder.rebuildModuleAt (/var/tmp/pamac-build-admin/logseq-desktop/src/logseq-0.6.6/static/node_modules/@electron-forge/core/node_modules/electron-rebuild/src/rebuild.ts:203:9)
at Rebuilder.rebuild (/var/tmp/pamac-build-admin/logseq-desktop/src/logseq-0.6.6/static/node_modules/@electron-forge/core/node_modules/electron-rebuild/src/rebuild.ts:158:9)
at /var/tmp/pamac-build-admin/logseq-desktop/src/logseq-0.6.6/static/node_modules/@electron-forge/core/src/util/rebuild.ts:38:5
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
==> ERROR: A failure occurred in build().
Aborting...

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/29

Logseq 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 with nodejs-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:

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/node' is not defined by "exports" in $XDG_CACHE_HOME/yay/logseq-desktop/src/logseq-0.5.6/node_modules/postcss/package.json

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!

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »