Arch Linux User Repository

Please support ARM64, patch below.

diff --git a/PKGBUILD b/PKGBUILD
index f3b0794..41ea2b8 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -4,21 +4,40 @@ _pkgname=lnd
 pkgver=0.20.0_beta
 _pkgver="${pkgver//_/-}"
 __pkgver="${_pkgver//\./\\\.}"
+case $CARCH in
+    "x86_64")
+       _arch="amd64"
+       ;;
+    "aarch64")
+       _arch="arm64"
+       ;;
+esac
 pkgrel=1
 pkgdesc="Lightning Network Daemon ⚡"
-arch=('x86_64')
+arch=('x86_64' 'aarch64')
 url="https://github.com/lightningnetwork/lnd"
 license=('MIT')
 provides=('lnd' 'lncli')
 conflicts=('lnd' 'lnd-git')
 source=(
-    "https://github.com/lightningnetwork/$_pkgname/releases/download/v$_pkgver/$_pkgname-linux-amd64-v$_pkgver.tar.gz"
     "$_pkgname-LICENSE-v$_pkgver::https://raw.githubusercontent.com/lightningnetwork/$_pkgname/v$_pkgver/LICENSE"
 )
+
+source_x86_64=(
+    "https://github.com/lightningnetwork/$_pkgname/releases/download/v$_pkgver/$_pkgname-linux-amd64-v$_pkgver.tar.gz"
+)
+source_aarch64=(
+    "https://github.com/lightningnetwork/$_pkgname/releases/download/v$_pkgver/$_pkgname-linux-arm64-v$_pkgver.tar.gz"
+)
 sha512sums=(
-    'f403f8d73e75506c536165a1c717d9fd6601d91ca29642ee714bfd99ae13010ab95b393744d000c4b34c91cab18c4292e013ab13077236744c3687fbec95e16c'
     '49de7041d5c7448a8f5cc387e4e820eca2a87c02b70d5a38aa3823354d960843e93ca12bd8b66a13708937539da85b90328bd4c32575792f0aa6755a011ba4bb'
 )
+sha512sums_x86_64=(
+    'f403f8d73e75506c536165a1c717d9fd6601d91ca29642ee714bfd99ae13010ab95b393744d000c4b34c91cab18c4292e013ab13077236744c3687fbec95e16c'
+)
+sha256sums_aarch64=(
+    'e4fb51cadd5d2a8d7bc6c4f834abf4605c89d361da328a0948e65fb7036d732a'
+)

 # This is a binary package, build flags do not apply
 options=(!debug)
@@ -47,7 +66,7 @@ prepare() {

     # Check the binaries match the manifest
     cat "$manifestfile" \
-        | grep "^[0-9a-f]\{64\}  $_pkgname-linux-amd64-v$__pkgver\(\.tar\.gz\|/lnd\|/lncli\)$" \
+        | grep "^[0-9a-f]\{64\}  $_pkgname-linux-$_arch-v$__pkgver\(\.tar\.gz\|/lnd\|/lncli\)$" \
         | sha256sum -c -

     maintainers=(
@@ -101,8 +120,8 @@ prepare() {
 }

 package() {
-    install -Dm 755 "$srcdir/$_pkgname-linux-amd64-v$_pkgver/lncli" -t "$pkgdir/usr/bin";
-    install -Dm 755 "$srcdir/$_pkgname-linux-amd64-v$_pkgver/lnd" -t "$pkgdir/usr/bin";
+    install -Dm 755 "$srcdir/$_pkgname-linux-$_arch-v$_pkgver/lncli" -t "$pkgdir/usr/bin";
+    install -Dm 755 "$srcdir/$_pkgname-linux-$_arch-v$_pkgver/lnd" -t "$pkgdir/usr/bin";

     install -Dm644 "${srcdir}/$_pkgname-LICENSE-v$_pkgver" -t "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"
 }

Please don't flag package as out of date for reasons other than the package being out of date.

Edit: I appreciate the heads-up about the revoked key though. Seems like it hasn't been relevant in the 2 years since it's been revoked, so I removed it.

What manual changes were you hoping to avoid? Importing the keys? If so, I don't believe it's generally considered a good practice to make automatic changes to the user's key store on their behalf. Do you use/know of any AUR packages that do this?

Hi,

Had some problems with keys too. On the Lightning "builder's guide", it says the keys are here (https://github.com/lightningnetwork/lnd/tree/master/scripts/keys) and we need to do a gpg --import to import each key.

I'm not an expert with all that but is there something to do with that information to avoid manual changes ?

Thanks

@dougEfish you need to update them. Unfortunately, some lnd devs are bit funky when it comes to managing their pgp keys; they don't all publish them on keyservers, and some of the ones in their repo are also expired... You can find them on keybase.

Looks like these keys are no longer valid:

 -> 9FC6B0BFD597A94DBF09708280E5375C094198D8, required by: lnd-bin
 -> 7AB3D7F5911708842796513415BAADA29DA20D26, required by: lnd-bin
 -> EB13A98091E8D67CDD7FC5A7E9FE7FE00AD163A4, required by: lnd-bin

:: Importing keys with gpg...
gpg: keyserver receive failed: No data

@setpill I did not know what the cause was since I do not know much about keyrings I thought it was the package's fault.

I'm not exactly sure what you are suggesting is broken. Each user is responsible for managing their own gpg keyring. Were you expecting the package to change your keyring for you?

The package is broken. I get this error: Fehler: Ausführung fehlgeschlagen: gpg --recv-keys 7E81EF6B9989A9CC93884803118759E83439A9B1:.

Edit: It only has the issues with paru. pikaur works fine installing this package.

Release v0.13.0-beta skipped due to a bug causing payments to fail (see https://github.com/lightningnetwork/lnd/issues/5406 and https://github.com/lightningnetwork/lnd/issues/5415 )