Arch Linux User Repository

1. This package does not support system's electron anymore because yarn's electron already supports Wayland.
2. The desktop file by default launches Logseq with the regular X11 backend. There's an extra action defined in the desktop file to launch with the Wayland backend. How to trigger an action within a desktop file depends on your desktop environment or app launcher.
3. The package uses a user's home directory to store cached npm/clojure dependencies. Hope this speeds up the build process for users who don't have high-speed internet.

Extra notes to people who want to flag this package out-of-date:

This is a GIT AUR package. It has nothing to do with the released versions. Whenever you (re-)build a GIT AUR package, it automatically pulls and (re-)builds with the latest commit and updates the version tag. So as long as the building process works fine, a GIT AUR package is not out-of-date.

@bader Thanks. Fixed.

Package fails to build due to a recent change in shadow-cljs.edn and deps.edn

PR: https://github.com/logseq/logseq/pull/3517

Error:

==> Starting prepare()...
patching file deps.edn
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file deps.edn.rej
patching file shadow-cljs.edn
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file shadow-cljs.edn.rej
==> ERROR: A failure occurred in prepare().
    Aborting...
 -> error making: logseq-desktop-git

PSA: if you are having issues with high CPU in logseq ^0.5.2 this is due to switch to electron 15.

To fix the high CPU usage, you can re-index the graph on start of logseq or use the latest nightly release:

https://github.com/logseq/logseq/releases/tag/nightly

For more information, refer to the GitHub issue:

https://github.com/logseq/logseq/issues/3421#issuecomment-994988672

@pychuang I cleared the cache and yes I can confirm that fixed the build issue. Thank you!

@bader yeah, it's so mysterious. At my first attempt, yay -S logseq-desktop-git gave me the same error. At my second attempt, downloading the source manually and using this PKGBUILD worked well. At my last attempt, I deleted some cached files, and yay -S logseq-desktop-git suddenly worked again... though I don't know why. And now I'm not able to reproduce the error anymore...

If you are still not able to use yay to build/install this package, could you please try one or all of these tries?

1. removing ~/.cache/yay/logseq-desktop-git, ~/.npm, ~/.m2, and ~/.gitlibs
2. use the clean build mode from yay

The package fails to build

[:app] Compiling ...
The required JS dependency "electron" is not available, it was required by "node_modules/@sentry/electron/esm/renderer/backend.js".

Dependency Trace:
    frontend/core.cljs
    frontend/handler.cljs
    frontend/modules/instrumentation/core.cljs
    frontend/modules/instrumentation/sentry.cljs
    node_modules/@sentry/electron/esm/renderer/index.js
    node_modules/@sentry/electron/esm/renderer/client.js
    node_modules/@sentry/electron/esm/renderer/backend.js

Searched for npm packages in:
    /home/user/.cache/yay/logseq-desktop-git/src/logseq-desktop-git/node_modules

See: https://shadow-cljs.github.io/docs/UsersGuide.html#npm-install

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...
 -> error making: logseq-desktop-git

I was able to build the package manually by downloading from git

To the person who flagged (or anyone who wants to flag) this package as out-of-date:

This is a GIT AUR package. It has nothing to do with the released versions. Whenever you (re-)build a GIT AUR package, it automatically pulls and (re-)builds with the latest commit and updates the version tag. So as long as the building process works fine, a GIT AUR package is not out-of-date.

If you still have questions, please consult Wiki or Reddit before you do anything.

If you encounter an error saying Package subpath './lib/node' is not defined by "exports" in .../logseq/node_modules/postcss/package.json, try to manually replace your nodejs with nodejs-lts-gallium, which provides nodejs 16.

The Arch's nodejs now is at version 17, and some dependencies of logseq haven't been coping well with nodejs 17, though they should.

@Edgeworth Yes, nodejs is required during build time. However, npm already depends on nodejs, so according to Arch's guideline, there's no need to explicitly include nodejs in the makedepends again (npm is already in makedepends).

The issue you encountered was due to that nodejs-lts-erbium also provides nodejs. If you check nodejs-lts-erbium with pacman -Qi or -Si, it will show Provides: nodejs=12.22.4. So specifying nodejs in makedepends would not solve the issue because makepkg and pacman see nodejs-lts-erbium as a legal nodejs provider.

As the underlying issue is caused by the nodejs version rather than which nodejs package is used, I think the solution should be specifying the nodejs version in PKGBUILD. For example, nodejs>=16 will disqualify nodejs-lts-erbium because the later one only provides nodejs=12.22.4. I will try to test it later this weekend.

@pychuang, I think you're write, perhaps it may be a makedepends, because I was unable to build it until I installed nodejs which removed (conflict) nodejs-lts-erbium.

I'm not familiar with Java or JS either so this may be a case of the blind leading the blind :).