Hello,
I found a temporary solution to the problem:
Here are the steps:
aptitude remove zfs-dkms
aptitude install zfs-zed=2.2.3-1~bpo12+1 zfsutils-linux=2.2.3-1~bpo12+1 zfs-dkms=2.2.3-1~bpo12+1
aptitude install libnvpair3linux=2.2.3-1~bpo12+1 libzfs4linux=2.2.3-1~bpo12+1 libuutil3linux=2.2.3-1~bpo12+1 libzfs4linux=2.2.3-1~bpo12+1 libzpool5linux=2.2. 3-1~bpo12+1
aptitude install zfs-zed=2.2.3-1~bpo12+1 zfsutils-linux=2.2.3-1~bpo12+1
aptitude hold libnvpair3linux libuutil3linux libzfs4linux libzpool5linux zfs-dkms zfs-zed zfsutils-linux
After "locking" the packages, you should see this:
root@msrv 48.07℃ :~# apt-mark showhold
libnvpair3linux
libuutil3linux
libzfs4linux
libzpool5linux
zfs-dkms
zfs-zed
zfsutils-linux
systemctl enable --now zfs-scrub-weekly@ZPOOL.timer
systemctl enable --now zfs-trim-weekly@ZPOOL.timer - if the array is on SSD
It would be nice from the armbian team to fix things
Actually, the new versions of zfs-dkms and zfsutils-linux come from the armbian repo, and these packages look for the libssl3t64 package, which is not present in Debian Bookworm, but is present in Debian Sid.
I assume the Debian packages are compiled on top of Ubuntu, which is based on the Debian Sid.