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: 26
Popularity: 0.91
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

1 2 3 4 5 6 7 Next › Last »

cwg1231 commented on 2024-05-03 04:16 (UTC)

When trying to update to 0.10.9-1, logseq-desktop-debug has a conflict with pulsar-desktop-debug.


error: failed to commit transaction (conflicting files)
logseq-desktop-debug: /usr/lib/debug/.build-id/08/05eac40eca021940fba86362246c391d52c5d1 exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/08/05eac40eca021940fba86362246c391d52c5d1.debug exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/2f/33078e6a1afa933d498dbc1ddba2954c80a969 exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/2f/33078e6a1afa933d498dbc1ddba2954c80a969.debug exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/54/ec801d25cfdd9e8e9647390ad4b878a30c9a74 exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/54/ec801d25cfdd9e8e9647390ad4b878a30c9a74.debug exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/80/4d27ab6ea5f4e51fdb2a42cf621db79a4ce34b exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/80/4d27ab6ea5f4e51fdb2a42cf621db79a4ce34b.debug exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/93/399ebc639a43226f8348722c39f9d36f5f87b1 exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/93/399ebc639a43226f8348722c39f9d36f5f87b1.debug exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/ad/bc37dbdae4f661213461904c0f01e005904b80 exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/ad/bc37dbdae4f661213461904c0f01e005904b80.debug exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/c3/ab3bd2f454c29415f4288c342d597be40b9cf3 exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/c3/ab3bd2f454c29415f4288c342d597be40b9cf3.debug exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/c6/abc02ed033ae5743b649be6f164afb007f2c2c exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/c6/abc02ed033ae5743b649be6f164afb007f2c2c.debug exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/d4/1fe579bed152666214ab352bddb7c03610b59a exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/d4/1fe579bed152666214ab352bddb7c03610b59a.debug exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/f6/294e6fc2647a8e507b42b1b0f9e8ab0afd06cb exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/f6/294e6fc2647a8e507b42b1b0f9e8ab0afd06cb.debug exists in filesystem (owned by pulsar-bin-debug)

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-11-03 22:15 (UTC) (edited on 2023-11-03 23:49 (UTC) by xiota)

@AlbertoAru Try building in a clean chroot.

Have you successfully built a previous version of this package in the past, or is this your first time trying to build this? If this is your first time building, try building 0.9.13 (change pkgver, set first checksum to SKIP).

Are you using an AMD processor?

AlbertoAru commented on 2023-11-03 21:32 (UTC)

GitHub is back, and with it the first part of the error (before the rm -rf .cache/yay/* section of my comment)

xiota commented on 2023-11-03 19:26 (UTC) (edited on 2023-11-03 21:59 (UTC) by xiota)

... 404 ... https://github.com/ ...

GitHub is hav[ing] some issue right now. Try again later.

AlbertoAru commented on 2023-11-03 19:00 (UTC) (edited on 2023-11-03 19:01 (UTC) by AlbertoAru)

I found this error during the upgrade.

.cache/yay/logseq-desktop/src/logseq-0.9.20/static/node_modules/electron-deeplink: Command failed.

[...]

==> ERROR: A failure occurred in prepare().
    Aborting...
 -> error making: logseq-desktop-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
logseq-desktop - exit status 4

After a rm -rf .cache/yay/* I got:

==> ERROR: Failure while downloading https://github.com/logseq/logseq/archive/refs/tags/0.9.20.zip
    Aborting...
 -> error downloading sources: .cache/yay/logseq-desktop 
         context: exit status 1 


:: (1/1) Parsing SRCINFO: logseq-desktop
==> Making package: logseq-desktop 0.9.20-1 (Fri Nov  3 19:57:06 2023)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading logseq-desktop-0.9.20.zip...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     9    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404
==> ERROR: Failure while downloading https://github.com/logseq/logseq/archive/refs/tags/0.9.20.zip
    Aborting...
 -> error making: logseq-desktop-exit status 1
 -> Failed to install the following packages. Manual intervention is required:
logseq-desktop - exit status 1

heijul commented on 2023-09-11 06:48 (UTC) (edited on 2023-09-11 07:05 (UTC) by heijul)

@xiota Thanks for the update, though the permission issue remains.

Took me a bit to find a fix and the reason (building takes too long :P ), but here's why: The problem is that the -a flag of cp preserves the mode (which for the files is what we want, I guess). When using ./ as source path the mode of the destination directory is updated, as well.

With either of these changes below it works properly:

Same as in logseq-desktop-git:

diff --git a/PKGBUILD b/PKGBUILD
index f9a2cd4..5984b32 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -59,2 +59,3 @@ package() {
     # important files are under static/out/Logseq-linux-x64
+    chmod 755 "${srcdir}/logseq-${pkgver}/static/out/Logseq-linux-x64"
     cd "${srcdir}/logseq-${pkgver}/static/out/Logseq-linux-x64"

Alternatively, but I'm not certain whether there are side-effects (though I don't see why there would be any):

diff --git a/PKGBUILD b/PKGBUILD
index f9a2cd4..465b67d 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -63,3 +63,3 @@ package() {
     install -dm755 "${pkgdir}/opt/${pkgname}"
-    cp -a -r -u --verbose ./ "${pkgdir}/opt/${pkgname}"
+    cp -a -r -u --verbose ./* "${pkgdir}/opt/${pkgname}"

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.

heijul commented on 2023-09-10 10:52 (UTC) (edited on 2023-09-10 10:56 (UTC) by heijul)

@xiota I am not sure if I missed anything (I'm new to packaging), but wanted to mention that building in a clean chroot worked for me.

FWIW, here's what I did (as normal user):

git clone https://aur.archlinux.org/logseq-desktop.git
cd logseq-desktop
# Update the PKGBUILD (see diff below).
mkdir chroot
CHROOT=./chroot
mkarchroot $CHROOT/root base-devel
arch-nspawn $CHROOT/root pacman -Syu
makechrootpkg -c -r $CHROOT
sudo pacman -U logseq-desktop-0.9.15-1-x86_64.pkg.tar.zst

Using:

diff --git a/PKGBUILD b/PKGBUILD
index 01db055..84aed88 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -4,3 +4,3 @@
 pkgname=logseq-desktop
-pkgver=0.9.13
+pkgver=0.9.15
 pkgrel=1
@@ -19,3 +19,3 @@ source=(
 sha256sums=(
-    'bb314c141a1b2a22e658ed29879929bf0c48c311334f195cc9cb3d6bcc9a8e96'
+    'ecf4c3485ba16c77892350d4a65515499fa9708cb3de5c8da58437ba34526fc0'
     'b26c6ed39e2635e08a0df83d92883e670b75b02ed1c2c279044909c04edf8fc2'

Using pkgver=0.9.14 with the proper sha256sum worked as well.

Also, I had to run sudo chmod 755 /opt/logseq-desktop afterwards, to run logseq as normal user. AFAICT this should probably be done in the PKGBUILD.

Hope this helps :)