[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64
This bug was fixed in the package flash-kernel - 3.0~rc.4ubuntu49.5 --- flash-kernel (3.0~rc.4ubuntu49.5) trusty; urgency=medium * Allow us to find DTBs in both the old flat layout and the new vendor subdirectory layout, so we keep backward compatibility (LP: #1408004) -- Adam Conrad adcon...@ubuntu.com Tue, 02 Jun 2015 14:57:54 -0600 ** Changed in: flash-kernel (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 Committed 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
[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64
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
[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64
Verified for both flash-kernel and debian-installer. ** Tags removed: verification-needed ** Tags added: verification-done -- 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 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
[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64
** Branch linked: lp:~ubuntu-core-dev/debian-installer/trusty-proposed -- 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: 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
[Kernel-packages] [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 -- 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
[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64
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
[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64
Hello Andy, or anyone else affected, Accepted flash-kernel into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/flash- kernel/3.0~rc.4ubuntu49.5 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: flash-kernel (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- 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: 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
[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64
This bug was fixed in the package linux - 3.19.0-7.7 --- linux (3.19.0-7.7) vivid; urgency=low [ Andy Whitcroft ] * Release Tracking Bug - LP: #1426013 [ Upstream Kernel Changes ] * x86/irq: Fix regression caused by commit b568b8601f05 * cxl: Fix leaking interrupts if attach process fails - LP: #1415102 * cxl: Early return from cxl_handle_fault for a shut down context - LP: #1415102 * cxl: Disable AFU debug flag - LP: #1415102 * cxl: Disable SPAP register when freeing SPA - LP: #1415102 * cxl: remove redundant increment of hwirq - LP: #1415102 * cxl: Add tracepoints - LP: #1415102 * cxl: Update CXL ABI documentation - LP: #1415102 * cxl: Use image state defaults for reloading FPGA - LP: #1415102 * cxl: Add image control to sysfs - LP: #1415102 * cxl: Enable CAPP recovery - LP: #1415102 * cxl: Add ability to reset the card - LP: #1415102 * cxl: Fix device_node reference counting - LP: #1415102 * cxl: Export optional AFU configuration record in sysfs - LP: #1415102 * cxl: Fail AFU initialisation if an invalid configuration record is found - LP: #1415102 * cxl: Add missing return statement after handling AFU errror - LP: #1415102 * powerpc/eeh: Introduce flag EEH_PE_REMOVED - LP: #1415102 * powerpc/eeh: Allow to set maximal frozen times - LP: #1415102 * HID: i2c-hid: Limit reads to wMaxInputLength bytes for input events -- Andy Whitcroft a...@canonical.com Thu, 26 Feb 2015 16:00:18 + -- 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: 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
[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64
This bug was fixed in the package debian-installer - 20101020ubuntu366 --- debian-installer (20101020ubuntu366) vivid; urgency=medium * Copy apm-mustang.dtb from its new location (LP: #1408004) -- Adam Conrad adcon...@ubuntu.com Fri, 27 Feb 2015 03:57:40 -0700 ** Changed in: debian-installer (Ubuntu) Status: Confirmed = Fix Released ** Changed in: linux (Ubuntu) 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: In Progress Status in flash-kernel source package in Trusty: In Progress Status in linux source package in Trusty: Invalid Bug description: 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
[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64
** Branch linked: lp:~ubuntu-core-dev/debian-installer/ubuntu -- 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: Confirmed Status in flash-kernel package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Committed 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: 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
[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64
** Changed in: flash-kernel (Ubuntu) Importance: Undecided = Medium -- 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: Confirmed Status in flash-kernel package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Committed 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: 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
[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64
This will need fixing in trusty's flash-kernel and trusty's lts-v (and beyond) d-i builds as well. ** Also affects: debian-installer (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: flash-kernel (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: debian-installer (Ubuntu Trusty) Assignee: (unassigned) = Adam Conrad (adconrad) ** Changed in: debian-installer (Ubuntu Trusty) Status: New = In Progress ** Changed in: flash-kernel (Ubuntu Trusty) Assignee: (unassigned) = Adam Conrad (adconrad) ** Changed in: flash-kernel (Ubuntu Trusty) Status: New = In Progress ** Changed in: linux (Ubuntu Trusty) Status: New = Invalid -- 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: Confirmed Status in flash-kernel package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Committed 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: 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
[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64
** Branch linked: lp:ubuntu/vivid-proposed/flash-kernel -- 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: Confirmed Status in flash-kernel package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Committed 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: 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
[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64
** Also affects: flash-kernel (Ubuntu) Importance: Undecided Status: New ** Changed in: flash-kernel (Ubuntu) Status: New = Confirmed ** Changed in: flash-kernel (Ubuntu) Assignee: (unassigned) = Adam Conrad (adconrad) -- 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: Confirmed Status in flash-kernel package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Committed Bug description: 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
[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64
** Changed in: debian-installer (Ubuntu) Status: Invalid = Confirmed ** Changed in: debian-installer (Ubuntu) Assignee: (unassigned) = Adam Conrad (adconrad) -- 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: Confirmed Status in flash-kernel package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Committed Bug description: 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
[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64
This bug was fixed in the package flash-kernel - 3.0~rc.4ubuntu54 --- flash-kernel (3.0~rc.4ubuntu54) vivid; urgency=medium * Allow us to find DTBs in both the old flat layout and the new vendor subdirectory layout, so we keep backward compatibility (LP: #1408004) -- Adam Conrad adcon...@ubuntu.com Fri, 27 Feb 2015 03:46:28 -0700 ** Changed in: flash-kernel (Ubuntu) Status: Confirmed = 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: Confirmed Status in flash-kernel package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed 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: 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
[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64
** Changed in: linux (Ubuntu) Milestone: ubuntu-15.01 = ubuntu-15.02 ** Changed in: debian-installer (Ubuntu) Milestone: ubuntu-15.01 = None -- 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: Invalid Status in linux package in Ubuntu: Fix Committed Bug description: 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
[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64
** Summary changed: - devel: DTBs have moved into vendor specific directories + 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. + + 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: New Status in linux package in Ubuntu: In Progress Bug description: 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
[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64
As this only affects arm64, and we do not yet currently use any dtbs in the installer on that arch, we are safe to ignore this. ** Changed in: debian-installer (Ubuntu) Status: New = Invalid ** Changed in: linux (Ubuntu) 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: Invalid Status in linux package in Ubuntu: Fix Committed Bug description: 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
