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

Go for it. Please share a branch with the backport back to salsa.

Go for it. Please share a branch with the backport back to salsa.

Hi Mario,
Thanks! I have prepared the backport and will upload to backports-new shortly.
I get an error pushing my branch to
https://salsa.debian.org/efi-team/efivar ; I have requested access to
efi-team on salsa but maybe those permissions are too strong?


Cheers!

Chris

Hi Mario,
Thanks! I have prepared the backport and will upload to backports-new shortly.
I get an error pushing my branch to
https://salsa.debian.org/efi-team/efivar ; I have requested access to
efi-team on salsa but maybe those permissions are too strong?


Cheers!

Chris

I've invited you as a developer to efivar, hopefully you can access it now.

I've invited you as a developer to efivar, hopefully you can access it now.

Hi Mario,

Thanks, I managed to push the branch trixie-backports to efivar now :-).


Cheers!

Chris

* Christopher Obbard <obbardc@debian.org> [260722 06:13]:

This sounds like something that we (as a distro) might want fixed in
trixie, not just trixie-backports. Would it be worthwhile suggesting
this as an update for the next trixie point release?

Best,
Chris

Christopher: would you be happy with that?

Hi,

Hmm, I wouldn't be opposed to this; but in my opinion it doesn't fix a
bug per-se and instead introduces new features so isn't suitable for a
stable point release ?

I think having it in trixie-backports in the short term would be
better, but I am happy to propose the fix for a trixie point release
as well.

Non-voting; just my 2c :-)

Chris

once a new upstream release is eventually cut; so I think we leave
this initial backport in place. Any queries let me know.

Chris

Just FYI, I managed to make some time to prepare a backport for trixie && submitted a trixie-pu bug describing the reasoning: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1143444

Please reply to the bug if I missed anything or there's anything you'd like to clarify.


Cheers!

Christopher Obbard

That looks great, thanks!

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!