Bug#591626: Unable to boot from encrypted Luks volume after upgrade
reassign 591626 cryptsetup
severity 591626 important
thanks
Hi,
On Wed, Aug 04, 2010 at 08:03:35PM +1000, Jiri Kanicky wrote:
> Package: apt
This is not likely to be the fault of apt. Reassigning to cryptsetup, to
be triaged there and possibly passed on to the real culprit. Also,
lowering severity as this sounds like an isolated case, that is, there
is something special on your system that causes the upgrade process to
fail rather than a general problem with the system.
Obviously this bug still needs to be addressed, possibly by adding
another check in some script, but it is by no means "critical".
> Version: 0.7.25.3
That is the testing/unstable version. Please be aware that unstable
breaks occasionally and if you use it, you are expected to be able to
repair your system (as you've done). If you are using testing and am
getting this bug, then it is obvious that noone else has seen it in the
ten days that it took the package to reach testing, so it is likely to
be a local configuration problem (probably said "N" when asked for some
configuration file upgrade).
> I am not able to boot from my encrypted LUKS volume everytime after I upgrade (apt-get upgrade).
Everytime, or only after specific packages are upgraded? If possible,
can you check the log files which packages were part of the upgrade when
the problem occured?
> PS to Developers:
> Please test things more! Lately there are more things broken then fixed.
Generally, unstable is expected to be tested on the developer's own
machine, and testing on several thousand machines. If something slips
through here, then it is usually a corner case that is triggered only in
very specific circumstances.
Simon
Reply to: