linux: 2.6.24-31.99 -proposed tracker

[Herton R. Krzesinski]

This bug is for tracking the 2.6.24-31.99 upload package. This bug will contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-stable-Prepare-package-start:Monday, 13. February 2012 19:22 UTC
kernel-stable-Certification-testing-end:Monday, 13. February 2012 19:31 UTC
kernel-stable-Prepare-package-end:Wednesday, 15. February 2012 05:00 UTC
kernel-stable-Promote-to-proposed-start:Wednesday, 15. February 2012 05:00 UTC
kernel-stable-Promote-to-proposed-end:Tuesday, 21. February 2012 11:00 UTC
kernel-stable-Verification-testing-start:Tuesday, 21. February 2012 11:01 UTC
kernel-stable-Security-signoff-start:Tuesday, 21. February 2012 17:00 UTC
kernel-stable-Verification-testing-end:Tuesday, 21. February 2012 17:00 UTC
kernel-stable-Regression-testing-start:Tuesday, 21. February 2012 17:00 UTC
kernel-stable-Regression-testing-end:Friday, 24. February 2012 23:00 UTC
kernel-stable-Promote-to-updates-start:Thursday, 01. March 2012 22:15 UTC
kernel-stable-Security-signoff-end:Thursday, 01. March 2012 22:15 UTC
kernel-stable-phase:Released
kernel-stable-phase-changed:Monday, 05. March 2012 16:30 UTC
kernel-stable-Promote-to-updates-end:Monday, 05. March 2012 16:30 UTC

[Brad Figg (brad-figg)]

All builds are complete, packages in this bug can be copied to -proposed.

[Brad Figg (brad-figg)]

The following packages ended up in the wrong component in the -proposed pocket:

linux-image-2.6.24-31-lpiacompat 2.6.24-31.99 - is in main instead of universe
linux-image-2.6.24-31-openvz 2.6.24-31.99 - is in main instead of universe
linux-image-2.6.24-31-openvz 2.6.24-31.99 - is in main instead of universe
linux-image-2.6.24-31-rt 2.6.24-31.99 - is in main instead of universe
linux-image-2.6.24-31-rt 2.6.24-31.99 - is in main instead of universe
linux-image-2.6.24-31-xen 2.6.24-31.99 - is in main instead of universe
linux-image-2.6.24-31-xen 2.6.24-31.99 - is in main instead of universe
linux-restricted-modules-server 2.6.24.31.33 - is in main instead of restricted
linux-restricted-modules-server 2.6.24.31.33 - is in main instead of restricted
linux-headers-lum-2.6.24-31-lpiacompat 2.6.24-31.51 - is in main instead of universe
linux-headers-lum-2.6.24-31-openvz 2.6.24-31.51 - is in main instead of universe
linux-headers-lum-2.6.24-31-openvz 2.6.24-31.51 - is in main instead of universe
linux-headers-lum-2.6.24-31-rt 2.6.24-31.51 - is in main instead of universe
linux-headers-lum-2.6.24-31-rt 2.6.24-31.51 - is in main instead of universe
linux-headers-lum-2.6.24-31-xen 2.6.24-31.51 - is in main instead of universe
linux-headers-lum-2.6.24-31-xen 2.6.24-31.51 - is in main instead of universe
linux-ubuntu-modules-2.6.24-31-lpiacompat 2.6.24-31.51 - is in main instead of universe
linux-ubuntu-modules-2.6.24-31-openvz 2.6.24-31.51 - is in main instead of universe
linux-ubuntu-modules-2.6.24-31-openvz 2.6.24-31.51 - is in main instead of universe
linux-ubuntu-modules-2.6.24-31-rt 2.6.24-31.51 - is in main instead of universe
linux-ubuntu-modules-2.6.24-31-rt 2.6.24-31.51 - is in main instead of universe
linux-ubuntu-modules-2.6.24-31-xen 2.6.24-31.51 - is in main instead of universe
linux-ubuntu-modules-2.6.24-31-xen 2.6.24-31.51 - is in main instead of universe
fglrx-kernel-source 1:8-3+2.6.24.18-31.12 - is in restricted instead of multiverse
fglrx-kernel-source 1:8-3+2.6.24.18-31.12 - is in restricted instead of multiverse
linux-restricted-modules-2.6.24-31-lpiacompat 2.6.24.18-31.12 - is in restricted instead of multiverse
linux-restricted-modules-2.6.24-31-openvz 2.6.24.18-31.12 - is in restricted instead of multiverse
linux-restricted-modules-2.6.24-31-openvz 2.6.24.18-31.12 - is in restricted instead of multiverse
linux-restricted-modules-2.6.24-31-rt 2.6.24.18-31.12 - is in restricted instead of multiverse
linux-restricted-modules-2.6.24-31-rt 2.6.24.18-31.12 - is in restricted instead of multiverse
linux-restricted-modules-2.6.24-31-xen 2.6.24.18-31.12 - is in restricted instead of multiverse
linux-restricted-modules-2.6.24-31-xen 2.6.24.18-31.12 - is in restricted instead of multiverse
nvidia-glx-legacy 71.86.04+2.6.24.18-31.12 - is in restricted instead of multiverse
nvidia-glx-legacy 71.86.04+2.6.24.18-31.12 - is in restricted instead of multiverse
nvidia-glx-legacy-dev 71.86.04+2.6.24.18-31.12 - is in restricted instead of multiverse
nvidia-glx-legacy-dev 71.86.04+2.6.24.18-31.12 - is in restricted instead of multiverse
nvidia-kernel-source 1:96.43.05+2.6.24.18-31.12 - is in restricted instead of multiverse
nvidia-kernel-source 1:96.4...

