agama 16.1 installer demands seriously excessive disk space on / to custom install

[mrmazda]

Original Summary:
agama 16.1 installer demands seriously excessive disk space on / to custom install

I booted https://download.opensuse.org/repositories/systemsmanagement:/Agama:/Devel/images_Leap_16.1/iso/agama-installer.x86_64-Leap_16.1.iso in order to test install the current state of 16.1, only to find it wouldn't let me choose my intended (pre-formatted) partition target:

# parted -l
Model: ATA APPLE HDD ST1000 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name                        Flags
 1      20.5kB  210MB   210MB   fat32        EFI System Partition        boot, esp
 2      210MB   80.2GB  80.0GB               p02 MacOS Catalina system
 3      80.2GB  300GB   220GB                p03 MacOS user data         msftdata
 4      300GB   309GB   8389MB  ext4         p04 Linux /usr/local
 5      309GB   326GB   16.8GB  ext4         p05 Linux /home
 6      326GB   351GB   25.2GB  ext4         p06 Linux /pub
 7      351GB   363GB   12.6GB  ext4         p07 openSUSE Tumbleweed
 8      363GB   376GB   12.6GB  ext4         p08 openSUSE 15.6
 9      376GB   389GB   12.6GB  ext4         p09 openSUSE 16.1
10      389GB   401GB   12.6GB  ext4         p10 openSUSE 16.0
11      401GB   779GB   377GB                reserved for more distros
12      779GB   1000GB  222GB   ext4         Apple ST10 Linux /isospace
# df
Filesystem     1K-blocks    Used Available Use% Mounted on
/dev/sda7       11999536 5069504   6299248  45% /
/dev/sda5       16021424     132  16004908   1% /home
/dev/sda4        7979908 1056000   6825604  14% /usr/local
/dev/sda6       24014052 2661364  21336304  12% /pub
/dev/sda1         201633     310    201323   1% /boot/efi
/dev/sda8       11999536 2998848   8369904  27% /disks/s156
/dev/sda9       11999536    2072  11366680   1% /disks/s161
/dev/sda10      11999536 3213164   8155588  29% /disks/s160

My target for 16.1 is #9, which is 50% larger than the usual maximum size I allocate to a / filesystem. Normally I allocate 8G, which would still be more than adequate for the existing openSUSE installations, which as you can see, are using a mere fraction of that amount of space. I expect 16.1 to differ little.

For those custom installing, the space required for / should be more accommodating.

As workaround, I was able to start over, first adding a 15G ext4 /dev/sda11 target using my normal toolset for the installation, then starting Agama anew. The result: dismal, subject for another report, or support forum discussion.

[ancorgs]

only to find it wouldn't let me choose my intended (pre-formatted) partition target:

What do you mean it doesn't let you choose the partition?

I do not think Agama impose any limit in the partitions that can be reused for "/".

[mrmazda]

Its proposal required ~12.6G or ~12.8 G, while my prepared target was only 12G, so it refused to let me select it for /.

[ancorgs]

I tried to reproduce this using Agama web UI. I could not.

My steps

1. I go to "Storage" and select a very small pre-existing partition to be used for "/" (2 GiB).
2. I go to "Software" and add both KDE and Gnome to the default selection. The total estimated size becomes ~8GiB

I still do not see Agama refusing to do anything, even if the selected partition is not big enough.

Can you describe your whole process and exactly at which point Agama refuses to continue?

I'm curious to know where that ~12.6GiB comes from

[mrmazda]

I tried again but reported primarily in #3180 instead of here, as it seems I managed to avoid reproducing as summarized. Apparently this must be a matter of doing things in a certain sequence, and finding everything from which is required to do something not already done. Those plasma/breeze-style, minimalist, barely visible, non-boxed, select list "buttons" are horrid things to deal with.