| What | Removed | Added |
|---|---|---|
| CC | ancor@suse.com |
Created attachment 751331 [details] YaST logs Our first though was that this was happening because the values for minimum sizes in control.xml were not properly adapted to yast-storage-ng (see [1] for more details). But I reproduced this and it really looks like the new proposal miscalculates stuff regarding how much the Windows partition must be resized. I'm attaching logs of my attempt. So this is a legitimate bug in the new proposal code, not just a lack of adjustment in control.xml (is still true that we need to adapt control.xml, but that's a different story). [1] https://github.com/yast/yast-storage-ng/blob/master/doc/old_and_new_proposal.md