Arch Linux User Repository

This package sets HOME=${SRCDEST:-$startdir}/node-home to avoid cluttering the user home directory, while allowing data (over 4GB) to be reused between builds. $srcdir is not used for this purpose because it can be wiped between runs.

This is interesting. I have different results on two different computers. (AMD vs Intel?) Will go ahead and bump versions. Any users who have the same build failure, try rolling back to 0.9.13 or use the -bin package.

No need to re-report the same issue. I'll update if I find a solution.

Note: No solution as of Jan 2024.

Clean chroot. Attempting to build after bumping to 0.9.14 or later results in error. Possibly related to AMD processors. Anyone know how to fix?

[4/4] Building fresh packages...
$ yarn build:amplify
$ parcel build ./src/amplify.ts --no-source-maps
error Command failed with signal "SIGSEGV".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
==> ERROR: A failure occurred in prepare().

@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?

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...

@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...

@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?

@ojford Try replacing nodejs with nodejs-lts-gallium.

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.

@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.

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!

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!

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.