This bug was fixed in the package linux-signed - 4.4.0-150.176
---------------
linux-signed (4.4.0-150.176) xenial; urgency=medium
* Master version: 4.4.0-150.176
linux-signed (4.4.0-149.175) xenial; urgency=medium
* Master version: 4.4.0-149.175
* Built-Using incorrect (LP: #1824016)
- Rename "VERSION" template string to more precise "UNSIGNED_SRC_VERSION"
- Use the correct source package name in Built-Using field
-- Khalid Elmously <khalid.elmou...@canonical.com> Wed, 29 May 2019
14:30:59 -0400
** Changed in: linux-signed (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1824016
Title:
Built-Using incorrect
Status in linux-signed package in Ubuntu:
Fix Released
Status in linux-signed-hwe package in Ubuntu:
Invalid
Status in linux-signed-hwe-edge package in Ubuntu:
Invalid
Status in linux-signed source package in Xenial:
Fix Released
Status in linux-signed-hwe source package in Xenial:
Fix Committed
Status in linux-signed-hwe-edge source package in Xenial:
Invalid
Status in linux-signed source package in Bionic:
Fix Released
Status in linux-signed-hwe source package in Bionic:
Fix Released
Status in linux-signed-hwe-edge source package in Bionic:
Fix Released
Status in linux-signed source package in Cosmic:
Fix Released
Status in linux-signed-hwe source package in Cosmic:
Invalid
Status in linux-signed-hwe-edge source package in Cosmic:
Invalid
Status in linux-signed source package in Disco:
Fix Released
Status in linux-signed-hwe source package in Disco:
Invalid
Status in linux-signed-hwe-edge source package in Disco:
Invalid
Bug description:
[Impact]
The Build-Using control file field is incorrect for linux-signed-hwe &
linux-signed-hwe-edge. They claim they were built against the "linux" package,
but should be linux-hwe/linux-hwe-edge respectively.
[Test Case]
Look at the Packages file.
[Fix]
Detect and insert the correct package name at build time.
[Regression Risk]
Hm.. maybe if something gets added using the PACKAGE keyword in control.stub
that isn't intended to be replaced gets accidentally replaced, screwing up some
other control field?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1824016/+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
