Your message dated Sat, 15 Aug 2026 12:31:17 +0100
with message-id
<[email protected]>
and subject line Re: Bug#1142580: efivar: intent to maintain a backport of
efivar for trixie-backports
has caused the Debian Bug report #1142580,
regarding efivar: intent to maintain a backport of efivar for trixie-backports
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.)
--
1142580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1142580
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: efivar
Version: 39-2
Severity: wishlist
X-Debbugs-Cc: [email protected], [email protected]
Dear Maintainer,
I would like to upload and maintain a backport of efivar for trixie-backports.
efivar 39-2 contains a patch backported from upstream[0] to enable persistent
EFI variable storage on the ESP. This is needed on platform which lack
dedicated firmware-managed EFI variable storage. See Bug#1102494[1] for
more information. This backport is needed to enable the persistent EFI
variable storage on Qualcomm platforms.
I have built and tested the version currently in testing against trixie. There
are no packaging changes needed.
I am happy to maintain the backport for the lifetime of the trixie-backports
suite and keep it updated as new versions migrate to testing.
Please let me know if the EFI Team would prefer to maintain the backport
itself, or if there are any package-specific concerns I should be aware of.
I will submit the backport changes to the existing Salsa repository.
This work is sponsored by Qualcomm as part of my employment
I work at Qualcomm and part of my job is trying to make Debian better on
Qualcomm hardware. We are currently maintaining downstream image builds
for customised Debian images for Qualcomm hardware[2] where we plan to
reduce the delta against Debian and other upstream projects over the
long term.
Cheers!
Christopher Obbard
Link[0]: https://github.com/rhboot/efivar/pull/267
Link[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102494
Link[2]: https://github.com/qualcomm-linux/qcom-deb-images
-- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 7.1.3+deb14-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Version: 39-2~bpo13+1
Since the efivar backport is now in trixie-backports[0] and we have a separate
bug for the inclusion in the stable point release[1], this bug can be closed
now :-)
[0]: https://packages.debian.org/trixie-backports/efivar
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1143444
Cheers!
--- End Message ---
