Vacation - status of partman-crypto / cryptsetup
Hi all,
I'll be leaving on Wednesday afternoon for a two week vacation (i.e. Dec
20 -> Jan 4) and I'll have limited Internet connectivity during that
time (and I will not have access to a devel machine).
So I thought it'd be a good idea to give a brief status update on bugs
that are somehow related to me considering the impending Etch release:
====
o Cryptsetup
#403075 - unreproducible and not that serious (normal users have no
reason to use cryptsetup anyway)
#398429 - which is a dummy bug that depends on #398302, if this bug is
fixed, resume from an encrypted swap partition should work.
The fixed klibc-utils is in unstable, there is one report in
#398302 that it doesn't work but I'm not able to reproduce.
The rest of the bugs are wishlist type bugs.
Conclusion: provided that the two reports above are indeed
unreproducible, that 2:1.0.4+svn16-2 in unstable migrates to
testing, and that klibc-utils >= 1.4.30-2 migrates, cryptsetup should
be fine.
=====
o partman-crypto
There are two problems that I know of that affects partman-crypto:
1) crypto devices cannot be deallocated once setup, without this, it's
not possible to e.g. run the guided partitioning twice if the first
round was with partman-auto-crypto.
I've written a patch for this and submitted it to #396023. It's quite
invasive though, and FJP regarded it as a post-Etch thing (and I agree)
2) crypto-on-md doesn't work (see #393728 and its two dupes). I've
written a patch for this as well, and its not very invasive, but it's
not clear whether it'll break something else. The only way to find
out would be through testing, which is a bit late to do.
Summary: two post-Etch issues which should be documented in the Etch d-i
errata (I haven't checked whether that has been done already to be
honest).
====
These are the issues that I'm aware of and that seemed important enough
to warrant mentioning.
So, overall, things are shaping up for a fine release. Happy holidays
everyone. Feel free to mail me over any issues but don't expect quick
answers...
--
David Härdeman
Reply to: