Hi Harlan,
On Sun, Dec 6, 2020 at 5:37 AM Harlan Lieberman-Berg
wrote:
> Took a look at this and tried to duplicate it by updating my stretch
> sbuild to use the security repo in case that did anything. No joy.
> The only difference between our environments now is eatmydata -- which
> could expl
Hi Utkarsh,
Took a look at this and tried to duplicate it by updating my stretch
sbuild to use the security repo in case that did anything. No joy.
The only difference between our environments now is eatmydata -- which
could explain odd file existance problems, considering.
I think it's good to
Hi Utkarsh,
That's not something I've seen before. Could you send me the build
log? It's probably fine if it happened during the testing stage, but
I'd like to double check considering this is going to stable directly.
Sincerely,
On Sat, Dec 5, 2020 at 11:49 AM Utkarsh Gupta wrote:
>
> Hi Har
Hi Harlan,
On Sat, Dec 5, 2020 at 3:23 PM Harlan Lieberman-Berg
wrote:
> Perfect. Let me know if you run into any issues. It should be pretty smooth -
> tested it in a clean stretch schroot and the patch isn't that complicated -
> but, you never know.
Just a quick question: whilst the build we
On Sat, Dec 5, 2020 at 04:41 Utkarsh Gupta wrote:
> Hi Harlan,
>
> I can take a more thorough look later today and upload this as is and
> release the announcement for it. Does it sound good to you?
>
Perfect. Let me know if you run into any issues. It should be pretty smooth
- tested it in a cl
Hi Harlan,
On Sat, 5 Dec, 2020, 2:48 pm Harlan Lieberman-Berg,
wrote:
> As part of the deprecation of the Let's Encrypt v1 API starting in
> January, we need to enable automatic conversion of the use of the v1
> endpoints to v2 endpoints in the version of certbot currently used in
> stretch.
>
>
