| 2008-10-15 17:48:40 |
Ernst Kloppenburg |
description |
this is probably not a bug in debconf, but in the update process in general
I started with
- a current hardy system without any foreign packages
- debconf set to use the frontend "kde"
then I started the upgrade with adept_manager --dist-upgrade
- the first few configuration questions were asked with the kde frontend as expected
- at some point, most likely after some library upgrade, debconf stopped using the kde frontend and proceeded asking it's questions using the readline frontend in the "terminal window" of the upgrade tool (always complaining about a missing libqt-perl first) |
this is probably not a bug in debconf, but in the update process in general
I started with
- a current hardy system without any foreign packages
- debconf set to use the frontend "kde"
then I started the upgrade with adept_manager --dist-upgrade-devel
- the first few configuration questions were asked with the kde frontend as expected
- at some point, most likely after some library upgrade, debconf stopped using the kde frontend and proceeded asking it's questions using the readline frontend in the "terminal window" of the upgrade tool (always complaining about a missing libqt-perl first) |
|
