Hi Steve and Cyril, Thanks for the help, using the netinst + configuring a mirror worked.
Best, Alex On Thu, Aug 7, 2025 at 5:30 PM Steve McIntyre <[email protected]> wrote: > > On Thu, Aug 07, 2025 at 04:22:31PM -0400, Alex Forrence wrote: > >Package: installation-reports > >Severity: normal > >X-Debbugs-Cc: [email protected] > > ... > > >I wanted to try out systemd-boot, so went through the text-mode expert > >install. > >Selected defaults for everything up until the bootloader menu entries. > >Skipped grub install and selected the systemd-boot entry. A relevant > >part of the log is below: > > > >sudo cat /var/log/installer/syslog | grep systemd-boot > >Aug 7 18:47:00 anna[2666]: DEBUG: retrieving systemd-boot-installer 0.11 > >Aug 7 18:54:02 main-menu[463]: INFO: Menu item 'systemd-boot-installer' > >selected > >Aug 7 18:54:02 in-target: Package systemd-boot is not available, but is > >referred to by another package. > >Aug 7 18:54:02 in-target: Package 'systemd-boot' has no installation > >candidate > >Aug 7 18:54:02 main-menu[463]: WARNING **: Configuring > >'systemd-boot-installer' failed with error code 100 > >Aug 7 18:54:02 main-menu[463]: WARNING **: Menu item > >'systemd-boot-installer' failed. > > > >Then finished installation with the grub option. > > This is a deliberate choice so far, as discussed with the systemd > maintainer. systemd-boot is not a default option for installation and > so isn't included in all the images by default. If you make sure you > use a network mirror during installation, things should work fine. > > -- > Steve McIntyre, Cambridge, UK. [email protected] > "Because heaters aren't purple!" -- Catherine Pitt >
