[Letsencrypt-devel] Bug#839851: Bug#839851: [letsencrypt.sh] New upstream available
mattia at debian.org
Wed Nov 30 20:11:28 UTC 2016
On Wed, Oct 05, 2016 at 08:13:53PM +0200, Jan Wagner wrote:
> thanks for working hard on the letsencrypt.sh packages and doing such a
> great job.
It would be a lot easier and more stimulating if upstream cared more
about backward compatibility.
Every single update has some breakage, which we don't want to have, so
we end up creating some upgrade plan on our own. Apparently recently
Lukas started to care a tad bit more, but really it's not enough :S
For 0.3.0 to be sane I did:
* revert config.sh rename, which had no upgrade plan whatsoever upstream
* add another safety net for ACCOUNT_KEY removal (did I got it right?
tbh I've just committed it after I wrote, without running it once)
I'm sure I missed something somewhere else....
> There is an new version available (0.3.1). Also the project name
> changes, but I'll create another bug report about this.
I've now imported 0.3.0. I'll now need to test it a bit myself, but if
you want feel free to steal it from git and help test it out.
I'll probably package dehydrated soon after this, but I don't think
I'll be able to create a decent upgrade plan from letsencrypt.sh to
dehydrated in time to for the stretch freeze.
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 `-
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: not available
More information about the Letsencrypt-devel