I can verify that the build in xenial-proposed resolves this bug using the example config attached.
Running an installation using curtin packed on a system with the current curtin release in xenial-updates installation fails. Curtin release: root@tmp:/tmp# apt-cache policy curtin curtin: Installed: 0.1.0~bzr399-0ubuntu1~16.04.1 Candidate: 0.1.0~bzr399-0ubuntu1~16.04.1 Failure: Unexpected error while running command. Command: ['mkfs.xfs', '-s', '1', '-f', '/dev/vdb2'] Exit code: 1 Reason: - Stdout: '' Stderr: 'unknown option -s 1\nUsage: mkfs.xfs\n/* blocksize */\t\t[-b log=n|size ...
When curtin is packed with the release in proposed, installation works
Curtin release: curtin: Installed: 0.1.0~bzr425-0ubuntu1~16.04.1 Candidate: 0.1.0~bzr425-0ubuntu1~16.04.1
I can verify that the build in xenial-proposed resolves this bug using the example config attached.
Running an installation using curtin packed on a system with the current curtin release in xenial-updates installation fails. 0ubuntu1~ 16.04.1 0ubuntu1~ 16.04.1
Curtin release:
root@tmp:/tmp# apt-cache policy curtin
curtin:
Installed: 0.1.0~bzr399-
Candidate: 0.1.0~bzr399-
Failure:
Unexpected error while running command.
Command: ['mkfs.xfs', '-s', '1', '-f', '/dev/vdb2']
Exit code: 1
Reason: -
Stdout: ''
Stderr: 'unknown option -s 1\nUsage: mkfs.xfs\n/* blocksize */\t\t[-b log=n|size
...
When curtin is packed with the release in proposed, installation works
Curtin release: 0ubuntu1~ 16.04.1 0ubuntu1~ 16.04.1
curtin:
Installed: 0.1.0~bzr425-
Candidate: 0.1.0~bzr425-