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

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.

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

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

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

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

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

@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}"

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

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