Your message dated Wed, 21 Jan 2026 00:26:08 +0000
with message-id <[email protected]>
and subject line Bug#1125739: fixed in fwupd-efi 1:1.8-4
has caused the Debian Bug report #1125739,
regarding fwupd-efi will FTBFS when gnu-efi gets multiarched
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 [email protected]
immediately.)
--
1125739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1125739
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: fwupd-efi
Version: 1:1.8-3
Tags: ftbfs patch upstream
User: [email protected]
Usertags: ftcbfs
fwupd-efi fails to cross build from source, because it fails locating
gnu-efi using pkg-config. gnu-efi still installs to /usr/lib and that's
not a location pkg-config searches during cross compilation. The
solution here is to move its files to multiarch. Once doing that,
fwupd-efi fails to build from source natively, because it hard codes the
assumption that gnu-efi is installed to /usr/lib and some other
non-multiarch paths. I'm attaching a patch that makes it detect
gnu-efi's location from pkg-config. Doing so works both before and after
the move. Please consider applying it and forwarding it upstream.
Helmut
--- fwupd-efi-1.8.orig/efi/meson.build
+++ fwupd-efi-1.8/efi/meson.build
@@ -37,6 +37,9 @@
efi_libdir = get_option('efi-libdir')
if efi_libdir == ''
+ efi_libdir = gnuefi.get_pkgconfig_variable('libdir')
+endif
+if efi_libdir == ''
fs = import('fs')
multi = run_command(cc.cmd_array(), '-print-multi-os-directory', check: true).stdout().strip()
efi_libdir = join_paths('/usr/lib/', multi)
--- End Message ---
--- Begin Message ---
Source: fwupd-efi
Source-Version: 1:1.8-4
Done: Bastian Germann <[email protected]>
We believe that the bug you reported is fixed in the latest version of
fwupd-efi, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bastian Germann <[email protected]> (supplier of updated fwupd-efi package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 21 Jan 2026 00:27:12 +0100
Source: fwupd-efi
Architecture: source
Version: 1:1.8-4
Distribution: unstable
Urgency: medium
Maintainer: Debian EFI <[email protected]>
Changed-By: Bastian Germann <[email protected]>
Closes: 1125739
Changes:
fwupd-efi (1:1.8-4) unstable; urgency=medium
.
* Team upload
* Prepare cross-compilation (Closes: #1125739)
Checksums-Sha1:
07a46bec1618ec85309ac3dfaaf24369adfabde5 2683 fwupd-efi_1.8-4.dsc
a5be420638977f285e35cf75b69ab87e1a662298 9680 fwupd-efi_1.8-4.debian.tar.xz
dafe62a96d5f3204a152b5dc9cc57a3bf75ddca1 6298 fwupd-efi_1.8-4_source.buildinfo
Checksums-Sha256:
61e8cf8df32fca213aafb8f970255f388866f7e120aa33ce6f02c51e883be3ee 2683
fwupd-efi_1.8-4.dsc
830eea35c2c568b4062231243ee6f603d0deb3122afb4ce3cbda6cadc19b49b3 9680
fwupd-efi_1.8-4.debian.tar.xz
6600cd5773312736bc420850990d0aecc30f520a27815637126e705f2aa6b5b0 6298
fwupd-efi_1.8-4_source.buildinfo
Files:
72dfd8f5b93937c44684772c3b4f19f4 2683 admin optional fwupd-efi_1.8-4.dsc
047e4261fbb5ec19c433a84032b75417 9680 admin optional
fwupd-efi_1.8-4.debian.tar.xz
7c51c8cebe62f9dcf21b8eb5802ece86 6298 admin optional
fwupd-efi_1.8-4_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmlwD6cQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFDOjDADhWMShMYl5SeeDH9Z2XjPyZzA9zFfszJBh
FRNi5XsOlDdYtnoRWeJGe6sxkvGoUNQsKBgShmPTH0FZ12CCc4vHSGykXX5qcEo9
nRYixOp6TBK/KksR2uw9BuAsA56lBVVBgSImrh9Lp44siDeMyf2Kp1w/prJvu0pB
uuHVfIMwbJgmJXlYyI9U8/GOprxUMqSDlAit5Hy6WupHQ3f23YPJR4Qx1YLKWxm5
Ny58CoIvhVtCATQu8yMak9UGW/LBMFtWUvC7A1CztK2vDOU1UxZpMDpDzpRLoSA9
z4YLUH0RcfOjz7spT2f+k7oh814lVgHA2aqsw3VSTgWtkLsF6GPPRrNMB2GmOgbc
X6CSI+IeOjyGhJrtVq6EtpcLNpxSpk+uvq4NdzUns6vnC/QRfeDqUcajti35rrpZ
7b2aZx2WS8vGAldXFzYUujCSjjGe+UyjXNzhn6LRlTDzC8y2Xoavm2Yy9f0mNSsx
9MoHIsVjRMRDjdbgdNL0fq6ss/SXgk0=
=w72Y
-----END PGP SIGNATURE-----
pgp4Aoib8WNyk.pgp
Description: PGP signature
--- End Message ---
