From mboxrd@z Thu Jan 1 00:00:00 1970 From: Larsen To: development@lists.ipfire.org Subject: [PATCH] pakfire: Add information about probable causes when pakfire cannot connect Date: Mon, 01 Jun 2015 22:50:07 +0200 Message-ID: In-Reply-To: <1433079387.3370.93.camel@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0106093180408913428==" List-Id: --===============0106093180408913428== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Add information about probable causes when pakfire cannot connect. This includes port 11371 TCP and incorrect date/time settings. Signed-off-by: Lars Schuhmacher --- 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"); --===============0106093180408913428==--