[Herton R. Krzesinski (herton)]

Just a note: all the "restricted instead of multiverse" items above may be wrong: the component checker is complaining because originally these packages went to the multiverse component in the release pocket of hardy, and it uses that as a base of information. Please advise if they are correct to be on restricted pocket, in which case I'll add an exception for these in the component checker so it doesn't complain. It would be easier with we had something like a database that had <package name> -> <component> mappings.

The remaining items are correct and should be fixed.

[Martin Pitt (pitti)]

Herton R. Krzesinski [2012-02-17 12:10 -0000]:
> Just a note: all the "restricted instead of multiverse" items above may
> be wrong: the component checker is complaining because originally these
> packages went to the multiverse component in the release pocket of
> hardy, and it uses that as a base of information. Please advise if they
> are correct to be on restricted pocket

They aren't. It's just ridiculously complicated to get the overrides
correct, as the only script that we have requires publication first
and runs very long. So copying kernels to -proposed requires two
separate steps with about an hour in between them.

That's why I'm so insistant on having all kernel binaries of a source
in main (of course that won't help the old releases any more).

So please keep the check, it's very useful and looks correct.

Martin

--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)

[Brad Figg (brad-figg)]

The following packages ended up in the wrong component in the -proposed pocket:

linux-image-2.6.24-31-lpiacompat 2.6.24-31.99 - is in main instead of universe
linux-image-2.6.24-31-openvz 2.6.24-31.99 - is in main instead of universe
linux-image-2.6.24-31-openvz 2.6.24-31.99 - is in main instead of universe
linux-image-2.6.24-31-rt 2.6.24-31.99 - is in main instead of universe
linux-image-2.6.24-31-rt 2.6.24-31.99 - is in main instead of universe
linux-image-2.6.24-31-xen 2.6.24-31.99 - is in main instead of universe
linux-image-2.6.24-31-xen 2.6.24-31.99 - is in main instead of universe
linux-restricted-modules-server 2.6.24.31.33 - is in main instead of restricted
linux-restricted-modules-server 2.6.24.31.33 - is in main instead of restricted
linux-headers-lum-2.6.24-31-lpiacompat 2.6.24-31.51 - is in main instead of universe
linux-headers-lum-2.6.24-31-openvz 2.6.24-31.51 - is in main instead of universe
linux-headers-lum-2.6.24-31-openvz 2.6.24-31.51 - is in main instead of universe
linux-headers-lum-2.6.24-31-rt 2.6.24-31.51 - is in main instead of universe
linux-headers-lum-2.6.24-31-rt 2.6.24-31.51 - is in main instead of universe
linux-headers-lum-2.6.24-31-xen 2.6.24-31.51 - is in main instead of universe
linux-headers-lum-2.6.24-31-xen 2.6.24-31.51 - is in main instead of universe
linux-ubuntu-modules-2.6.24-31-lpiacompat 2.6.24-31.51 - is in main instead of universe
linux-ubuntu-modules-2.6.24-31-openvz 2.6.24-31.51 - is in main instead of universe
linux-ubuntu-modules-2.6.24-31-openvz 2.6.24-31.51 - is in main instead of universe
linux-ubuntu-modules-2.6.24-31-rt 2.6.24-31.51 - is in main instead of universe
linux-ubuntu-modules-2.6.24-31-rt 2.6.24-31.51 - is in main instead of universe
linux-ubuntu-modules-2.6.24-31-xen 2.6.24-31.51 - is in main instead of universe
linux-ubuntu-modules-2.6.24-31-xen 2.6.24-31.51 - is in main instead of universe
fglrx-kernel-source 1:8-3+2.6.24.18-31.12 - is in restricted instead of multiverse
fglrx-kernel-source 1:8-3+2.6.24.18-31.12 - is in restricted instead of multiverse
linux-restricted-modules-2.6.24-31-lpiacompat 2.6.24.18-31.12 - is in restricted instead of multiverse
linux-restricted-modules-2.6.24-31-openvz 2.6.24.18-31.12 - is in restricted instead of multiverse
linux-restricted-modules-2.6.24-31-openvz 2.6.24.18-31.12 - is in restricted instead of multiverse
linux-restricted-modules-2.6.24-31-rt 2.6.24.18-31.12 - is in restricted instead of multiverse
linux-restricted-modules-2.6.24-31-rt 2.6.24.18-31.12 - is in restricted instead of multiverse
linux-restricted-modules-2.6.24-31-xen 2.6.24.18-31.12 - is in restricted instead of multiverse
linux-restricted-modules-2.6.24-31-xen 2.6.24.18-31.12 - is in restricted instead of multiverse
nvidia-glx-legacy 71.86.04+2.6.24.18-31.12 - is in restricted instead of multiverse
nvidia-glx-legacy 71.86.04+2.6.24.18-31.12 - is in restricted instead of multiverse
nvidia-glx-legacy-dev 71.86.04+2.6.24.18-31.12 - is in restricted instead of multiverse
nvidia-glx-legacy-dev 71.86.04+2.6.24.18-31.12 - is in restricted instead of multiverse
nvidia-kernel-source 1:96.43.05+2.6.24.18-31.12 - is in restricted instead of multiverse
nvidia-kernel-source 1:96.4...

[Martin Pitt (pitti)]

The overrides are correct now:

linux-restricted-modules-2.6.24-31-rt | 2.6.24.18-31.12 | hardy-proposed/multiverse | amd64, i386
linux-headers-lum-2.6.24-31-openvz | 2.6.24-31.51 | hardy-proposed/universe | amd64, i386

I suppose the bot ran right after I set to "fix released", but after setting the overrides it needs a publisher run to make the changes visible to archive.u.c.

[Brad Figg (brad-figg)]

Only CVEs which do not require verification.

[C de-Avillez (hggdh2)]

no regressions observed

[John Johansen (jjohansen)]

looks good

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 2.6.24-31.99

---------------
linux (2.6.24-31.99) hardy-proposed; urgency=low

  [Herton R. Krzesinski]

  * Release Tracking Bug
    - LP: #931627

  [Andy Whitcroft]

  * debian -- validate patches are applied to openvz etc

  [Stefan Bader]

  * SAUCE: Return deny all as default in encode_share_access
    - LP: #917829
    - CVE-2011-4324

  [Tim Gardner]

  * [Config] Generate patch set from flattened sources
  * [Config] Added apply-patch-to-binary-custom
  * [Config] Flattened openvz
  * [Config] Flattened xen

  [Upstream Kernel Changes]

  * sound/oss: remove offset from load_patch callbacks
    - LP: #925337
    - CVE-2011-1476
  * sound/oss/opl3: validate voice and channel indexes
    - LP: #925335
    - CVE-2011-1477
  * Fix for buffer overflow in ldm_frag_add not sufficient
    - LP: #922371
    - CVE-2011-2182
  * Move "exit_robust_list" into mm_release()
    - LP: #927889
    - CVE-2012-0028
  * futex: Nullify robust lists after cleanup
    - LP: #927889
    - CVE-2012-0028
 -- Herton Ronaldo Krzesinski <email address hidden> Mon, 13 Feb 2012 17:25:53 -0200

[Brad Figg (brad-figg)]

The package has been published and the bug is being set to Fix Released