From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mbroz@redhat.com>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
	by mail.saout.de (Postfix) with ESMTP
	for <dm-crypt@saout.de>; Wed, 28 Apr 2010 12:17:35 +0200 (CEST)
Received: from int-mx01.intmail.prod.int.phx2.redhat.com
	(int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11])
	by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o3SAHYwG005324
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
	for <dm-crypt@saout.de>; Wed, 28 Apr 2010 06:17:34 -0400
Received: from [10.36.5.196] (vpn1-5-196.ams2.redhat.com [10.36.5.196])
	by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP
	id o3SAHWIV002582
	for <dm-crypt@saout.de>; Wed, 28 Apr 2010 06:17:33 -0400
Message-ID: <4BD80B3C.90307@redhat.com>
Date: Wed, 28 Apr 2010 12:17:32 +0200
From: Milan Broz <mbroz@redhat.com>
MIME-Version: 1.0
References: <20100428091338.DC90815F01D@c-in3ws--03-03.sv2.lotusliveops.com>
In-Reply-To: <20100428091338.DC90815F01D@c-in3ws--03-03.sv2.lotusliveops.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] "ERROR:apitest failed" after make check cryptsetup
 1.1.0
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
	<mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
	<mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

On 04/28/2010 11:13 AM, Si St wrote:
> "can you try svn snapshot first - does it work?"
> What do you mean by "svn Snapshot"?

I meant current devel code
http://code.google.com/p/cryptsetup/source/checkout

(you have to run autoconf there. Or wait few days for 1.1.1 release)


> Don't understand the expression, I am probably a too weak newbie in this game.
> 
> I have by the way ended all attemps of make install until it is 100%. I dont dare to mess up my SLED10,
> but in case I later should or ought to update I will do it on Your recommendation. So far the cryptsetup 1.0.3 works fine and smooth for me.

I have no access to SLED10 currently, but it is possible that only test is broken
because of unsupported IV option - can you try this change?

http://code.google.com/p/cryptsetup/source/diff?spec=svn201&r=201&path=/trunk/tests/apitest.c

The test were written primarily for maintainers, so it is quite possible that it fails on some old system,
but I'll try to fix them in next release.

Milan