Comment 3 for bug 2054100

Revision history for this message
Hans Joachim Desserud (hjd) wrote : Re: Can't upgrade keyboard-configuration on Noble

>Yes, I have proposed enabled.

I assume you are aware it's not generally recommended to keep proposed enabled and install all upgrades. Anyways, that means this is the same issue which is keeping xkeyboard-config from migrating to the release repo.

Regarding comma or pipe, I cannot say for certain because I'm not that familiar with this package but it might be on purpose. Some packages do it to lock their dependencies in place. This is especially true if the underlying package do large changes so you cannot be sure if everything still works with newer versions or if you need to know what the changes are to take full advantage of the new things. This means that 2.38.1, 2.38.2 or security fixes will still match and be installable but never versions like 2.39 would be blocked. Maybe all console-setup needs is a manual rebuild to pick up the current version available or it might require further changes to the package to handle the newer changes.

The way forward will probably be a newer version of console-setup which supports the latest version, when that is uploaded to -proposed both packages will work and can be migrated together. In the meantime, xkeyboard-config will be kept in -proposed in order to not make other packages uninstallable.