-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support mmdebstrap's --format
option
#4
Comments
For context, the reason I wanted to specify the format was because my goal was ext4, not ext2. When I run mmdebstrap, I have it create an ext2 file named That filename doesn't end in ".ext2", so it only works when specifying the format manually. Also, that |
Bug: #4 Signed-off-by: Benjamin Drung <[email protected]>
Thanks for reporting this bug. I have pushed a fix in the Sadly the Have you filed a bug for |
No. I was just thinking out loud. I'm not even sure it would be within the scope of mmdebstrap. It's easy enough to put it in a script that runs after mmdebstrap/bdebstrap finishes, after all. |
I tested the format branch, and it worked as expected. I updated my config to say: format: ext2
target: rootfs Then ran: and the result worked perfectly.
Thanks for the quick fix! |
Bug: #4 Signed-off-by: Benjamin Drung <[email protected]>
Merged the fix to main and released bdebstrap 0.5.0. |
Hi,
I like the idea of bdebstrap, so I tried it out today. However, it doesn't seem to capture my usage of mmdebstrap.
I tried to put my mmdebstrap parameters into a yaml format and run it with bdebstrap, and found that the --format parameter is not supported as a yaml key. I tried this input:
And I got this output:
The parameter exists, and it works when I run mmdebstrap directly. Here's the mmdebstrap documentation. Is it possible for bdebstrap to pass it through somehow?
I was expecting it to run something similar to this:
Thanks!
The text was updated successfully, but these errors were encountered: