From mboxrd@z Thu Jan  1 00:00:00 1970
From: Leo Famulari <leo@famulari.name>
Subject: Re: gnutls 'name-constraints' test failure
Date: Tue, 19 Jul 2016 13:05:35 -0400
Message-ID: <20160719170535.GA17723@jasmine>
References: <578A854F.30302@cock.li> <20160717073206.GA17182@jasmine>
	<87shv84crp.fsf@gnu.org> <20160717173334.GA2626@jasmine>
	<20160718164855.GA3227@jasmine> <20160718171552.GA20926@jasmine>
	<87shv5kch6.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="PEIAKu/WMn1b1Hv9"
Content-Transfer-Encoding: 8bit
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48912)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <leo@famulari.name>) id 1bPYSs-0003DF-6n
	for guix-devel@gnu.org; Tue, 19 Jul 2016 13:05:51 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <leo@famulari.name>) id 1bPYSn-0005cG-W0
	for guix-devel@gnu.org; Tue, 19 Jul 2016 13:05:49 -0400
Content-Disposition: inline
In-Reply-To: <87shv5kch6.fsf@gnu.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Ludovic =?iso-8859-1?Q?Court=E8s?= <ludo@gnu.org>
Cc: guix-devel@gnu.org


--PEIAKu/WMn1b1Hv9
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

On Tue, Jul 19, 2016 at 03:02:13PM +0200, Ludovic Courtès wrote:
> So GnuTLS already doesn’t build on core-updates, right?  In that case,
> we should go ahead an update it.

I built 3.5.2 on master, but now there is another test failure,
'testdsa'. I've attached the log.

It appears that the test requires a `netstat` available. Does GnuTLS
mock network access somehow?

Unfortunately, I have to go AFK for ~12 hours. Maybe somebody else can
look at it?

--PEIAKu/WMn1b1Hv9
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="test-suite.log"

============================================
   GnuTLS 3.5.2: tests/dsa/test-suite.log
============================================

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: testdsa
=============

Checking various DSA key sizes (port )
Checking DSA-1024 with TLS 1.0
./testdsa: line 55: netstat: command not found
./../scripts/common.sh: line 73: netstat: command not found
./../scripts/common.sh: line 54: netstat: command not found
./../scripts/common.sh: line 57: netstat: command not found
try 1
./../scripts/common.sh: line 54: netstat: command not found
./../scripts/common.sh: line 57: netstat: command not found
try 2
./../scripts/common.sh: line 54: netstat: command not found
./../scripts/common.sh: line 57: netstat: command not found
try 3
./../scripts/common.sh: line 54: netstat: command not found
./../scripts/common.sh: line 57: netstat: command not found
try 4
./../scripts/common.sh: line 54: netstat: command not found
./../scripts/common.sh: line 57: netstat: command not found
try 5
./../scripts/common.sh: line 54: netstat: command not found
./../scripts/common.sh: line 57: netstat: command not found
try 6
Server 35835 did not come up


--PEIAKu/WMn1b1Hv9--