Activity log for bug #47055
Date | Who | What changed | Old value | New value | Message |
---|---|---|---|---|---|
2006-05-28 09:04:55 | Krzysztof Lichota | bug | added bug | ||
2006-05-28 09:05:53 | Krzysztof Lichota | bug | added attachment 'syslog' (syslog) | ||
2006-05-28 09:06:22 | Krzysztof Lichota | bug | added attachment 'partman' (partman log) | ||
2006-05-28 09:07:52 | Krzysztof Lichota | bug | added attachment 'partitioning-wrong-extened-partition.png' (Screenshot of qtparted with partition layout) | ||
2006-05-28 16:12:10 | Colin Watson | ubiquity: severity | Normal | Minor | |
2006-05-28 16:12:10 | Colin Watson | ubiquity: statusexplanation | |||
2008-07-31 17:32:09 | seisen1 | ubiquity: status | New | Invalid | |
2008-07-31 19:20:51 | seisen1 | ubiquity: status | Invalid | Incomplete | |
2008-09-14 19:04:08 | Colin Watson | ubiquity: status | Incomplete | Fix Released | |
2008-09-14 19:04:08 | Colin Watson | ubiquity: statusexplanation | This is fixed, after a fashion. The partitioner no longer offers the opportunity to explicitly create an extended partition; you can create primary or logical partitions, and it will do whatever it needs to do in terms of extended partitions. Thus there is no longer a conflict between an explicit user request and what the partitioner does. I don't plan to restore the ability to explicitly lay out extended partitions. It isn't necessary in an installer context, and as I noted it is trivial to resize extended partitions provided that there is some adjacent unpartitioned space. I have never heard of a real case where this caused a problem for automatic or OEM installations, and I've dealt with a lot of those. |