From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: [PATCH] v3 .. Add epic5 irc client Date: Tue, 6 Dec 2016 19:35:37 +0000 Message-ID: <20161206193538.22496-1-ng0@libertad.pw> References: <87y41v6evk.fsf@we.make.ritual.n0.is> Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40074) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cELWu-0004xJ-BQ for guix-devel@gnu.org; Tue, 06 Dec 2016 14:35:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cELWr-0003Hq-1B for guix-devel@gnu.org; Tue, 06 Dec 2016 14:35:56 -0500 Received: from aibo.runbox.com ([91.220.196.211]:47421) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cELWq-0003HG-Qc for guix-devel@gnu.org; Tue, 06 Dec 2016 14:35:52 -0500 Received: from [10.9.9.210] (helo=mailfront10.runbox.com) by bars.runbox.com with esmtp (Exim 4.71) (envelope-from ) id 1cELWn-0000KW-ON for guix-devel@gnu.org; Tue, 06 Dec 2016 20:35:49 +0100 Received: from x5d83f1bd.dyn.telefonica.de ([93.131.241.189] helo=localhost) by mailfront10.runbox.com with esmtpsa (uid:892961 ) (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) id 1cELWf-000757-FU for guix-devel@gnu.org; Tue, 06 Dec 2016 20:35:41 +0100 In-Reply-To: <87y41v6evk.fsf@we.make.ritual.n0.is> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org Changes since the last patch (https://lists.gnu.org/archive/html/guix-devel/2016-10/msg00549.html): * removed gdbm * changed openssl to libressl (inline commented why) * explicitly pointed the config to the tls implementation * checked multiple networks for functionality, all work but... ... tls does not work when round robin of irc networks kick in. It might be a bug with epic5 -> ircd being used. For me this is functional, and I will get in contact with upstream developers (if they aren't using something like github or gitlab these days) to investigate this problem. epic5 is known to be difficult to configure, so I would not rule out an error on my side (not the package) in my client config. [PATCH] gnu: Add epic5.