From: Larsen <larsen007@web.de>
To: development@lists.ipfire.org
Subject: [PATCH] pakfire: Add information about probable causes when pakfire cannot connect
Date: Tue, 02 Jun 2015 23:19:56 +0200 [thread overview]
Message-ID: <op.xzmf7il2cahio0@honk.fritz.box> (raw)
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
Add information about probable causes when pakfire cannot connect. This includes port 11371 TCP and incorrect date/time settings.
Signed-off-by: Lars Schuhmacher <larsen007(a)web.de>
---
src/pakfire/lib/functions.pl | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/pakfire/lib/functions.pl b/src/pakfire/lib/functions.pl
index d14e031..127f63b 100644
--- a/src/pakfire/lib/functions.pl
+++ b/src/pakfire/lib/functions.pl
@@ -870,6 +870,7 @@ sub checkcryptodb {
unless ( "$ret" eq "0" ) {
message("CRYPTO WARN: The GnuPG isn't configured corectly. 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";
system("$command --recv-key $myid >> $Conf::logdir/gnupg-database.log 2>&1");
system("$command --recv-key $trustid >> $Conf::logdir/gnupg-database.log 2>&1");
next reply other threads:[~2015-06-02 21:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 21:19 Larsen [this message]
2015-06-02 21:55 ` Michael Tremer
[not found] <1433079387.3370.93.camel@ipfire.org>
2015-06-01 20:50 ` Larsen
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=op.xzmf7il2cahio0@honk.fritz.box \
--to=larsen007@web.de \
--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