public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Cc: svnpenn@gmail.com
Subject: Re: [ANNOUNCEMENT] Updated: libreadline7-7.0.1-1, libreadline-devel-7.0.1-1, bash-4.4.5-1
Date: Fri, 13 Jan 2017 14:47:00 -0000	[thread overview]
Message-ID: <e3644c5c-0280-f699-71c8-2c59e3c0534c@redhat.com> (raw)
In-Reply-To: <58785ffd.a5249d0a.66c86.fcde@mx.google.com>


[-- Attachment #1.1: Type: text/plain, Size: 1006 bytes --]

On 01/12/2017 11:05 PM, Steven Penny wrote:
> On Tue, 3 Jan 2017 10:34:01, "Eric Blake (cygwin)" wrote:
>> The releases of readline 7.0.1-1 and bash 4.4.5-1, which have been
>> experimental for a few weeks, have now been promoted to current.
> 
> Note that new version of libreadline7 breaks interactive non ASCII input. Please
> see:
> 
> http://cygwin.com/ml/cygwin/2017-01/msg00066.html
> 
> downgrading to the following versions fixes the problem:
> 
> - libreadline7-6.3.8
> - bash-4.3.48

Is the problem in libreadline7 or in bash? The newer bash requires the
newer readline, but if the problem is in readline proper, then the newer
readline plus the older bash would reproduce it.

I don't think I introduced any accidental downstream regressions, so
this may be a true upstream regression in readline.  But I have not yet
had time to try and reproduce the problem.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2017-01-13 14:47 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-03 16:55 Eric Blake (cygwin)
2017-01-13  5:07 ` Steven Penny
2017-01-13 14:47   ` Eric Blake [this message]
2017-01-14  0:23     ` Steven Penny
2017-01-14 21:48       ` Eric Blake
2017-01-15  0:27         ` Steven Penny
2017-01-15 13:23           ` Vince Rice
2017-01-15 14:11             ` cyg Simple
2017-01-15 14:30               ` Steven Penny
2017-01-16 10:32                 ` Yaakov Selkowitz
2017-01-16 12:40                   ` Steven Penny
2017-01-15 22:33         ` Thomas Wolff
2017-01-16  0:45           ` Steven Penny
2017-01-16  0:54             ` Steven Penny
2017-01-17  2:47         ` Steven Penny
2017-01-17  3:32           ` Steven Penny
2017-01-18  0:36             ` Steven Penny
2017-01-18  2:08               ` Eric Blake
2017-01-18  3:55                 ` Steven Penny
2017-01-18  4:09                   ` Doug Henderson
2017-01-18  5:02                     ` Larry Hall (Cygwin)
2017-01-18  5:45                       ` Steven Penny
2017-01-19  5:23                         ` Steven Penny
2017-01-19 13:23                           ` Eliot Moss
2017-01-19 14:21                             ` Eric Blake
2017-01-19 18:13                               ` Corinna Vinschen
2017-01-19 23:54                                 ` Steven Penny
2017-01-20 13:04                                   ` Corinna Vinschen
2017-01-20 14:51                           ` Eric Blake
2017-01-20 15:00                             ` Eric Blake
2017-01-21  3:57                               ` Steven Penny
2017-01-18  1:46     ` Eric Blake

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e3644c5c-0280-f699-71c8-2c59e3c0534c@redhat.com \
    --to=eblake@redhat.com \
    --cc=cygwin@cygwin.com \
    --cc=svnpenn@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).