Bug#754596: libc6 package upgrade sends ISO-2022 escape sequences to a terminal which doesn't support them (PuTTY in UTF-8 mode)

2014-10-12 Thread Stephen Powell
On Tue, 15 Jul 2014 22:49:18 +0200, Sven Joachim wrote:
 On 2014-07-12 23:30 +0200, Stephen Powell wrote:
 
 The problem occurs when libc6 must be upgraded during apt-get upgrade
 or apt-get dist-upgrade.  I see a screen which looks like this:

 -

 lu Configuring libc6:s390x tk
 x Running services and programs that are using NSS need to be restarted,x
 x otherwise they might not be able to do lookup or authentication any more  x
 x (for services such as ssh, this can affect your ability to login).x
 x Please review the following space-separated list of init.d scripts forx
 x services to be restarted now, and correct it if needed.   x
 x   x
 x Note: restarting sshd/telnetd should not affect any existing  x
 x connections.  x
 x   x
 x Services to restart for GNU libc library upgrade: x
 x   x
 x vsftpd exim4 cron atd x
 x   x
 x  Ok x
 x   x
 mqqqj

 -

 As you can see, PuTTY was sent the traditional ISO-2022 box-drawing escape
 sequences to draw the box, which does not work when PuTTY is operating in
 UTF-8 mode.  These need to be converted into equivalent UTF-8 sequences to
 look right.  I wish to emphasize that libc6 is the *only* package which does
 this.
 
 Seems logical, see below.
 
 If the bug is not in package libc6, then why is libc6 the *only* package
 which doesn't use the proper box-drawing technique?
 
 Because your UTF-8 locale isn't available at the time the above screen
 is shown.  It comes from the libc6 preinst, and libc6 declares a Breaks
 on the old locales package (see #585737 for details).
 

Sorry for the long delay in responding, Sven.  I just now noticed your
update to the bug log.  I get hundreds of e-mails per day.  I must have
accidentally deleted yours before reading it.

I will try running apt-get install locales first from now on, before running
apt-get upgrade or apt-get --purge dist-upgrade, and see if that helps.

-- 
  .''`. Stephen Powellzlinux...@wowway.com
 : :'  :
 `. `'`
   `-


-- 
To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/1963553673.4759314.1413152295292.javamail.zim...@wowway.com



Bug#754596: libc6 package upgrade sends ISO-2022 escape sequences to a terminal which doesn't support them (PuTTY in UTF-8 mode)

2014-07-12 Thread Stephen Powell
.  It's only when
using a terminal which does *not* support ISO-2022 escape sequences in UTF-8
mode that we have a problem.

Personally, I believe that supporting ISO-2022 escape sequences in UTF-8
mode represents a standards violation (see
http://www.cl.cam.ac.uk/~mgk25/unicode.html#term).  But that's beside the
point.  The point is that PuTTY does *not* support ISO-2022 escape sequences
in UTF-8 mode, and due to the terminal type definition of xterm-utf8,
ncurses knows this.  Yet it is being sent untranslated ISO-2022 escape
sequences somehow.  But only when upgrading package libc6.  Not when upgrading
any other package.  Very strange.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-


--
To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/504656925.4452.1405200626016.javamail.r...@md01.wow.synacor.com



Bug#597756: iconv: conversion stopped due to problem in writing the output

2010-09-22 Thread Stephen Powell
Package: eglibc
Version: 2.11.2-5

I'm not sure if this bug is in iconv itself or in another package which
calls iconv, but since I have discovered the problem in at least two
packages (bash and dash) I will report it against iconv and you may
reassign it as you see fit.

When looking at the man page for bash or dash, then quitting immediately
on the first screen by pressing q, I sometimes get the following error message:

iconv: conversion stopped due to problem in writing the output

But I can't seem to reproduce the problem consistently.  Sometimes I
get the error, and sometimes I don't.  I have yet to come up with a
scenario that always causes the failure symptoms.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-



-- 
To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/401068719.195003.1285185716556.javamail.r...@md01.wow.synacor.com