Signed-off-by: Bill Sprinters <sharkytheshark@mailbox.org>
---
Aerc has been forked, as Drew didn't want to be involved anymore.
See here for details: https://lists.sr.ht/~sircmpwn/aerc/<CFBVJ3G1Y4YB.ZI6C02D0MS0S%40diabtop>
Development of aerc is continuing from the new fork.

 community/aerc/APKBUILD | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/community/aerc/APKBUILD b/community/aerc/APKBUILD
index 1b839fd675..da64fd69d7 100644
--- a/community/aerc/APKBUILD
+++ b/community/aerc/APKBUILD
@@ -1,7 +1,7 @@
 # Maintainer: Drew DeVault <sir@cmpwn.com>
 pkgname=aerc
 pkgver=0.5.2
-pkgrel=2
+pkgrel=3
 pkgdesc="email client for your terminal"
 url="https://aerc-mail.org"
 # riscv64 blocked by crypto dependency
@@ -10,7 +10,7 @@ license="MIT"
 depends="less ncurses"
 makedepends="go scdoc"
 subpackages="$pkgname-doc"
-source="$pkgname-$pkgver.tar.gz::https://git.sr.ht/~sircmpwn/aerc/archive/$pkgver.tar.gz"
+source="$pkgname-$pkgver.tar.gz::https://git.sr.ht/~rjarry/aerc/archive/$pkgver.tar.gz"
 
 build() {
 	make PREFIX=/usr
-- 
2.34.1

I don't see any reason to simply "rebuild" it against the new upstream, which won't have changed at all. Why not update it to 0.6.0 at the same time?

-- 
via https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/27786#note_194532

Signed-off-by: Bill Sprinters <sharkytheshark@mailbox.org>
---
Aerc is now also updated to 0.6.0, which should fix the issue with the first patch.

 community/aerc/APKBUILD | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/community/aerc/APKBUILD b/community/aerc/APKBUILD
index 1b839fd675..c8d1b9bffe 100644
--- a/community/aerc/APKBUILD
+++ b/community/aerc/APKBUILD
@@ -1,7 +1,7 @@
 # Maintainer: Drew DeVault <sir@cmpwn.com>
 pkgname=aerc
-pkgver=0.5.2
-pkgrel=2
+pkgver=0.6.0
+pkgrel=0
 pkgdesc="email client for your terminal"
 url="https://aerc-mail.org"
 # riscv64 blocked by crypto dependency
@@ -10,7 +10,7 @@ license="MIT"
 depends="less ncurses"
 makedepends="go scdoc"
 subpackages="$pkgname-doc"
-source="$pkgname-$pkgver.tar.gz::https://git.sr.ht/~sircmpwn/aerc/archive/$pkgver.tar.gz"
+source="$pkgname-$pkgver.tar.gz::https://git.sr.ht/~rjarry/aerc/archive/$pkgver.tar.gz"
 
 build() {
 	make PREFIX=/usr
@@ -25,5 +25,5 @@ package() {
 }
 
 sha512sums="
-b5472f204ee2226dffaefb1a1554644711e030bac227cb708510fc4eec46ecb7ab48b7e82b1400024d8893ef2d4b880edffd98fd10339459015c0bb27956d452  aerc-0.5.2.tar.gz
+04c80d5c86cc1cf978ae2590a469f56241978253dab82dfa0a8b17860b496c2c9ee30ebf345953046968856da06beadebdced4bdee6e92d5faf85abe1ff5bcd3  aerc-0.6.0.tar.gz
 "
-- 
2.34.1

Bill Sprinters <sharkytheshark@mailbox.org> replied via email:

```
Signed-off-by: Bill Sprinters <sharkytheshark@mailbox.org>
---
Aerc is now also updated to 0.6.0, which should fix the issue with the first patch.

 community/aerc/APKBUILD | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/community/aerc/APKBUILD b/community/aerc/APKBUILD
index 1b839fd675..c8d1b9bffe 100644
--- a/community/aerc/APKBUILD
+++ b/community/aerc/APKBUILD
@@ -1,7 +1,7 @@
 # Maintainer: Drew DeVault <sir@cmpwn.com>
 pkgname=aerc
-pkgver=0.5.2
-pkgrel=2
+pkgver=0.6.0
+pkgrel=0
 pkgdesc="email client for your terminal"
 url="https://aerc-mail.org"
 # riscv64 blocked by crypto dependency
@@ -10,7 +10,7 @@ license="MIT"
 depends="less ncurses"
 makedepends="go scdoc"
 subpackages="$pkgname-doc"
-source="$pkgname-$pkgver.tar.gz::https://git.sr.ht/~sircmpwn/aerc/archive/$pkgver.tar.gz"
+source="$pkgname-$pkgver.tar.gz::https://git.sr.ht/~rjarry/aerc/archive/$pkgver.tar.gz"
 
 build() {
 	make PREFIX=/usr
@@ -25,5 +25,5 @@ package() {
 }
 
 sha512sums="
-b5472f204ee2226dffaefb1a1554644711e030bac227cb708510fc4eec46ecb7ab48b7e82b1400024d8893ef2d4b880edffd98fd10339459015c0bb27956d452  aerc-0.5.2.tar.gz
+04c80d5c86cc1cf978ae2590a469f56241978253dab82dfa0a8b17860b496c2c9ee30ebf345953046968856da06beadebdced4bdee6e92d5faf85abe1ff5bcd3  aerc-0.6.0.tar.gz
 "
-- 
2.34.1


```

-- 
via https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/27786#note_194564

Can you send your v2 in a new thread?

-- 
via https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/27786#note_194565

> Can you send your v2 in a new thread?
I've just done it now.
Sorry for the confusion, I'm still getting used to git send-email.

Bill Sprinters <sharkytheshark@mailbox.org> replied via email:

```
> Can you send your v2 in a new thread?
I've just done it now.
Sorry for the confusion, I'm still getting used to git send-email.

```

-- 
via https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/27786#note_194568