AAVMF firmware volume (de)serialization broken
Bug #2051348 reported by
Mate Kukri
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-uefivars (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
python-uefivars has some bugs and broken assumptions that make it incompatible with AAVMF (ARM64 edk2 firmware) variable volumes.
This bug has an attached debdiff that cherry-picks some patches from my upstream branch that solve the issue:
- "edk2.py: Use length from firmware volume header (Fixes #9) #10": Merged into upstream main
- "edk2.py: Improve firmware volume (de)serialization #11": Open pull request
Please see upstream bug report and pull requests for more details:
- https:/
- https:/
- https:/
Changed in python-uefivars (Ubuntu): | |
status: | New → Fix Committed |
To post a comment you must log in.
Hi Mate,
Thanks for the debdiff. There are still a few things that can be improved before uploading, though:
* Please add a bug reference in your d/changelog entry /dep-team. pages.debian. net/deps/ dep3/
* We're sorely lacking context to understand what this is about, could you add some more in the bug title and description?
* Please add DEP-2 headers to your patches to make ongoing maintenance easier: https:/
Notably the headers regarding upstream status are IMHO particularly useful: Forwarded, Applied-Upstream.
Unsubscribing ubuntu-sponsors, please re-subscribe once you think my concerns have been addressed.
Cheers,
Simon