On Wed, 12 Mar 2025 22:34:01 +0100 Gianfranco Costamagna <locutusofb...@debian.org> wrote: > On Tue, 25 Feb 2025 11:27:36 +0100 Yves-Alexis Perez <cor...@debian.org> wrote: > > On Tue, Feb 25, 2025 at 11:26:58AM +0100, Yves-Alexis Perez wrote: > > > On Tue, Feb 25, 2025 at 11:13:40AM +0100, Yves-Alexis Perez wrote: > > > > On Tue, Feb 25, 2025 at 10:03:37AM +0000, Luca Boccassi wrote: > > > > > On Tue, 25 Feb 2025 at 09:57, Yves-Alexis Perez <cor...@debian.org> wrote: > > > > > Would you be able to provide a patch that fixes them? > > > > > > > > Unfortunately no, but I only discovered the bug today while trying to > > > > use KeyTool.efi and not finding it. Is upstream aware of the issue? > > > > > > So I did a quick test by reverting the changes to the Makefile disabling > > > the EFI binaries build and it *seems* to actually work just fine, at > > > least here on my box. > > > > > > It's really a smoke test but I'm not sure how well the Ubuntu changes > > > have been checked. It seems to me they did a lot of work to fix the > > > FTBFS but the "stop building EFI binaries" might be unrelated. > > > > Here's the (trivial) patch I used. > > -- > > Yves-Alexis Perez > > Hello, I took your patch to simplify the other one coming from Ubuntu. > I also did some test in ppa, and the reason for the build to fail in Ubuntu > was a missing symbol related to stack guards during build. > I disabled stack-protector and uploaded in sid, now we should have everything back!
Thanks for taking care of that - but unfortunately it looks like the FTFBS on arm64 is back with this upload: https://buildd.debian.org/status/fetch.php?pkg=efitools&arch=arm64&ver=1.9.2-3.3&stamp=1741817188&raw=0
