unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Matthew James Kraai <kraai@ftbfs.org>
To: 57569@debbugs.gnu.org
Cc: Matthew James Kraai <kraai@ftbfs.org>
Subject: [bug#57569] [PATCH] Fix misspelling of GUIX_DIGITAL_OCEAN_TOKEN.
Date: Sat,  3 Sep 2022 16:55:30 -0700	[thread overview]
Message-ID: <20220903235530.4901-1-kraai@ftbfs.org> (raw)

* gnu/machine/digital-ocean.scm (maybe-raise-missing-api-key-error): Fix
  misspelling of GUIX_DIGITAL_OCEAN_TOKEN.
---
 gnu/machine/digital-ocean.scm | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/gnu/machine/digital-ocean.scm b/gnu/machine/digital-ocean.scm
index 90b66a54d9..3361cfe922 100644
--- a/gnu/machine/digital-ocean.scm
+++ b/gnu/machine/digital-ocean.scm
@@ -1,6 +1,7 @@
 ;;; GNU Guix --- Functional package management for GNU
 ;;; Copyright © 2019 Jakob L. Kreuze <zerodaysfordays@sdf.org>
 ;;; Copyright © 2020 Brice Waegeneire <brice@waegenei.re>
+;;; Copyright © 2022 Matthew James Kraai <kraai@ftbfs.org>
 ;;;
 ;;; This file is part of GNU Guix.
 ;;;
@@ -407,7 +408,7 @@ (define (maybe-raise-missing-api-key-error)
     (raise (condition
             (&message
              (message (G_ "No Digital Ocean access token was provided. This \
-may be fixed by setting the environment variable GUIX_DIGITAL_OCAEN_TOKEN to \
+may be fixed by setting the environment variable GUIX_DIGITAL_OCEAN_TOKEN to \
 one procured from https://cloud.digitalocean.com/account/api/tokens.")))))))
 
 (define (maybe-raise-unsupported-configuration-error machine)
-- 
2.37.2





             reply	other threads:[~2022-09-03 23:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-03 23:55 Matthew James Kraai [this message]
2022-09-04 15:09 ` bug#57569: [PATCH] Fix misspelling of GUIX_DIGITAL_OCEAN_TOKEN Mathieu Othacehe

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=20220903235530.4901-1-kraai@ftbfs.org \
    --to=kraai@ftbfs.org \
    --cc=57569@debbugs.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).