Not release-critical. It turned out that the exit status was due to
migration-assistant not catching mount errors and me having an LVM PV
lying around on the disk. The way m-a's cleanup and ok_handler work is
still very weird and I think may have some subtle bugs, but it can wait
until after feisty.
** Summary changed:
- migration-assistant cleanup handler recurses into wait and sets wrong
dbfilter.status
+ migration-assistant cleanup handler does very weird stuff involving
recursively calling run_command
** Changed in: ubiquity (Ubuntu)
Importance: High => Medium
Target: ubuntu-7.04 => None
--
migration-assistant cleanup handler does very weird stuff involving recursively
calling run_command
https://bugs.launchpad.net/bugs/105861
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
