> 2025年5月6日 16:33，Martin-Éric Racine <[email protected]> 写道： > > ti 6.5.2025 klo 11.13 Miao Wang ([email protected]) kirjoitti: >> >> On Sat, 26 Apr 2025 10:37:51 +0300 =?utf-8?q?Martin-=C3=89ric_Racine?= >> <[email protected]> wrote: >>> Package: ipxe >>> Version: 1.0.0+git-20190125.36a4c85-5.1 >>> Followup-For: Bug #1102120 >>> X-Debbugs-Cc: [email protected] >>> >>> The problem with spliting the package is that, upon upgrade, ipxe will >>> loose its GRUB menu. This is not a desirable outcome. >>> >>> Please revert this. >>> >>> Thanks. >>> >> >> Hi, >> >> Thanks for letting me know this problem. I understand your concern that >> users installing the ipxe package will notice the grub menu is missing >> after the upgrade. However, to support installing correct ipxe image(s) >> for booting the current machine, as I have mentioned in #1093500, the >> package should be arch-dependent. However, the ipxe package also provides >> images for booting other machines (might be used with other softwares to >> provide pxe booting services), which should be arch-independent. As a >> result, the separation is necessary. > > It is NOT necessary.
I believe it should be necessary. Firstly, if the two packages are merged into one, there will be contradiction on whether the resulting package should be arch-dependent or arch-independent We now provide boot images for i386, amd64, arm64, riscv64, loong64. If the combined ipxe packages is arch-independent, then users will see lots of such images in /boot, most of which are useless due to mismatched architecture. If the combined ipxe packages is arch-dependent, then it is not build-able on riscv64 and loong64, because building images for x86-64 hosts (located in /usr/lib/ipxe/) requires cross compiler targeting x86-64, which is not available on riscv64 and loong64. As a result, it is necessary to split the images for the two needs into two packages to overcome this contradiction. Secondly, images to boot other machines and images and the menu entry to boot the current machine are actually for two different purposes. A user who wants to host a PXE boot server using iPXE boot images is unlikely to also want to boot this sever into iPXE environment. A user who relies on iPXE installed as a boot entry in the locally installed grub for booting is also unlikely to need iPXE images in various formats for various platforms. As a result, splitting the ipxe package is good for reducing unnecessary files installed. > >> To overcome for the possible disruption to the users, I have added a >> NEWS entry to notify the users who want a grub menu to install the split >> ipxe-grub. > > That's not gonna help. People will still lose their GRUB menu entry > upon upgrading. This could break their installation, if they're > expected to boot from PXE by default. The package ipxe after the split now recommends ipxe-grub. So during the upgrade, ipxe-grub will be automatically installed for normal users. If a professional user specifies --no-install-recommends, then it is expected that the NEWS will be carefully read and the need for ipxe-grub will be carefully evaluated. Cheers, Miao Wang
