Aarch64 build

[baarkerlounger]

The aarch64 build seems to be several versions (1.7.0) behind the x86_64 builds (1.26.4).

[hfiguiere]

Does it even work ? Current build is x86_64 only from a .deb package.

[hfiguiere]

See f3e64e8 and #16

[baarkerlounger]

Currently running 1.7.0 on a PinePhone (ARM64) running Mobian and installed via flatpak - that works fine. Just no updates for it since then obviously.

[ghisvail]

There has been an attempt to switch back to a source build in #55

[hfiguiere]

I thought electron was about to make application portable...

#sarcasm

[ghisvail]

I thought electron was about to make application portable...

Truth be told Electron has got its issues, but often it's the insanity of JavaScript packaging which is at fault. There are very little projects I know where offline builds are possible without a non-trivial amount of patching.

[alistair23]

Bitwarden now builds ARM binaries, see bitwarden/desktop#1095

It should be possible to just use those .debs once a release happens

[hfiguiere]

patch got revert. It seems that again, github is the blocker.

Now we do have builder for aarch64 on flathub, so building from source could be a solution.

[hfiguiere]

which I know was also reverted.

[locness3]

What's the status of this?

[ghisvail]

Nothing new.

[julianfairfax]

There has been an attempt to switch back to a source build in #55

Was the attempt unsuccessful?

[ghisvail]

Considering the upstream repository has been restructured, there is a high chance that the last attempt of building from source needs a rework.

[alexhaydock]

What is needed for #55 to get merged?

I notice that the aarch64 build is reported as existing by Flatpak and it does actually download on an aarch64 host, but it doesn't run:

user@asahi:~$ flatpak run com.bitwarden.desktop 
/app/bin/bitwarden: line 2:     3 Segmentation fault      (core dumped) npm start --prefix=/app/main

It does look like the version of Node that's being packaged here is correctly aarch64 so I'm not sure why the immediate segfault, but I didn't look into it too closely given that #55 still seems to be open:

user@asahi:~$ file /var/lib/flatpak/app/com.bitwarden.desktop/aarch64/stable/9eaa33ff7890ee62da3718e148774220176666364adabeb9bf7502d7f6a7da29/files/bin/node
/var/lib/flatpak/app/com.bitwarden.desktop/aarch64/stable/9eaa33ff7890ee62da3718e148774220176666364adabeb9bf7502d7f6a7da29/files/bin/node: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, stripped

[hfiguiere]

What is needed for #55 to get merged?

Probably the maintainers. Now if somebody can rebase it to trigger a new build that can be tested and it is tested to work, I'd be happy to press the merge button.