From owner-freebsd-ports-bugs@FreeBSD.ORG Wed Apr 3 19:20:02 2013 Return-Path: Delivered-To: freebsd-ports-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4220292C for ; Wed, 3 Apr 2013 19:20:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 34379962 for ; Wed, 3 Apr 2013 19:20:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r33JK1Bt040299 for ; Wed, 3 Apr 2013 19:20:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r33JK10A040298; Wed, 3 Apr 2013 19:20:01 GMT (envelope-from gnats) Date: Wed, 3 Apr 2013 19:20:01 GMT Message-Id: <201304031920.r33JK10A040298@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org Cc: From: Darren Pilgrim Subject: Re: ports/177416: mail/postgrey has surfaced a bug in perl's taint checking X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Darren Pilgrim List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Apr 2013 19:20:02 -0000 The following reply was made to PR ports/177416; it has been noted by GNATS. From: Darren Pilgrim To: Paul Beard Cc: "bug-followup@FreeBSD.org" Subject: Re: ports/177416: mail/postgrey has surfaced a bug in perl's taint checking Date: Wed, 03 Apr 2013 12:14:29 -0700 On 2013-04-03 09:05, Paul Beard wrote: > So this is resolved, as best I can tell with no inbound smtp to check > it with. I never determined what port was the issue. I agree it seems like the issue is solved and we can close this PR. > Are there any existing scripts or tools that review installed ports, > other than libchk and pkg_check? portugprade comes with some extra tools. I just use portmaster and the basic pkg tools. > What I take away from this is that I > should be prepared to rip out every perl module and then reinstall > all the leaf ports, just to make sure there are no collisions. So in > the event perl5.16 becomes the default, I may do that. I don't think that's necessary. A lot of what you just did was cleaning out stale ports and (hopefully) correcting any package database corruption. I'd do the normal perl5.n -> perl5.(n+2) upgrade process first and see if it works.