Date: Fri, 5 May 2017 18:18:53 +0200 From: Jos Chrispijn <bsdports@cloudzeeland.nl> To: mokhi <mokhi64@gmail.com> Cc: freebsd-ports@freebsd.org Subject: Re: ICU Portupdate faulty Message-ID: <805526d8-0fb0-3038-58b1-d398369b0734@cloudzeeland.nl> In-Reply-To: <CAByVWPUeeCDcNo8d8OW3EJo2S5VzENukkvAYrYzObjnix6vggA@mail.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 :-]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?805526d8-0fb0-3038-58b1-d398369b0734>