Your message dated Tue, 8 May 2018 12:20:47 +0300
with message-id <20180508092047.GA31530@logic>
and subject line Re: Bug#895047: Missing thousands separator symbol in the 
default console font
has caused the Debian Bug report #895047,
regarding Missing thousands separator symbol in the default console font
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 ow...@bugs.debian.org
immediately.)


-- 
895047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: console-setup-linux
Version: 1.182

Hi,

GNU libc commit [1] changed the thousands separator symbol for many locales to 
U+202F NARROW NO-BREAK SPACE. This symbol doesn't seem to exist in the default 
console font, which leads to an unknown symbol in e.g. apt output (see the 
attached screenshot).

 [1] https://sourceware.org/git/?
p=glibc.git;a=commit;h=70a6707fa15e63591d991761be025e26e8d02bb6

--- End Message ---
--- Begin Message ---
Package: console-setup-linux
Version: 1.183


On Fri, Apr 06, 2018 at 06:05:59PM +0300, Алексей Шилин wrote:
> 
> GNU libc commit [1] changed the thousands separator symbol for many 
> locales to U+202F NARROW NO-BREAK SPACE. This symbol doesn't seem to 
> exist in the default console font, which leads to an unknown symbol in 
> e.g. apt output (see the attached screenshot).

I hope I fixed this bug in version 1.183 of the package but then
I forgot to upload it.  Fortunately, version 1.184 is already in the 
archive.

Anton Zinoviev

--- End Message ---

Reply via email to