From owner-freebsd-ports-bugs@FreeBSD.ORG Wed Apr 3 16:10:01 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 5FD34796 for ; Wed, 3 Apr 2013 16:10:01 +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 521FFD58 for ; Wed, 3 Apr 2013 16:10:01 +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 r33GA1Td005385 for ; Wed, 3 Apr 2013 16:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r33GA1MP005384; Wed, 3 Apr 2013 16:10:01 GMT (envelope-from gnats) Date: Wed, 3 Apr 2013 16:10:01 GMT Message-Id: <201304031610.r33GA1MP005384@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org Cc: From: Paul Beard 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: Paul Beard List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Apr 2013 16:10:01 -0000 The following reply was made to PR ports/177416; it has been noted by GNATS. From: Paul Beard To: Darren Pilgrim Cc: "bug-followup@FreeBSD.org" Subject: Re: ports/177416: mail/postgrey has surfaced a bug in perl's taint checking Date: Wed, 3 Apr 2013 09:05:26 -0700 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.=20 My count of p5 ports is down to 54. Everything seems to work. I did hit = an error on a portmaster run where the port had some traces of CVSup = which got me a string of warning messages. I haven't used CVSup in quite = some time. So there's probably more of that out there waiting to be = tripped over.=20 Are there any existing scripts or tools that review installed ports, = other than libchk and pkg_check? 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.=20 I never did find out why there is a p5-IO port installed alongside the = same named port in the base perl install. That was part of the issue, = that postgrey was using trying to use it based on the name. But I never = worked out uninstalling it and rebuilding perl didn't solve it. Or how = it kept coming back with 4 year old timestamps.=20 -- Paul Beard Are you trying to win an argument or solve a problem?=20