Re: [Letsencrypt-devel] Certbot in Debian Stretch
On 28/11/16 18:13, Peter Eckersley wrote:
> On Fri, Nov 25, 2016 at 12:48:35PM +0100, Christian Seiler wrote:
>
>> Note that per backports rules, $RELEASE_N-backports must track
>> $RELEASE_N_PLUS_1, so if you remove certbot from Stretch, you'll
>> also have to remove it from jessie-backports.
>
> Thank you for pointing this out Christian. This policy removes what might have
> been the simplest option, and seems to mean that we'll want to work hard on a plan
> where Certbot is in Stretch in a way that works both for us upstream and for
> the Debian release team.
>
This would probably mean making sure the client is checking the network
API version and giving the user helpful, distro-specific instructions if
there is a mismatch, e.g. a Debian user would see a message "The Let's
Encrypt API no longer supports your client version, it is now essential
for you to install certbot by (running apt-get upgrade | using
$RELEASE_N-backports)"
To get the message exactly right, it would be useful if the certbot
utility would actually check the apt catalog for both an SRU and
backport and tell the user exactly which one is sufficient to get them
going again.
Regards,
Daniel
Reply to: