Comment 4 for bug 506971

> ubiquity doesn't pay a great deal of attention to the type
> fields in the partition table, but it does pay attention to
> the partition contents, which tend to be more meaningful
> these days. Could you please verify what's actually in the
> partitions in question?

Unfortunately I had to overwrite that SD card in the meantime.

The reason why the partitions didn't match their content was because I generally pre-partition my SD card in a precise way to make space for boot images; ubiquity doesn't provide the precision I want and can't itself install boot images to the target medium on imx51 (armel). This pre-partitioning results in ubiquity seeing partitions which are uninitialised and so their contents may not match the type fields in the partition table; indeed it is a mistake to interpret the contents of an unitialised partition, but ubiquity has no way to know this.

Of course, the partition types can be overriden now that the bug which was preventing partition creation was fixed.

So maybe there is no bug; it's more a case of the intended behaviour not being what I expect.

If I experience the bug again, I'll try your parted command to see what that generates.