Summary: | sys-fs/cryptsetup-1.0.4 with 1.0.3 config-file destroys partitions | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andreas Dehmel <zarquon> |
Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | critical | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andreas Dehmel
2007-10-21 13:50:20 UTC
<snip> ewarn "This ebuild introduces a new set of scripts and configuration" ewarn "then the previous system. If you are currently using /etc/conf.d/crypfs" ewarn "then you *MUST* read the new /etc/conf.d/cryptfs for instructions" ewarn "on how to convert your previous cryptfs to the new syntax or your" ewarn "encrypted partitions will *NOT* work." </snip> So, how about that you actually *read* what we told you, and run etc-update, as told to after upgrade by portage? I know it says that in the log. But I also said that "not work" means "doesn't mount" and _not_ "destroys partitions". Even if it did mention that possibility in the elog, it'd still be a critical error because both the log message and the change of keyword are far too easy to overlook and you have just one chance to get it right, afterwards the partition is corrupted. Do you really think anybody would accept a change like this in fstab, regardless of whether you log out a warning or not? Fat chance. Ignoring all the warnings and provided instructions is not an ebuild bug, sorry. If you dislike how cryptsetup-luks behaves on broken config file, take it upstream, not to Gentoo bugzilla. |