update-manager should refuse to update hardy vserver/chroot guests to lucid
Bug #826544 reported by
Rolf Leggewie
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| update-manager (Ubuntu) |
Won't Fix
|
High
|
Unassigned | ||
Bug Description
Please add some code to update-manager in hardy to test whether the OS in running as a vserver guest or inside a chroot. In that case, update-manager should refuse to update the OS to lucid until bug 430224 is properly resolved.
Revision history for this message
| Rolf Leggewie (r0lf) wrote | #1 |
| Changed in update-manager (Ubuntu): | |
| importance: | Undecided → High |
| milestone: | none → hardy-updates |
| Changed in update-manager (Ubuntu): | |
| status: | New → Opinion |
| Changed in update-manager (Ubuntu): | |
| status: | Opinion → New |
Revision history for this message
| Evan Peck (colors) wrote | #2 |
| Changed in update-manager (Ubuntu): | |
| status: | New → Incomplete |
| status: | Incomplete → Confirmed |
Revision history for this message
| Rolf Leggewie (r0lf) wrote | #3 |
| Changed in update-manager (Ubuntu): | |
| milestone: | hardy-updates → none |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
I think this is of critical importance, but setting to High only due to the limited amount of users affected by this. Those that are affected are VERY severely affected, though, up to complete data-loss.