control: found -1 0.1.0-2 control: notfound -1 0.1.0-2~bpo8+1 control: forwarded -1 https://github.com/lukas2511/letsencrypt.sh/pull/202
On Sat, May 21, 2016 at 06:34:41AM +0200, David Kuehling wrote: > Version: 0.1.0-2~bpo8+1 > I'm testing this using the backports package, but I guess the problem > applies to sid as well (same version). Yeah, but, well, don't report bugs using the backport version. The Debian BTS does a version tracker, and it is not aware of the backports, and fun things happens. > Recently letsencrypt.org changed to return pretty json with lots of > newlines (as tested via > https://acme-staging.api.letsencrypt.org/directory). I wonder when this happened and how. Exactly yesterday I renewed some certs of mine and the things just worked. > This breaks > various sed-based json parsing code in the distributed version of > letsencrypt.sh . Also I wonder if it would be better if letsencrypt.sh used jq(1) instead of sed, but well.. > https://github.com/lukas2511/letsencrypt.sh/pull/202 > > The "official" fix is here: > > > https://github.com/lukas2511/letsencrypt.sh/commit/561f0626b855ec4ee94856884e2f1eff9ade2d88 > > cheers, yeah, great, guess we can just cherry-pick it :) -- 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