Public bug reported:
linux-signed-oem was failing to build because it was trying to look up
the location of the secureboot signed artifacts in the archive based on
the component of the build-dependency (linux-headers-$kver-oem) which
was in universe.
<cjwatson> slangasek: For better or worse, LP currently hardcodes main
for the signing custom upload there, so we shouldn't do ftpmaster
surgery to move the files around.
The kernel packaging should not try to look up the component, but should
always look for this under main/.
This is not a blocker for GA, this was addressed by linux-oem being
promoted to main.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1766916
Title:
secureboot signing code looks for signed artifacts by component,
should always be in main
Status in linux package in Ubuntu:
Incomplete
Bug description:
linux-signed-oem was failing to build because it was trying to look up
the location of the secureboot signed artifacts in the archive based
on the component of the build-dependency (linux-headers-$kver-oem)
which was in universe.
<cjwatson> slangasek: For better or worse, LP currently hardcodes main
for the signing custom upload there, so we shouldn't do ftpmaster
surgery to move the files around.
The kernel packaging should not try to look up the component, but
should always look for this under main/.
This is not a blocker for GA, this was addressed by linux-oem being
promoted to main.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766916/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
