all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: Attila Lendvai <attila@lendvai.name>
Cc: "62491@debbugs.gnu.org" <62491@debbugs.gnu.org>,
	"Ludovic Courtès" <ludovic.courtes@inria.fr>,
	"Maxim Cournoyer" <maxim.cournoyer@gmail.com>
Subject: bug#62491: [berlin] certbot renewal appears to be broken
Date: Thu, 23 Nov 2023 08:23:42 +0100	[thread overview]
Message-ID: <87pm0153wh.fsf@xelera.eu> (raw)
In-Reply-To: <vvzWc4OLtIgDeH6vblpu15xH0Ka3R8tyi4EAcZ4i7vxRXDIn9-9Pt09kWC3v9-OIRpyFVuF3tX0VzOLS-QmyLRWRU_gLPOLELrzpB-zG60U=@lendvai.name>

[-- Attachment #1: Type: text/plain, Size: 571 bytes --]

Hi Attila,

Attila Lendvai <attila@lendvai.name> writes:

[...]

> if yes, then i'll need to get back in context to answer properly.

In this thread I'd like to understand what is (was?) the real nature of
the bugs described, I'm just trying to collect more information

I feel we should discuss how the certbot service works in a different
thread, to stay focused on the bug report

If you need further discussion, please feel free to open a new thread on
guix-devel and Cc: me! :-)

Thanks! Gio'

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]

  reply	other threads:[~2023-11-23  7:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27 21:05 bug#62491: [berlin] certbot renewal appears to be broken Maxim Cournoyer
2023-05-04 14:37 ` bug#62491: (No Subject) Attila Lendvai
2023-11-22 17:37   ` bug#62491: [berlin] certbot renewal appears to be broken Giovanni Biscuolo
2023-11-22 18:05     ` Attila Lendvai
2023-11-23  7:23       ` Giovanni Biscuolo [this message]
2023-11-23  4:17     ` Maxim Cournoyer
2023-11-23  7:42       ` Giovanni Biscuolo
2023-11-23  8:46         ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pm0153wh.fsf@xelera.eu \
    --to=g@xelera.eu \
    --cc=62491@debbugs.gnu.org \
    --cc=attila@lendvai.name \
    --cc=ludovic.courtes@inria.fr \
    --cc=maxim.cournoyer@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.