Verified all the linux-meta headers changes in precise: linux-ac100_3.0.27.1.2_armel.deb: Depends: linux-image-ac100 (= 3.0.27.1.2), linux-headers-ac100 (= 3.0.27.1.2) linux-ac100_3.0.27.1.2_armhf.deb: Depends: linux-image-ac100 (= 3.0.27.1.2), linux-headers-ac100 (= 3.0.27.1.2) linux-armadaxp_3.2.0.1613.19_armhf.deb: Depends: linux-image-armadaxp (= 3.2.0.1613.19), linux-headers-armadaxp (= 3.2.0.1613.19) linux-generic_3.2.0.36.43_amd64.deb: Depends: linux-image-generic (= 3.2.0.36.43), linux-headers-generic (= 3.2.0.36.43) linux-generic_3.2.0.36.43_i386.deb: Depends: linux-image-generic (= 3.2.0.36.43), linux-headers-generic (= 3.2.0.36.43) linux-generic-pae_3.2.0.36.43_i386.deb: Depends: linux-image-generic-pae (= 3.2.0.36.43), linux-headers-generic-pae (= 3.2.0.36.43) linux-highbank_3.2.0.36.43_armhf.deb: Depends: linux-image-highbank (= 3.2.0.36.43), linux-headers-highbank (= 3.2.0.36.43) linux-hwe-generic_3.2.0.36.43_amd64.deb: Depends: linux-image-hwe-generic, linux-headers-generic linux-hwe-generic_3.2.0.36.43_i386.deb: Depends: linux-image-hwe-generic, linux-headers-generic-pae linux-lowlatency_3.2.0.36.25_amd64.deb: Depends: linux-image-lowlatency (= 3.2.0.36.25), linux-headers-lowlatency (= 3.2.0.36.25) linux-lowlatency_3.2.0.36.25_i386.deb: Depends: linux-image-lowlatency (= 3.2.0.36.25), linux-headers-lowlatency (= 3.2.0.36.25) linux-lowlatency-pae_3.2.0.36.25_i386.deb: Depends: linux-image-lowlatency-pae (= 3.2.0.36.25), linux-headers-lowlatency-pae (= 3.2.0.36.25) linux-omap_3.2.0.36.43_armel.deb: Depends: linux-image-omap (= 3.2.0.36.43), linux-headers-omap (= 3.2.0.36.43) linux-omap_3.2.0.36.43_armhf.deb: Depends: linux-image-omap (= 3.2.0.36.43), linux-headers-omap (= 3.2.0.36.43) linux-omap4_3.2.0.1424.25_armel.deb: Depends: linux-image-omap4 (= 3.2.0.1424.25), linux-headers-omap4 (= 3.2.0.1424.25) linux-omap4_3.2.0.1424.25_armhf.deb: Depends: linux-image-omap4 (= 3.2.0.1424.25), linux-headers-omap4 (= 3.2.0.1424.25) linux-powerpc_3.2.0.36.43_powerpc.deb: Depends: linux-powerpc-smp (= 3.2.0.36.43) linux-powerpc64-smp_3.2.0.36.43_powerpc.deb: Depends: linux-image-powerpc64-smp (= 3.2.0.36.43), linux-headers-powerpc64-smp (= 3.2.0.36.43) linux-powerpc-smp_3.2.0.36.43_powerpc.deb: Depends: linux-image-powerpc-smp (= 3.2.0.36.43), linux-headers-powerpc-smp (= 3.2.0.36.43) linux-server_3.2.0.36.43_amd64.deb: Depends: linux-image-server (= 3.2.0.36.43), linux-headers-server (= 3.2.0.36.43) linux-server_3.2.0.36.43_i386.deb: Depends: linux-generic-pae linux-virtual_3.2.0.36.43_amd64.deb: Depends: linux-image-virtual (= 3.2.0.36.43), linux-headers-virtual (= 3.2.0.36.43) linux-virtual_3.2.0.36.43_i386.deb: Depends: linux-image-virtual (= 3.2.0.36.43), linux-headers-virtual (= 3.2.0.36.43)
-- You received this bug notification because you are a member of TI OMAP Developers, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/960770 Title: Packages requiring dkms at Pandaboard (omap 4) will also pull linux- headers-generic because current dkms dependencies Status in “dkms” package in Ubuntu: Fix Released Status in “linux-meta” package in Ubuntu: Fix Released Status in “linux-meta-ac100” package in Ubuntu: In Progress Status in “linux-meta-armadaxp” package in Ubuntu: Fix Committed Status in “linux-meta-lowlatency” package in Ubuntu: Fix Committed Status in “linux-meta-nexus7” package in Ubuntu: Fix Released Status in “linux-meta-ti-omap4” package in Ubuntu: Fix Released Status in “dkms” source package in Precise: Fix Committed Status in “linux-meta” source package in Precise: Fix Committed Status in “linux-meta-ti-omap4” source package in Precise: Fix Committed Status in “dkms” source package in Quantal: New Status in “linux-meta” source package in Quantal: New Status in “linux-meta-ac100” source package in Quantal: Fix Committed Status in “linux-meta-armadaxp” source package in Quantal: Fix Released Status in “linux-meta-lowlatency” source package in Quantal: New Status in “linux-meta-nexus7” source package in Quantal: Invalid Status in “linux-meta-ti-omap4” source package in Quantal: New Bug description: [SRU Justification] DKMS is pulling in incorrect headers on some images/installs, plus this fix backports the removal of the 'linux-image' dep that was pulling in linux-image on various media, despite precise.2 wanting linux-image-lts-quantal. This should be fixed by dropping the dkms dependency on headers, and making linux-flavour depend on the correct headers, as it does in Q and R. [Test Case for DKMS] Testcase is twofold: 1) verify that the binary packages no longer have deps on any linux-headers or linux-image packages. 2) verify that the latest precise daily builds no longer incorrectly carry 3.2.0 kernels on x86 [Test case for linux-meta-*] Make sure linux-$(flavour) now depends on linux-image-flavour *and* linux-headers-flavour, rather than just linux-image. [Regression potential] Low, this dependency was pretty much always broken, and it was merely a fluke that it was handled correctly elsewhere and mostly a non-issue on x86 installs. [Original Report] The PowerVR SGX kernel module package for Pandaboard depends on linux-headers-omap4 (headers package for the Omap 4 based kernel) and DKMS, but when installing the package DKMS will also pull linux-headers-generic, forcing the module build to happen with both kernel headers package, besides wasting quite a few extra megabytes. PPA with the current PVR SGX driver: https://launchpad.net/~rsalveti/+archive/pvr-sgx/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/960770/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~tiomap-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~tiomap-dev More help : https://help.launchpad.net/ListHelp
