From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [SECURITY] libidn - locale specific error in test suite
Date: Fri, 24 Mar 2017 19:00:00 -0000 [thread overview]
Message-ID: <837b8e00-57ec-a670-0cec-c0f06c77b3d2@cygwin.com> (raw)
In-Reply-To: <4fab8a5b-f385-251d-57b6-baba5a01d8f4@cygwin.com>
On 2017-03-10 16:01, Yaakov Selkowitz wrote:
> On 2017-02-22 12:58, Yaakov Selkowitz wrote:
>> On 2017-01-19 14:42, Yaakov Selkowitz wrote:
>>> On 2017-01-03 04:53, Dr. Volker Zell wrote:
>>>> Just tried packaging libidn-1.33 and found a locale specific error in
>>>> the test suite (Which was working fine with my latest build). When
>>>> running under strace I get:
>>>
>>> Dr. Volker,
>>>
>>> Since the bug discovered by this test is unrelated to libidn itself,
>>> there should be no need to hold back the libidn release therefor.
>>
>> Ping?
>
> Ping 2?
Ping 3?
--
Yaakov
next prev parent reply other threads:[~2017-03-24 19:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 15:18 [SECURITY] libidn Yaakov Selkowitz
2016-09-30 6:44 ` Dr. Volker Zell
2016-12-29 20:49 ` Yaakov Selkowitz
2017-01-03 10:54 ` [SECURITY] libidn - locale specific error in test suite Dr. Volker Zell
2017-01-09 14:26 ` Corinna Vinschen
2017-01-18 12:13 ` Dr. Volker Zell
2017-01-18 15:24 ` Eric Blake
2017-01-19 10:39 ` Corinna Vinschen
2017-01-19 17:40 ` Eric Blake
2017-01-19 18:19 ` Corinna Vinschen
2017-01-19 20:17 ` Eric Blake
2017-01-19 21:02 ` Corinna Vinschen
2017-01-19 21:17 ` Eric Blake
2017-01-20 8:36 ` Corinna Vinschen
2017-01-19 20:34 ` Eric Blake
2017-01-19 20:43 ` Yaakov Selkowitz
2017-02-22 18:58 ` Yaakov Selkowitz
2017-03-10 22:01 ` Yaakov Selkowitz
2017-03-24 19:00 ` Yaakov Selkowitz [this message]
2017-05-03 21:38 ` Yaakov Selkowitz
2017-03-10 22:02 ` Yaakov Selkowitz
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=837b8e00-57ec-a670-0cec-c0f06c77b3d2@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin-apps@cygwin.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).