-
Notifications
You must be signed in to change notification settings - Fork 136
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
The MBR extended implementation causes a problem with a non-MBR configuration #473
Comments
sjoerdsimons
added a commit
to sjoerdsimons/debos
that referenced
this issue
Jan 20, 2024
The extended partition handling for msdos accidentally got applied to all partition types. Ensure and be more defensive against msdos special handling getting applied to other partition types Fixes: go-debos#473
sjoerdsimons
added a commit
to sjoerdsimons/debos
that referenced
this issue
Jan 20, 2024
The extended partition handling for msdos accidentally got applied to all partition types. Ensure and be more defensive against msdos special handling getting applied to other partition types Fixes: go-debos#473
Thank you I tested that patch and the same |
Thanks for testing! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi I don't know enough about the project yet to know how to create a minimal reproducible example, but when i use this file with
debos
, if I use commit 03ec3cb ofdebos
it works but if I use commit da773cc or any of the recent commits after that, thedebos
command gets stuck inside the fakemachine because of a partition named "extended" getting incorrectly created in the wrong place even though the.yaml
file specifiesgpt
and notmbr
If I have time I will try to create a minimal reproducible example
The text was updated successfully, but these errors were encountered: