I'm the author of GPT fdisk, and I intend to release a version 1.0.8 with this fix within a day or two. The only major change since 1.0.7 is the MR linked by Christian above. If patching earlier versions of GPT fdisk, then the following commit should be included, too:
This commit fixes a matching problem on reading data. If both are uncorrected, then it looks like it's working, but the partition name is written in the wrong byte order on big-endian systems; and if one fix is applied without the other, then a partition name written by GPT fdisk will appear garbled when read back by GPT fdisk, and there may be compatibility problems with other programs.
I'm the author of GPT fdisk, and I intend to release a version 1.0.8 with this fix within a day or two. The only major change since 1.0.7 is the MR linked by Christian above. If patching earlier versions of GPT fdisk, then the following commit should be included, too:
https:/ /sourceforge. net/p/gptfdisk/ code/ci/ 86dd5fea351a5a5 5bea26b7622eb85 ebd6075a60/
This commit fixes a matching problem on reading data. If both are uncorrected, then it looks like it's working, but the partition name is written in the wrong byte order on big-endian systems; and if one fix is applied without the other, then a partition name written by GPT fdisk will appear garbled when read back by GPT fdisk, and there may be compatibility problems with other programs.
This affects only big-endian systems.