Please update lvm2 in precise from quantal
Bug #1009972 reported by
Dimitri John Ledkov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| lvm2 (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned | ||
| Precise |
Invalid
|
Wishlist
|
Unassigned | ||
Bug Description
potentially up to 2.02.88-2ubuntu2
| Changed in lvm2 (Ubuntu): | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
| tags: | added: 2.02.88-2ubuntu2 |
| tags: |
added: fs.oneplanning removed: 2.02.88-2ubuntu2 |
| Changed in lvm2 (Ubuntu Precise): | |
| milestone: | none → ubuntu-12.04.1 |
| Changed in lvm2 (Ubuntu Precise): | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
| Changed in lvm2 (Ubuntu Quantal): | |
| milestone: | none → quantal-alpha-3 |
| no longer affects: | lvm2 (Ubuntu Quantal) |
| Changed in lvm2 (Ubuntu): | |
| status: | Confirmed → Fix Released |
Revision history for this message
| Steve Langasek (vorlon) wrote | #1 |
| Changed in lvm2 (Ubuntu Precise): | |
| status: | Confirmed → Invalid |
To post a comment you must log in.
This doesn't fit the SRU criteria for an SRU. This either needs to be a backport (to precise-backports) or a more targeted cherry-pick of fixes on top of 2.02.66 that doesn't carry as much risk of regression as pulling in the whole upstream drop does.