./configure gives a "bad version string" for libparted 3.3 because it's not a "1.6.0" format #16
Comments
|
That is going to be fixed in v1.1.0. Thanks for reporting. |
ya-mouse
added a commit
that referenced
this issue
Apr 5, 2020
- drop support for libparted older than 2.4 (#16) - introduce `-n, --partition` to set a partition number when dealing with file dumps, /dev/loop and /dev/ram devices (#15) - ask confirmation for operations (e.g. FAT32 -> FAT16 conversion), add `-f, --force` option to not prompt (#13) - do not limit FAT32 usage on small partitions (#11) - update changelog (#10)
ya-mouse
added a commit
that referenced
this issue
Apr 5, 2020
Grand update: - drop support for libparted older than 2.4 (#16) - introduce `-n, --partition` to set a partition number when dealing with file dumps, /dev/loop and /dev/ram devices (#15) - ask confirmation for operations (e.g. FAT32 -> FAT16 conversion), add `-f, --force` option to not prompt (#13) - do not limit FAT32 usage on small partitions (#11) - update changelog (#10)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Temporary solution is to insert a
return 0;to line 4795 to skip this check.The text was updated successfully, but these errors were encountered: