Package: letsencrypt.sh
Version: 0.3.0-1~bpo8+1
Severity: grave
Tags: patch
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I installed letsencrypt.sh version 0.3.0-1~bpo8+1.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I ran "letsencrypt --cron" as root.
* What was the outcome of this action?
/usr/bin/letsencrypt.sh: line 179: ACCOUNT_KEY_JSON: unbound variable
* What outcome did you expect instead?
A successful run.
There is a typo on line 179; the $ and { characters seem to be
transposed. Patch included.
/Teddy Hogeborn
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 8.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/16 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages letsencrypt.sh depends on:
ii ca-certificates 20141019+deb8u2
ii curl 7.38.0-4+deb8u5
ii openssl 1.0.1t-1+deb8u5
letsencrypt.sh recommends no packages.
letsencrypt.sh suggests no packages.
-- no debconf information
-- debsums errors found:
debsums: changed file /usr/bin/letsencrypt.sh (from letsencrypt.sh package)
--- /usr/bin/letsencrypt.sh.~1~ 2016-12-08 15:24:46.000000000 +0100
+++ /usr/bin/letsencrypt.sh 2016-12-09 18:23:08.306160178 +0100
@@ -176,7 +176,7 @@
fi
if [[ -f "${ACCOUNT_KEY_JSON:-"${BASEDIR}/private_key.json"}" ]] && [[ ! -f "${new_ACCOUNT_KEY_JSON}" ]]; then
echo "! Moving private_key.json to ${new_ACCOUNT_KEY_JSON}"
- mv -v "{$ACCOUNT_KEY_JSON:-"${BASEDIR}/private_key.json"}" "${new_ACCOUNT_KEY_JSON}"
+ mv -v "${ACCOUNT_KEY_JSON:-"${BASEDIR}/private_key.json"}" "${new_ACCOUNT_KEY_JSON}"
fi
ACCOUNT_KEY="${new_ACCOUNT_KEY}"
ACCOUNT_KEY_JSON="${new_ACCOUNT_KEY_JSON}"
