Open marria05 opened 2 years ago
Just as an update. The same script, when run on a Debian Buster machine works as expected. The version of pyparted on this system is 3.11.2
.
Another update. I'm able recreate this in a vanilla Debian Bullseye VM using the Debian supplied python3-parted
package.
Just wanted to comment here and note that I will not be able to look in to this issue for a week or so. But thank you for the detailed report here. Please continue to post here if you have more details. If you are working on a fix, PRs are welcome too.
I've been asked to update an install script that I had written a couple of years to check that it still works correctly under the new(ish) version of Debian. On running it on a test machine, it appears the partition sizing no longer seems to work for me.
Using the demo file
make_one_primary_partition.py
(found in the examples directory), I can create a single partition that uses the entire disk.However, note the start and end positions for the partition don't seem to tally from the pyparted debug code and what
fdisk
is showing.If I modify the example to specify a specific size for the partition:
I get the following:
Am I doing something wrong? I had initially thought it might be the drive. But a test VM behaves in exactly the same manner. I don't have a Debian Buster machine to hand right now to confirm, otherwise I would try running it on that as well.
I was using the version of pyparted that came with install of Debian which appears to be
3.11.7
. I have, however tried upgrading to what appears to be the latest (3.20.0
), but that doesn't seem to have made any difference.