https://bugzilla.suse.com/show_bug.cgi?id=1231363 https://bugzilla.suse.com/show_bug.cgi?id=1231363#c4 Ancor Gonzalez Sosa <ancor@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor@suse.com --- Comment #4 from Ancor Gonzalez Sosa <ancor@suse.com> --- There are several things to clarify. (In reply to Jan Engelhardt from comment #2)

That, or the 'at least 17.5' is too generous, in the sense it should be 'at least 1.6 GB' (size reported under "Software" notebook page).

Let's start here. The minimum required size for each filesystem is hardcoded for the "product" (Leap, in this case). It is not calculated from the software selection. That was also the case for Leap 15.X and YaST. The size limits for Leap likely need to be adjusted at Agama. Now they are here: https://github.com/agama-project/agama/blob/master/products.d/leap_160.yaml#... That says: - For root use at least 5GiB (17.5GiB is Btrfs snapshots are used) - For swap use at least the RAM size or 1GiB That's what the UI reflects. I personally would start de-activating the "enlarge to RAM" feature of the swap since that's controversial and I would not expect anyone to try Leap 16.0 on real hardware for now.

Deleting the swap partition reveals that "at least 17.5" translates to "19.99" for some reason - and then fits the disk exactly.

Well, "at least 17.5 GiB" translates to 19.99 GiB... because that's the available size. If you want to create a single partition of "at least 17 GiB" in a disk of X size (for X > 17 GiB), I expect you end up with a partition of size X. Why is that hard to understand? It's a matter of wording?

Expected Results: Propose something that fits in 20 GB.

Well. We are trying to change the approach with Agama compared to YaST (not written in stone yet, just playing with the concept). YaST started with the same requisites (17.5 GiB for "/" and a swap as big as the RAM). If it was not possible to make a proposal with those requirements, it re-tried several time relaxing the requisites (smaller RAM so loosing ability to suspend, disabling snapshots so "/" could be smaller, and so on). In the end, it was able to propose an initial setup... but the feature set of the operating system (snapshots, suspend, separate home...) changed without user interaction. In these initial versions of Agama we are trying with a different approach in which the user has to explicitly disable the auto-swap and/or snapshots in order to adjust requirements and then fit on the disk. As said, nothing is set in stone and we still need to think how to expose all that usability-wise. -- You are receiving this mail because: You are on the CC list for the bug.