Okay, this looked much better. I was still not able to apply the patch right away, but I am also not sure what the reason for that was here.

It's merged now. Thank you.

-Michael

On Tue, 2015-06-02 at 23:19 +0200, Larsen wrote:

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