** Changed in: edk2 (Debian)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569602
Title:
[FFE] DFSG-free FAT driver
To manage notifications about this
This bug was fixed in the package edk2 - 0~20160408.ffea0a2c-2
---
edk2 (0~20160408.ffea0a2c-2) unstable; urgency=medium
* Provide split AAVMF_{CODE,VARS}.fd for arm64 in the qemu-efi package,
for VM-friendly nvram persistence in the same style as Fedora et al.
and by
** Changed in: edk2 (Debian)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569602
Title:
[FFE] DFSG-free FAT driver
To manage notifications about this
SECURE_BOOT_ENABLE flag seems ok -- if that's not our standard mode (I
doubt it is), it doesn't break images and at worst we can deliver fixes
in SRUs. So please go ahead.
** Changed in: edk2 (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member
Correct - it is to package a new upstream release with a changed license
and moving the package to universe.
I've prep'd some packaging, which Steve is currently reviewing - the
complete changelog at the moment is:
edk2 (0~20160408.ffea0a2c-1) UNRELEASED; urgency=medium
* New upstream
What is the particular FF request here? If this means packaging a new
upstream release with a changed license and moving the package to
universe, that sounds fine as long as there are no other changes.
If you are going to upload other changes, please list them. That said,
edk2 is a leaf package
** Changed in: edk2 (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569602
Title:
[FFE] DFSG-free FAT driver
To manage notifications about this bug go
