Hello Andy, or anyone else affected, Accepted debian-installer into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debian- installer/20101020ubuntu318.18 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: debian-installer (Ubuntu Trusty) Status: In Progress => Fix Committed -- 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 Committed Status in flash-kernel source package in Trusty: Fix Committed 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
