unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jack Hill <jackhill@jackhill.us>
To: guix-devel@gnu.org
Subject: Re: Certbot with alternative certificate authority
Date: Thu, 5 Mar 2020 14:49:06 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.20.2003051444230.19733@marsh.hcoop.net> (raw)
In-Reply-To: <alpine.DEB.2.20.2003051334390.19733@marsh.hcoop.net>

On Thu, 5 Mar 2020, Jack Hill wrote:

> What error have I made?

Thanks to Tobias Geerinckx-Rice on IRC, it looks like I forgot additional 
record changes as well. Even though Tobias was not able to reproduce my 
exact problem, making the following additional changes fixed it for me:


```
diff --git a/gnu/services/certbot.scm b/gnu/services/certbot.scm
index 3e71026387..f2cc00e97f 100644
--- a/gnu/services/certbot.scm
+++ b/gnu/services/certbot.scm
@@ -146,7 +146,7 @@
           (message (format #f (G_ "~a may need to be run~%") script)))
      (match config
        (($ <certbot-configuration> package webroot certificates email
-                                  rsa-key-size default-location)
+                                  server rsa-key-size default-location)
         (with-imported-modules '((guix build utils))
           #~(begin
               (use-modules (guix build utils))
@@ -158,7 +158,7 @@
  (define certbot-nginx-server-configurations
    (match-lambda
      (($ <certbot-configuration> package webroot certificates email
-                                rsa-key-size default-location)
+                                server rsa-key-size default-location)
       (list
        (nginx-server-configuration
```

I will clean up these changes and submit a proper patch to improve our 
certbot service.

Best,
Jack

  reply	other threads:[~2020-03-05 19:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05 18:57 Certbot with alternative certificate authority Jack Hill
2020-03-05 19:49 ` Jack Hill [this message]
2020-03-05 20:42   ` Jack Hill

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=alpine.DEB.2.20.2003051444230.19733@marsh.hcoop.net \
    --to=jackhill@jackhill.us \
    --cc=guix-devel@gnu.org \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).