From: Milan Broz <mbroz@redhat.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] "ERROR:apitest failed" after make check cryptsetup 1.1.0
Date: Wed, 28 Apr 2010 12:17:32 +0200 [thread overview]
Message-ID: <4BD80B3C.90307@redhat.com> (raw)
In-Reply-To: <20100428091338.DC90815F01D@c-in3ws--03-03.sv2.lotusliveops.com>
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
next prev parent reply other threads:[~2010-04-28 10:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 9:13 [dm-crypt] "ERROR:apitest failed" after make check cryptsetup 1.1.0 Si St
2010-04-28 10:17 ` Milan Broz [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-30 9:47 Si St
2010-04-28 16:18 Si St
2010-04-28 16:09 Si St
2010-04-29 17:10 ` Milan Broz
2010-04-28 15:56 Si St
2010-04-28 16:07 ` Felix Blanke
2010-04-27 19:13 Si St
2010-04-27 19:38 ` Milan Broz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BD80B3C.90307@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox