Bug#1060368: partman-auto: add basic support for loongarch64

[zhangdandan]

Source: partman-auto
Version: 163
Severity: wishlist
Tags: patch
User: debian-***@lists.debian.org
Usertags: loong64

Dear maintainers,

Support automatic partition adaptation partman-auto for debian-installer.
Please consider the patch (my local patch) I have attached.
If the content of my local patch does not meet the specifications,
please contact me.
According to the maintainer's suggestions, it may be necessary to
continue updating or modifying this patch.

I integrated partman-auto_163+loong64_loong64.udeb in my local DVD iso.
When installing the system through debian-installer, supports automatic
partitioning function by default.
If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

[Pascal Hambourg]

Hello,

Post by zhangdandan
Support automatic partition adaptation partman-auto for debian-installer.
Please consider the patch (my local patch) I have attached.

I do not know anything about the loongarch64 architecture, but I can't
help having questions about the proposed recipes. Do you have any
pointers about the disk layout expected by this platform ? Or is it
standard UEFI disk layout ?

- loong64 and loong64-efi recipes are identical, so why not use symlinks
like other recipes do instead of duplicating files ?

- Why is a separate /boot partition created only if the partitioning
scheme is GPT ?

- A regular FAT32 filesystem is explicitly mounted on /boot/efi. Is it
intended to be used as an EFI system partition ?

- If yes, why doesn't it use the dedicated "efi" method ?

- Moreover, why does it have "lvmok" (meaning that it can be a LVM
logical volume) ? Platform firmware usually cannot read LVM.

[Debian Bug Tracking System]

Your message dated Fri, 22 Nov 2024 09:28:18 +0800
with message-id <55df2e9e-3d20-335e-3999-***@loongson.cn>
and subject line Bug#1060368: fixed in partman-auto 171
has caused the Debian Bug report #1060368,
regarding partman-auto: add basic support for loongarch64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)