public inbox for cryptsetup@lists.linux.dev
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: Geza Bohus <gbohus@yahoo.com>,
	cryptsetup development <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 19:07:14 +0200	[thread overview]
Message-ID: <60fd4577-2409-5d5a-a615-b1b65c0f5fc8@gmail.com> (raw)
In-Reply-To: <etPan.624b1fa6.52ad5a2e.74ce@yahoo.com>

On 04/04/2022 18:41, Geza Bohus wrote:
>   
> 
> 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

Basically, yes.

You have somewhere in PATH new cryptsetup tool, but in lib dir old libcryptsetup.

(If you installed it manually, it can by in various non-standard locations, so
the best is check "which cryptsetup" (or "type -p cryptsetup") and remove it
from there manually, then reinstall the version from your distribution.

Usually we are backward compatible, but it is really not a good idea to combine
different version of libcryptsetup and cryptsetup.

(IOW what you see is the "correct" error caused by library symbols versioning
to prevent a malfunction :-)

Milan

  reply	other threads:[~2022-04-04 17:07 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
2022-04-04 17:07       ` Milan Broz [this message]
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=60fd4577-2409-5d5a-a615-b1b65c0f5fc8@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=cryptsetup@lists.linux.dev \
    --cc=gbohus@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox