And I don't see anything like this in source and patches (maybe I'm wrong, but it's hidden)
To be more precise, I do my own package (parted 3.1, a future ppa will come) and I _really_ see different when use with ubuntu-vm-builder :
In the current case, I have a disk with 4k block, my partition is 512 align and my VM is 512 align! (you see the problem I hope)
I understand the problem with 2 different versions. But when you see the parted changelog, it's unbelievable to keep an old / patchy version of somethings so central in a Linux distribution (and to see fedora with 3.1 and debian with 2.3 while it's a debian project...)
sorry but the commit who activate the 1M alignment is this one : http:// git.savannah. gnu.org/ cgit/parted. git/commit/ ?id=c749046a54d 983f74f8156c0ae a71b0995b9477d
And I don't see anything like this in source and patches (maybe I'm wrong, but it's hidden)
To be more precise, I do my own package (parted 3.1, a future ppa will come) and I _really_ see different when use with ubuntu-vm-builder :
In the current case, I have a disk with 4k block, my partition is 512 align and my VM is 512 align! (you see the problem I hope)
Here is for example a (bad) workaround : http:// bazaar. launchpad. net/~guilhem- fr/vmbuilder/ parted/ revision/ 484
I understand the problem with 2 different versions. But when you see the parted changelog, it's unbelievable to keep an old / patchy version of somethings so central in a Linux distribution (and to see fedora with 3.1 and debian with 2.3 while it's a debian project...)