Activity log for bug #348660
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2009-03-25 20:30:14 | Oliver Grawert | bug | added bug | ||
| 2009-03-26 08:23:21 | Oliver Grawert | ubiquity: importance | Undecided | High | |
| 2009-03-26 08:23:21 | Oliver Grawert | ubiquity: statusexplanation | |||
| 2009-03-26 08:23:21 | Oliver Grawert | ubiquity: milestone | ubuntu-9.04 | ||
| 2009-03-26 08:45:12 | Emmet Hikory | ubiquity: status | New | Confirmed | |
| 2009-03-26 08:45:12 | Emmet Hikory | ubiquity: statusexplanation | I can reproduce the behaviour, but I believe that the code snippet presented is not the issue: that matches the semantics of automatic_mode. Essentially, in automatic_mode, the preseeding can override the interface. When not in automatic_mode, preseeding only sets default values in the interface, and the interface expects those to change. To me, the problem consists of the lack of support for a bootloading in ubiquity. The try clause starting around ubiquity/scripts/install.py:1617 should have appropriate clauses for armel to install (or not) appropriate bootloaders (unless in automatic mode, and preseeded to not do so). | ||
| 2009-03-26 11:37:35 | Emmet Hikory | bug | assigned to flash-kernel (Ubuntu) | ||
| 2009-03-26 12:18:07 | Colin Watson | ubiquity (Ubuntu): status | Confirmed | Fix Committed | |
| 2009-03-26 12:18:07 | Colin Watson | ubiquity (Ubuntu): assignee | cjwatson | ||
| 2009-03-27 14:42:45 | Colin Watson | bug task added | flash-kernel (Ubuntu Jaunty) | ||
| 2009-03-27 14:42:45 | Colin Watson | bug task added | ubiquity (Ubuntu Jaunty) | ||
| 2009-03-30 15:50:07 | Launchpad Janitor | ubiquity: status | Fix Committed | Fix Released | |
| 2009-04-09 14:06:57 | Oliver Grawert | flash-kernel (Ubuntu Jaunty): status | New | Fix Released | |
| 2010-02-22 10:41:25 | Launchpad Janitor | branch linked | lp:ubuntu/ubiquity |
