Added information about probable causes when pakfire cannot connect

Added information about probable causes when pakfire cannot connect

[Larsen]

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

I came across a problem where pakfire couldn´t connect and showed the  
following message again and again:

CRYPTO WARN: The GnuPG isn't configured corectly. Trying now to fix this.
CRYPTO WARN: It's normal to see this on first execution.
server-list.db       100.00% |=============================>|   985.00 B
DOWNLOAD ERROR: The downloaded file (2.17/lists/server-list.db) wasn't  
verified by IPFire.org. Sorry - Exiting...


I solved this by opening port 11371 after spending some time to find that  
solution. Therefore, I created a patch that gives the user some advice  
what could be wrong if that message returns repeatedly.


Lars

[-- Attachment #2: pakfire_additional_info.patch --]
[-- Type: application/octet-stream, Size: 876 bytes --]

 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");