Swâmi> I could temporarily work around this by manually copying
Swâmi> libgcrypt.so.11.2.3 and libgpg-error.so.0.3.0 to /lib, with
Swâmi> their symlinks, but this is not a satisfactory solution.
I have now gone even further, I copied the statically linked
executable from http://luks.endorphin.org/dm-crypt and started to use
that, now.
Swâmi> I'm dissatisfied seeing that this bug importance is yet set
Swâmi> to "medium" as this can prevent a system from booting ; I
Swâmi> feel that solving this should be high priority so it
Swâmi> doesn't hit too many people in the face (those who haven't
Swâmi> upgraded Feisty => Gutsy yet but may soon do...). IMHO,
Swâmi> this bug is critical.
I completely agree, this *is* critical. To say that loud and clear, if
you are currently in Feisty and have encrypted partitions for which
you need cryptsetup,
DON'T UPGRADE TO GUTSY
unless you think you master this bug. In particular, keep a live cd
arround.
>>>>> ``Swâmi'' == Swâmi Petaramesh <email address hidden> writes:
Swâmi> I could temporarily work around this by manually copying error.so. 0.3.0 to /lib, with
Swâmi> libgcrypt.so.11.2.3 and libgpg-
Swâmi> their symlinks, but this is not a satisfactory solution.
I have now gone even further, I copied the statically linked luks.endorphin. org/dm- crypt and started to use
executable from http://
that, now.
Swâmi> I'm dissatisfied seeing that this bug importance is yet set
Swâmi> to "medium" as this can prevent a system from booting ; I
Swâmi> feel that solving this should be high priority so it
Swâmi> doesn't hit too many people in the face (those who haven't
Swâmi> upgraded Feisty => Gutsy yet but may soon do...). IMHO,
Swâmi> this bug is critical.
I completely agree, this *is* critical. To say that loud and clear, if
you are currently in Feisty and have encrypted partitions for which
you need cryptsetup,
DON'T UPGRADE TO GUTSY
unless you think you master this bug. In particular, keep a live cd
arround.
Jens