pakfire: Add information about probable causes when pakfire cannot connect
Message ID | op.xzkj5tm1cahio0@honk.fritz.box |
---|---|
State | Superseded |
Headers |
Return-Path: <development-bounces@lists.ipfire.org> Received: from mail01.ipfire.org (mail01.tremer.info [172.28.1.200]) by septima.ipfire.org (Postfix) with ESMTP id 7F15F60741 for <patchwork@ipfire.org>; Mon, 1 Jun 2015 22:50:38 +0200 (CEST) Received: from hedwig.ipfire.org (localhost [IPv6:::1]) by mail01.ipfire.org (Postfix) with ESMTP id 568734BDD; Mon, 1 Jun 2015 22:50:38 +0200 (CEST) Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=212.227.17.11; helo=mout.web.de; envelope-from=larsen007@web.de; receiver=development@lists.ipfire.org Received: from mout.web.de (mout.web.de [212.227.17.11]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPS id A13C24B62 for <development@lists.ipfire.org>; Mon, 1 Jun 2015 22:50:26 +0200 (CEST) Received: from honk.fritz.box ([2.240.9.62]) by smtp.web.de (mrweb102) with ESMTPSA (Nemesis) id 0Lx7Mz-1ZAeXA3DSL-016ii9 for <development@lists.ipfire.org>; Mon, 01 Jun 2015 22:50:25 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "development@lists.ipfire.org" <development@lists.ipfire.org> References: <op.xzf32oztcahio0@honk.fritz.box> <1433079387.3370.93.camel@ipfire.org> Date: Mon, 01 Jun 2015 22:50:07 +0200 Subject: [PATCH] pakfire: Add information about probable causes when pakfire cannot connect MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Larsen <larsen007@web.de> Message-ID: <op.xzkj5tm1cahio0@honk.fritz.box> In-Reply-To: <1433079387.3370.93.camel@ipfire.org> User-Agent: Opera Mail/12.17 (Win32) X-Provags-ID: V03:K0:P/axTC/ysvrA7UJdMSXrCS35ysS2Q/W+rF8f8G4I0XQIolE/y1f JjXDeO2yXbV3r5rHkWsLJpavrxwS5NRNMPeve0Yv0QOPxnE73zCWbaQTBQ/EdI4oRmGkV2t vASGk6XzHJe1MPXbQVgc1FdGh/EqpSwX0Q7bXYP2S5SYlr4qcWik+BBFZ46tPpB2W/OXAXW JWqteSHZh4a2cBAvEEF0A== X-UI-Out-Filterresults: notjunk:1; X-BeenThere: development@lists.ipfire.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: IPFire development talk <development.lists.ipfire.org> List-Unsubscribe: <http://lists.ipfire.org/mailman/options/development>, <mailto:development-request@lists.ipfire.org?subject=unsubscribe> List-Archive: <http://lists.ipfire.org/pipermail/development/> List-Post: <mailto:development@lists.ipfire.org> List-Help: <mailto:development-request@lists.ipfire.org?subject=help> List-Subscribe: <http://lists.ipfire.org/mailman/listinfo/development>, <mailto:development-request@lists.ipfire.org?subject=subscribe> Errors-To: development-bounces@lists.ipfire.org Sender: "Development" <development-bounces@lists.ipfire.org> |
Message
Lars Schuhmacher
June 2, 2015, 6:50 a.m. UTC
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(+)
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");