[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#607058: keyboard-configuration: [lenny->squeeze] prompt twice during upgrade



tags 607058 +wontfix +sqweeze
thanks

On Tue, Dec 14, 2010 at 01:24:36PM +0100, Luca Capello wrote:
> 
> Upgrading from lenny to squeeze produce the following error (the output
> is in French, but it should be easy to understand what is going on):
> =====
> debian:/home/luca# apt-get dist-upgrade
> [...]
> =====
> 
> Given that I already chose the keyboard at the beginning of the upgrade,
> I do not see why the question is asked again.

>From what I can tell this error (the model question asked twice 
during the upgrade) arises in the following case:

1. console-setup has been installed before the upgrade (the version 
from lenny).

2. For some reason the variable XKBMODEL is initialized as empty 
string in the configuration file.

I was able to reproduce this bad behaviour of the old version of 
console-setup but I haven't tried the find the source of the bug.  
>From what I can tell after dpkg-reconfigure the configuration file is 
always correct so the problem affects only users who have used 
console-setup in lenny with its initial configuration.  The empty 
XKBMODEL didn't cause problems because 1. console-setup was able to 
work correctly with empty value of XKBMODEL and 2. in lenny X didn't 
use the configuration of console-setup.

The recent versions of console-setup try to correct the problem with 
the empty XKBMODEL but they do this is a way that causes the model 
question to be asked twice - during the preconfiguration of the 
package and during the postconfiguration.  I am reluctant to fix this 
because it doesn't seem easy (see #352697).  I am afraid if I try to 
fix the bug I might introduce a worse one (better to ask one 
additional question than to leave a broken configuration file). 
Anyway, it is somehow pointless to fix this in sid and wheezy because 
direct upgrades lenny->wheezy are not supported.

I'd suggest to mark 607060 as not being blocked by this bug.

Anton Zinoviev



Reply to: