This bug was fixed in the package debian-installer -
20101020ubuntu318.18
---------------
debian-installer (20101020ubuntu318.18) trusty; urgency=medium
* Switch to '---' as option separator for all kernels (LP: #1427252)
* Add lts-vivid variants for all targets except for e500, for which
support was dropped in the utopic/lts-utopic kernel (LP: #1459779)
* Conditionally use apm-mustang.dtb from new location (LP: #1408004)
-- Adam Conrad <adcon...@ubuntu.com> Tue, 02 Jun 2015 11:07:49 -0600
** Changed in: debian-installer (Ubuntu Trusty)
Status: Fix Committed => Fix Released
--
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/1408004
Title:
devel: DTBs have moved into vendor specific directories on arm64
Status in debian-installer package in Ubuntu:
Fix Released
Status in flash-kernel package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in debian-installer source package in Trusty:
Fix Released
Status in flash-kernel source package in Trusty:
Fix Released
Status in linux source package in Trusty:
Invalid
Bug description:
[ SRU Justification ]
For trusty, the lts-vivid debian-installer builds install the lts-vivid
kernel, which has the DTBs in the new location. As such, both d-i and f-k need
fixing to look for the correct locations.
[ Test Case ]
For d-i, the test case is to build d-i and ensure it's picking up the right
DTBs for both old and new location builds.
For f-k, the test case is to do an installation of both lts-utopic and
lts-vivid on arm64 and ensure that flash-kernel is operating on the
DTBs without error in both cases.
[ Regression Potential ]
The d-i change has already been tested in a PPA and is known-good, while the
f-k change is a straight cherry-pick from vivid, where it was known to work, so
both should be minimally scary.
[ Original Report ]
The installed DTBs have moved into vendor specific directories. We need to
1) make sure we are hoovering them up right, and 2) that the consumers thereof
(d-i etc) are consuming them in the new locations.
NOTE: this actually is only _installed_ into those new directories on
arm64.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1408004/+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
