From owner-freebsd-ports@freebsd.org  Fri May  5 16:18:56 2017
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9EACCD5F673
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Fri,  5 May 2017 16:18:56 +0000 (UTC)
 (envelope-from bsdports@cloudzeeland.nl)
Received: from ares.cloudzeeland.nl (cloudzeeland.xs4all.nl [83.161.133.58])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "cloudzeeland.nl",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 612691F7
 for <freebsd-ports@freebsd.org>; Fri,  5 May 2017 16:18:55 +0000 (UTC)
 (envelope-from bsdports@cloudzeeland.nl)
Received: from ares.cloudzeeland.nl (unknown [10.10.10.32])
 by ares.cloudzeeland.nl (Postfix) with ESMTP id 76AD14FE7E05;
 Fri,  5 May 2017 18:18:52 +0200 (CEST)
Received: from [10.10.10.40] (styx.zeeland24.nl [82.176.127.71])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client did not present a certificate)
 by ares.cloudzeeland.nl (Postfix) with ESMTPSA id 1B7514FE7E04;
 Fri,  5 May 2017 18:18:52 +0200 (CEST)
Subject: Re: ICU Portupdate faulty
To: mokhi <mokhi64@gmail.com>
References: <1c87d7b6-54f7-77f0-7476-338bd24aee54@cloudzeeland.nl>
 <CAByVWPVRp4PnW0Fm26aL_TW4R9BUtOQvn9XEEaQtJFqHMz3xaA@mail.gmail.com>
 <8d3c7d80-d51e-3743-eb41-d6633c498153@cloudzeeland.nl>
 <CAByVWPUeeCDcNo8d8OW3EJo2S5VzENukkvAYrYzObjnix6vggA@mail.gmail.com>
Cc: freebsd-ports@freebsd.org
From: Jos Chrispijn <bsdports@cloudzeeland.nl>
Message-ID: <805526d8-0fb0-3038-58b1-d398369b0734@cloudzeeland.nl>
Date: Fri, 5 May 2017 18:18:53 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAByVWPUeeCDcNo8d8OW3EJo2S5VzENukkvAYrYzObjnix6vggA@mail.gmail.com>
X-Virus-Scanned: ClamAV using ClamSMTP on ares.cloudzeeland.nl
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.23
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 05 May 2017 16:18:56 -0000

Yes I noticed as well.
Point is that after updating my tree, the issue still exists allthough I 
have th correct portupdate in my ports.

Let me check what is going wrong here.

Thanks,
Jos

Op 5-5-2017 om 17:48 schreef mokhi:
> Well, as I can see here < http://www.freshports.org/devel/icu/ > an
> older version of this port is vulnerable not current version.
> Maybe by updating your tree your problem will be solved :-]