Bug#1092581: systemd-boot fails to install if directories are missing on boot/efi partitions

[Luca Boccassi]

Control: tags -1 -moreinfo
Control: tags -1 unreproducible
Control: close -1

On Thu, 9 Jan 2025 at 12:12, Norbert Lange <nolange79 at gmail.com> wrote:
>
> Am Do., 9. Jan. 2025 um 12:11 Uhr schrieb Luca Boccassi <bluca at debian.org>:
> >
> > Control: tags -1 moreinfo
> >
> > On Thu, 09 Jan 2025 10:51:41 +0100 Norbert Lange <nolange79 at gmail.com>
> > wrote:
> > > Package: systemd-boot
> > > Version: 257.1-7
> > > Severity: important
> > > X-Debbugs-Cc: nolange79 at gmail.com
> > >
> > > Dear Maintainer,
> > >
> > > I am running a fresh installation form the debian testing installer,
> > > while installing systemd-boot I got the following errors:
> > >
> > > Failed to open "/efi/EFI/BOOT/.#BOOTX64.EFIa96c171bbeb42eff" for
> > writing: No such file or directory
> > > Failed to open "/boot/loader/entries.srel" for writing: No such file
> > or directory
> > >
> > > after creating those directories the installation succeeded
> >
> > Where is your ESP mounted from your fstab?
>
> /efi

Note that the default in Debian is /boot/efi

> >
> > Please reproduce manually with debug logs by running
> > 'SYSTEMD_LOG_LEVEL=debug bootctl install --make-machine-id-
> > directory=auto' and attach the output
>
> I CANT produce anymore.
> For some reasons it seems the postinstall script called 'update'
> instead of 'install' the first time?
> here a my logs, installation constantly failed. until i manually
> created the directories.
>
> then i purged the packages, cleaned up remains (machine-id directories).
>
> now there is no problem installing systemd-boot

Ok, I can't reproduce it either, so let's close then. Maybe the ESP
wasn't mounted for some local-system-specific reason the first time.