From owner-freebsd-ports@FreeBSD.ORG Thu Dec 7 13:20:47 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AD85816A403; Thu, 7 Dec 2006 13:20:47 +0000 (UTC) (envelope-from gamato@users.sf.net) Received: from mail.pipni.cz (mail.pipni.cz [193.86.238.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95B2843CA2; Thu, 7 Dec 2006 13:19:55 +0000 (GMT) (envelope-from gamato@users.sf.net) Received: from mail.pipni.cz ([193.86.238.3]:34713 helo=gamato.org) id 1GsJB4-0002nG-AZ; Thu, 07 Dec 2006 14:20:42 +0100 From: "mato" To: josh.carroll@psualum.com Date: Thu, 7 Dec 2006 14:20:42 +0100 Message-Id: <20061207131208.M28770@users.sf.net> In-Reply-To: <8cb6106e0612061646m1a9b9f94nc33bdb36ad25594d@mail.gmail.com> References: <20061206233232.GA72778@xor.obsecurity.org> <45775FA0.7020206@users.sf.net> <8cb6106e0612061646m1a9b9f94nc33bdb36ad25594d@mail.gmail.com> X-Mailer: Open WebMail 2.51 20050627 X-OriginatingIP: 170.252.96.10 (m@gamato.org) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Cc: freebsd-questions@freebsd.org, freebsd-ports@freebsd.org Subject: Re: portupgrade refusin to upgrade a port .. when it shouldn't imho X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Dec 2006 13:20:47 -0000 On Wed, 6 Dec 2006 16:46:24 -0800, Josh Carroll wrote > > >> ** Port marked as IGNORE: multimedia/win32-codecs: > > >> is forbidden: Remote code execution: > > >> http://vuxml.FreeBSD.org/24f6b1eb-43d5-11db-81e1-000e0c2e438a.html > > >> > > >> Isn't this behaviour flawed ?? Or am I missing something ? > > You need to make config in /usr/ports/multimedia/win32-codecs, and > unselect quicktime. Then the port should install. This is assuming, > of course, that you can live without the QT codec(s). > > Josh OK, I will try it.. Thank you all. But the question remains -- if new port version is not vulnerable why i cannot upgrade to it ?? Cheers, Martin