Your message dated Fri, 9 Dec 2016 18:41:28 +0100 with message-id <20161209174127.ga21...@mapreri.org> and subject line Re: [Letsencrypt-devel] Bug#847594: ACCOUNT_KEY_JSON: unbound variable has caused the Debian Bug report #847594, regarding ACCOUNT_KEY_JSON: unbound variable to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 847594: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847594 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---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}"
--- End Message ---
--- Begin Message ---notfound 847594 0.3.0-1~bpo8+1 found 847594 0.3.0-1 fixed 847594 0.3.0-2 stop On Fri, Dec 09, 2016 at 06:29:47PM +0100, Teddy Hogeborn wrote: > Package: letsencrypt.sh > Version: 0.3.0-1~bpo8+1 backports version are not known to the bug tracker. > /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. Yeah, I happen to have just uploaded it :) I'm checking with the release team whether they grant me a speedy testing migration, so I can backport it properly, otherwise I'll release a ~bpo8+2 to have the fix deployed. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
--- End Message ---
