linux-lts-trusty: 3.13.0-52.86~precise1 -proposed tracker

Bug #1451421 reported by Brad Figg
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kernel SRU Workflow
Fix Released
Medium
Unassigned
Automated-testing
Fix Released
Medium
Canonical Kernel Team
Certification-testing
Invalid
Medium
Canonical Hardware Certification
Prepare-package
Fix Released
Medium
Brad Figg
Prepare-package-meta
Invalid
Medium
Canonical Kernel Team
Prepare-package-signed
Fix Released
Medium
Brad Figg
Promote-to-proposed
Fix Released
Medium
Adam Conrad
Promote-to-security
Fix Released
Medium
Adam Conrad
Promote-to-updates
Fix Released
Medium
Adam Conrad
Regression-testing
Invalid
Medium
Canonical Platform QA Team
Security-signoff
Fix Released
Medium
Adam Conrad
Verification-testing
Fix Released
Medium
Canonical Kernel Team
linux-lts-trusty (Ubuntu)
Invalid
Medium
Unassigned
Precise
Fix Released
Medium
Unassigned

Bug Description

This bug is for tracking the 3.13.0-52.86~precise1 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, 04. May 2015 12:02 UTC
kernel-stable-master-bug:1451288
kernel-stable-Prepare-package-end:Wednesday, 06. May 2015 01:01 UTC
kernel-stable-Promote-to-proposed-start:Wednesday, 06. May 2015 01:01 UTC
kernel-stable-Promote-to-proposed-end:Wednesday, 06. May 2015 17:33 UTC
kernel-stable-Verification-testing-start:Wednesday, 06. May 2015 19:01 UTC
kernel-stable-Certification-testing-start:Wednesday, 06. May 2015 19:01 UTC
kernel-stable-Security-signoff-start:Wednesday, 06. May 2015 19:01 UTC
proposed-announcement-sent:True
kernel-stable-Regression-testing-start:Wednesday, 06. May 2015 19:01 UTC
kernel-stable-Certification-testing-end:Wednesday, 06. May 2015 21:00 UTC
kernel-stable-Verification-testing-end:Wednesday, 06. May 2015 21:00 UTC
kernel-stable-Promote-to-updates-start:Wednesday, 06. May 2015 22:00 UTC
kernel-stable-Security-signoff-end:Wednesday, 06. May 2015 22:00 UTC
kernel-stable-Promote-to-updates-end:Thursday, 07. May 2015 02:00 UTC
kernel-stable-phase:Released
kernel-stable-phase-changed:Thursday, 07. May 2015 03:02 UTC

Brad Figg (brad-figg)
tags: added: kernel-release-tracking-bug
tags: added: block-proposed-precise
tags: added: precise
Changed in kernel-sru-workflow:
status: New → In Progress
importance: Undecided → Medium
Changed in linux-lts-trusty (Ubuntu):
importance: Undecided → Medium
Changed in linux-lts-trusty (Ubuntu Precise):
importance: Undecided → Medium
Revision history for this message
Brad Figg (brad-figg) wrote : Packages available

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

description: updated
Brad Figg (brad-figg)
description: updated
Adam Conrad (adconrad)
Changed in linux-lts-trusty (Ubuntu):
status: New → Invalid
Brad Figg (brad-figg)
description: updated
Brad Figg (brad-figg)
description: updated
Revision history for this message
Adam Conrad (adconrad) wrote :

Will be releasing this kernel to -security, as it addresses regressions in a security update.

Brad Figg (brad-figg)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-lts-trusty - 3.13.0-52.86~precise1

---------------
linux-lts-trusty (3.13.0-52.86~precise1) precise; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
    - LP: #1451421

  [ Upstream Kernel Changes ]

  * audit: create private file name copies when auditing inodes
    - LP: #1450442

 -- Brad Figg <email address hidden> Sun, 03 May 2015 18:36:19 -0700

Changed in linux-lts-trusty (Ubuntu Precise):
status: New → Fix Released
status: New → Fix Released
Brad Figg (brad-figg)
description: updated
Revision history for this message
Brad Figg (brad-figg) wrote : Package Released!

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

Changed in kernel-sru-workflow:
status: In Progress → Fix Released
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.