Package Details: logseq-desktop 0.10.9-1

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: 25
Popularity: 0.26
First Submitted: 2021-03-28 16:28 (UTC)
Last Updated: 2024-04-30 14:33 (UTC)

Pinned Comments

xiota commented on 2024-01-15 00:17 (UTC) (edited on 2024-01-15 00:19 (UTC) by xiota)

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.

xiota commented on 2023-09-11 03:34 (UTC) (edited on 2024-01-14 17:37 (UTC) by xiota)

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.

xiota commented on 2023-08-23 07:46 (UTC) (edited on 2023-12-03 06:07 (UTC) by xiota)

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

Latest Comments

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

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:

  • logseq-desktop-bin will be built from binary that released by upstream just like this package did.
  • logseq-desktop-bin will conflict with logseq-desktop
  • Since v0.5.2, this package will be built from the source

I'm facing some build issues so far, so the v0.5.2 release for logseq-desktop could be delayed.

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.

bgme 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:

We strongly encouraged you to upgrade to the latest version (note: v0.5.1) to avoid any data loss.

sardaukar commented on 2021-10-11 19:28 (UTC)

Please update the SHA-256 for logseq-linux-x64-0.4.3.zip from 6c559b42eb227457e528006e4ff9de4405d9e12fefdf79d5f55063e58393e78e to bb76a263f1050f96bdf796a4a05bab6ea5b91edd825db983d6e9dc301fbfb2b1

dmz.madrid commented on 2021-09-15 21:35 (UTC)

Please update the SHA-256 for logseq-linux-x64-0.3.9.zip from 82061e862e0e5f39be14f2c8a2a47d2a48d1cffc69b900532183e2fe1e5f536c to d541a903b16f0216734547b2c465cc3c563c16c3bcb15288209331099cc7d902

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:

rm -r ~/.config/Logseq

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