kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #121749
[Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64
** Description changed:
- 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.
+ [ 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.
--
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:
In Progress
Status in flash-kernel source package in Trusty:
In Progress
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
References