[Dev] cryptsetup-2.0.0-1 makes system unbootable.

[Andreas Grapentin]

This is the combination of 2 problems:

 first, kernel version 4.14.4 was broken, and we downgraded the repos to
 back to the latest 4.13 kernel to adress this issue

 secondly, and completely unrelatedly, arch pushed a major version updat
 to cryptsetup from 1.* to 2.0, which broke our systemd build. This has
 also been corrected through a rebuild of systemd.

So in theory, it should be safe again to upgrade.

Best,
Andreas

On Wed, Dec 13, 2017 at 10:48:42PM +0900, Attic Hermit wrote:
> 
> And this bug causes that the system can't mount encrypted storages
> either. I downgraded cryptsetup to 1.7.5-2, but some reason, the system
> fails with prompting "'bd_crypto_luks_open_blob' called, but not
> implemented!".
> 
> So I restore my system from a snapshot and downgraded completely.
> 
> -- 
> Attic Hermit
> _______________________________________________
> Dev mailing list
> Dev at lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/dev

-- 

------------------------------------------------------------------------------
my GPG Public Key:                 https://files.grapentin.org/.gpg/public.key
------------------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171214/f48f6c7f/attachment.sig>