Your message dated Sun, 15 Dec 2013 12:41:30 +0000
with message-id <[email protected]>
and subject line Bug#671342: Removed package(s) from unstable
has caused the Debian Bug report #309326,
regarding console-tools: CapsLock doesn't work properly for extended kmap
keycode definitions
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
309326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=309326
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: console-tools
Version: 1:0.2.3dbs-56
Severity: normal
The proper behavior of CapsLock is to shift small letters to caps and -
when combined with Shift - to shift caps to small letters. According to
documentation, this behavior is enabled when a key is defined in one of
the following two ways in the "kmap" file: having just one plain ASCII
letter or by adding the "+" sign before the symbol. Example:
keycode 24 = o
keycode 24 = +o +O
However, the second form does not work, it still generates small "o"
when CapsLock is enabled.
This bug makes it imposible to properly define any keymap with
diacritical (non-ASCII) characters. For instance, to define "รณ", the
following keycode definitions are needed:
keycode 24 = +o +O +oacute +Oacute
...or...
keycode 24 = o
altgr keycode 24 = +oacute
shift altgr keycode 24 = +Oacute
In both cases, the CapsLock doesn't work correctly; it seems that the
"+" sign is ignored. From the two last examples, the former is even
worse since it makes the behavior of plain "o" incorrect.
The problem affects many of the console-data kmap definitions, which use
the first or the second form frequently.
All my consoles are in the unicode mode, non-framebuffer.
The keymaps used to work in the past (maybe the problem is kernel
related).
-- System Information:
Debian Release: 3.1
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.8-11-amd64-k8
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages console-tools depends on:
ii console-common 0.7.51 Basic infrastructure for text cons
ii debconf 1.4.48 Debian configuration management sy
ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an
ii libconsole 1:0.2.3dbs-56 Shared libraries for Linux console
ii sysvinit 2.86.ds1-1 System-V like init
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2:0.2.3-73+rm
Dear submitter,
as the package console-tools has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see http://bugs.debian.org/671342
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)
--- End Message ---
