Werner Llácer

> There's one minor issue with this change. I'll come back and see what it can be, but these behave differently: > > ``` > $ sudo python examples/guided.py` >...

Before you start complaining `perform_installation` could also be written as ```python def perform_installation(mountpoint,mode='full'): """ This is the main installation routine Performs the installation steps on a block device. Only requirement...

This is happening to me too on a loop device. Seems that it is looking for a partuuid which does not exist ¿? @svartkanin I will check #1333 and report...

@svartkanin PR #1333 breaks even earlier, if a partition *already* exists on the disk, but performs if the target disk has no partitions (but retains the gpt label) Master fails...

If you are using the master branch (or similar) this is the same error as in issue #1343 . It is solved via PR #1355, which is in the integration...

@rado84-github it seems you didn't selected/defined any target mountpoint to install into. The installation scripts mounts all the targets under the `/mnt/archinstall` but only creates it if there is something...

We have been working in the definition of space of the partitions. This is how it looks now   Note the different percentages. It's intentional

Help needed ! I need a list of all possible restrictions you can think about partition management (size constrains for GPT/MBR disks, constrains due to UEFI/BIOS, what can and can...

I've added the possibility of generating disk_layout files -before i had planned- Was needed in order to check compatibility. It is generated at the usual directory with the name `layout_diskmanager.json`....

I've integrated `only_hd` into `diskmanager`, so we can now generate a REAL disk structure directly from this module (i.e we are now in phase IV). Testing was otherwise too tedious,...