This bug was fixed in the package gnu-efi - 3.0.13+git20210716.269ef9d-1
---
gnu-efi (3.0.13+git20210716.269ef9d-1) experimental; urgency=medium
* New upstream version 3.0.13+git20210716.269ef9d
* Add any-riscv64 to Architecture list (Closes: #988231) (LP: #1938324)
* Add any-ia
Yeah, that's not the right way. Then it would be 3.0.13-0ubuntu1, and
not changed in the upstream version. Which is OK too, but I went ahead
and imported a git-archive export as 3.0.13+git20210716.269ef9d-1 in the
Debian repository and uploaded that to experimental with any-riscv64
(and any-ia64) a
The 3.0.13 release was in March 2021. The RISC-V patches were added
after this.
What I have done in my PPA is using a 3.0.13 tarball and adding the 22
patches written thereafter to debian/patches:
0001-Add-Device-Path-Utilities-Protocol-support.patch
0002-Add-EFI_SHELL_PROTOCOL-definitions.patch
Do we need a snapshot past 3.0.13 for this? I'd prefer to use releases,
to be honest. The upstream versioning for snapshots should really be
something like 3.0.13+git..
Doing this properly in the git repo (https://salsa.debian.org/efi-
team/gnu-efi) would be nice, and then upload to experimental a
** Tags added: fr-1528
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938324
Title:
gnu-efi does not support RISC-V
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+
Cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988231
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938324
Title:
gnu-efi does not support RISC-V
To manage notifications about this bug go t
