From: Geza Bohus <gbohus@yahoo.com>
To: Milan Broz <gmazyland@gmail.com>, cryptsetup@lists.linux.dev
Subject: Re: cryptsetup: /lib/arm-linux-gnueabihf/libcryptsetup.so.12: version `CRYPTSETUP_2.4' not found error
Date: Mon, 4 Apr 2022 18:41:05 +0200 [thread overview]
Message-ID: <etPan.624b1fa6.52ad5a2e.74ce@yahoo.com> (raw)
In-Reply-To: <2bdc84bb-de25-3a07-450d-0001a602030c@gmail.com>
Hi Milan,
Thanks for your reply. Of course I saw the problem with the versions, I just don't understand how it can require a newer version than what apt claims to be the latest.
If I understand correctly, you're suggesting to do
sudo apt install cryptsetup
Right?
Thanks,
Geza
On 2022. April 4. at 18:26:56, Milan Broz (gmazyland@gmail.com (mailto:gmazyland@gmail.com)) wrote:
>
> On 04/04/2022 18:08, Geza Bohus wrote:
> ...
>
> > I have installed cryptsetup-2.4.3 as described here:
> ...
> >
> > apt claims that I have the newest version, v2.3.7:
>
> Do you see the difference in versions?
>
> You just cannot have old libcryptsetup with a new command line tool.
>
> Either install everything from the distro repository, or install everything directly from upstream,
> but you cannot combine versions this way.
> (Here new commandline tools depend on new API calls that are not in the old libceryptsetup.)
>
> Better do not compile it yourself, use distro provided versions.
>
> Milan
next prev parent reply other threads:[~2022-04-04 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <etPan.624b1819.7c3954eb.74ce.ref@yahoo.com>
2022-04-04 16:08 ` cryptsetup: /lib/arm-linux-gnueabihf/libcryptsetup.so.12: version `CRYPTSETUP_2.4' not found error Geza Bohus
2022-04-04 16:26 ` Milan Broz
2022-04-04 16:41 ` Geza Bohus [this message]
2022-04-04 17:07 ` Milan Broz
2022-04-04 17:31 ` Geza Bohus
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=etPan.624b1fa6.52ad5a2e.74ce@yahoo.com \
--to=gbohus@yahoo.com \
--cc=cryptsetup@lists.linux.dev \
--cc=gmazyland@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.