public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] pakfire - 'functions.pl': fixed typo
Date: Sun, 03 Dec 2017 14:16:16 +0100	[thread overview]
Message-ID: <20171203131616.24487-1-matthias.fischer@ipfire.org> (raw)

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

Just read this typo in a forum posting. Couldn't resist...

Best,
Matthias

Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
---
 src/pakfire/lib/functions.pl | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/pakfire/lib/functions.pl b/src/pakfire/lib/functions.pl
index cfb7e5117..5fe4cc4e6 100644
--- a/src/pakfire/lib/functions.pl
+++ b/src/pakfire/lib/functions.pl
@@ -904,7 +904,7 @@ sub checkcryptodb {
 	logger("CRYPTO INFO: Checking GnuPG Database");
 	my $ret = system("gpg --list-keys | grep -q $myid");
 	unless ( "$ret" eq "0" ) {
-		message("CRYPTO WARN: The GnuPG isn't configured corectly. Trying now to fix this.");
+		message("CRYPTO WARN: The GnuPG isn't configured correctly. Trying now to fix this.");
 		message("CRYPTO WARN: It's normal to see this on first execution.");
 		message("CRYPTO WARN: If this message is being shown repeatedly, check if time and date are set correctly, and if IPFire can connect via port 11371 TCP.");
 		my $command = "gpg --keyserver pgp.ipfire.org --always-trust --status-fd 2";
-- 
2.15.1


                 reply	other threads:[~2017-12-03 13:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20171203131616.24487-1-matthias.fischer@ipfire.org \
    --to=matthias.fischer@ipfire.org \
    --cc=development@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox