Lucid LTS Maverick backport, update to 2.6.35-25.44

Bug #707577 reported by Tim Gardner on 2011-01-25
264
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-lts-backport-maverick (Ubuntu)
Undecided
Unassigned
Lucid
Undecided
Tim Gardner
linux-meta-lts-backport-maverick (Ubuntu)
Undecided
Unassigned
Lucid
Undecided
Tim Gardner

Bug Description

Sync with Maverick 2.6.35-25.44

Tim Gardner (timg-tpi) on 2011-01-25
Changed in linux-lts-backport-maverick (Ubuntu):
assignee: nobody → Tim Gardner (timg-tpi)
status: New → Fix Committed
Changed in linux-lts-backport-maverick (Ubuntu Lucid):
assignee: nobody → Tim Gardner (timg-tpi)
status: New → Fix Committed
Changed in linux-lts-backport-maverick (Ubuntu):
assignee: Tim Gardner (timg-tpi) → nobody
status: Fix Committed → Incomplete
status: Incomplete → Invalid
Martin Pitt (pitti) wrote :

As we are currently in the 10.04.2 preparation SRU freeze, this would need to wait until after 10.04.2. If it's urgent, can we please check with certification/QA that this can be tested within one week? We are already behind in moving the lucid CDs to build from -updates only.

Tim Gardner (timg-tpi) wrote :

Martin - Postponing this is OK with me. The current version in -updates is good enough for the DVD point release.

Accepted linux-lts-backport-maverick into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Tim Gardner (timg-tpi) wrote :

This kernel is in use on tangerine.buildd.

Tim Gardner (timg-tpi) on 2011-02-09
tags: added: verification-done-lucid
Tim Gardner (timg-tpi) on 2011-02-10
Changed in linux-meta-lts-backport-maverick (Ubuntu):
status: New → Invalid
Changed in linux-meta-lts-backport-maverick (Ubuntu Lucid):
assignee: nobody → Tim Gardner (timg-tpi)
status: New → Fix Committed
Tim Gardner (timg-tpi) on 2011-02-10
security vulnerability: no → yes
Martin Pitt (pitti) wrote :

There is no corresponding linux-meta-lts-backport-maverick for this ABI version in lucid-proposed, and neither is one in the kernel PPA.

Also, how is that v-done already? I don't see any feedback from QA or certification?

Changed in linux-meta-lts-backport-maverick (Ubuntu Lucid):
status: Fix Committed → In Progress
Kees Cook (kees) on 2011-03-02
tags: added: kernel-tracking-bug
Tim Gardner (timg-tpi) on 2011-03-02
Changed in linux-meta-lts-backport-maverick (Ubuntu Lucid):
status: In Progress → Fix Committed
Tim Gardner (timg-tpi) wrote :

Martin - I uploaded linux-meta-lts-backport-maverick_2.6.35.25.36 to the kernel PPA.

As for the v-done tag, neither QA or Cert are testing these backported kernels. I've been making the assumption that since the only change between the released kernel and the backported kernel is just the toolchain, then its probably OK if it boots and the released version has passed QA and cert. The backported kernels are in use on several of the kernel build machines and have had no issues. That is why I felt I could set this to v-done.

Martin Pitt (pitti) wrote :

Thanks, copied to -proposed now.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-meta-lts-backport-maverick - 2.6.35.25.36

---------------
linux-meta-lts-backport-maverick (2.6.35.25.36) lucid; urgency=low

  * linux-lts-backport-maverick 2.6.35-25.44
    - LP: #707577
 -- Tim Gardner <email address hidden> Thu, 10 Feb 2011 13:49:54 -0700

Changed in linux-meta-lts-backport-maverick (Ubuntu Lucid):
status: Fix Committed → Fix Released
Martin Pitt (pitti) wrote :

Copied to -updates and -security. Closing manually due to typo in the changelog.

Changed in linux-lts-backport-maverick (Ubuntu Lucid):
status: Fix Committed → Fix Released
Jamie Strandboge (jdstrand) wrote :

IMHO these need to have more QA than boot testing since they are considered officially supported. For example, while the security team publishes identical source versions for Mozilla updates, they are tested the same on all releases. While I understand that it shouldn't make a difference, our team has seen instances where different toolchains can make a big difference.

To post a comment you must log in.
This report contains Public Security information  Edit
Everyone can see this security related information.

Other bug subscribers