dapper -> edgy -> feisty -> gutsy update fails
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| evms (Ubuntu) |
Invalid
|
Low
|
Unassigned | ||
Bug Description
Binary package hint: evms
Dear Colleagues
when I upgraded a root server from dapper lts to gutsy (via edgy feisty) all swap partitions were not recognized anymore, but locked by a not seen process.
All other partition (mdX) were running fine.
After fighting with this problem for some hours, Soren Hansen told me to remove evms* packages from gutsy.
It looks like that evms (even when it's not needed) will catch all unused partitions...
As Michael Vogt told me, this won't happen when someone is using release-
Tollef mentioned, that evms is being ran from initial initramfs during kernel boot...so we need something to make sure that this won't happen, when the user who is upgrading is not using evms at all.
Regards,
\sh
| Daniel T Chen (crimsun) wrote | #1 |
| Changed in evms: | |
| importance: | Undecided → Low |
| status: | New → Incomplete |
| Pedro Villavicencio (pedro) wrote | #2 |
| Changed in evms: | |
| status: | Incomplete → Invalid |
Now that we don't support dapper-> X (X != hardy), should we be adding Conflicts to a source package for hardy-updates?