Looks like letsencrypt fucked up release engineering, noticed this
because somebody flagged this package...
See: https://github.com/letsencrypt/letsencrypt/issues/1966
---
community/letsencrypt/APKBUILD | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/community/letsencrypt/APKBUILD b/community/letsencrypt/APKBUILD
index e4df3cf..0947423 100644
--- a/community/letsencrypt/APKBUILD
@@ -2,7 +2,8 @@
# Maintainer: Francesco Colista <fcolista@alpinelinux.org>
pkgname=letsencrypt
pkgver=0.1.1
-pkgrel=0
+_realver=$pkgver-corrected
+pkgrel=1
pkgdesc="An ACME client that can update Apache/Nginx configurations"
url="https://github.com/letsencrypt/letsencrypt"
arch="noarch"
@@ -19,10 +20,9 @@ depends_dev=""
makedepends="$depends_dev $_depends_acme"
install=""
subpackages="py-acme:acme"
-source="letsencrypt-$pkgver.tar.gz::https://github.com/letsencrypt/letsencrypt/archive/v$pkgver.tar.gz"
-
-_builddir="$srcdir"/letsencrypt-$pkgver
+source="$pkgname-$pkgver.tar.gz::https://github.com/$pkgname/$pkgname/archive/v$_realver.tar.gz"
+_builddir="$srcdir"/$pkgname-$_realver
prepare() {
local i
cd "$_builddir"
@@ -51,6 +51,6 @@ acme() {
python setup.py install --prefix=/usr --root="$subpkgdir" || return 1
}
-md5sums="b686984988e05af54e19b7dbcad75a82 letsencrypt-0.1.1.tar.gz"
-sha256sums="3f5210fc2e28577b1b24c4fbfb5c20ac259925a5fad81cf69a1b4f62d76511db letsencrypt-0.1.1.tar.gz"
-sha512sums="bd045622f77272447b9d497c410a128c30371c6df5beab418089c2c8b26fef9e87ecc6055bdf4017d7d2fb5f840b4900ff9efba848d07a2bf3a1be9d7fc0df99 letsencrypt-0.1.1.tar.gz"
+md5sums="93d639e954c2c7aabca2d74c6e921346 letsencrypt-0.1.1.tar.gz"
+sha256sums="d9efa11a90cd38bf38218e51c541978ebb836f00ede0c9c8155301ca30a55774 letsencrypt-0.1.1.tar.gz"
+sha512sums="26e8b41280a0e9bdbd7324d223c7d72915d2a9149b6a569bad3c17deb01c3426b93b86d4e411865526308e656df5a7d1fb6eaca9fab95600f6ed87def5c30a5a letsencrypt-0.1.1.tar.gz"
--
2.7.0
---
Unsubscribe: alpine-aports+unsubscribe@lists.alpinelinux.org
Help: alpine-aports+help@lists.alpinelinux.org
---