From owner-freebsd-ports-bugs@FreeBSD.ORG Sat Mar 30 02:30:02 2013 Return-Path: Delivered-To: freebsd-ports-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F3FAA851 for ; Sat, 30 Mar 2013 02:30: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 E76EC917 for ; Sat, 30 Mar 2013 02:30: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 r2U2U1Jd011751 for ; Sat, 30 Mar 2013 02:30:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r2U2U1GU011744; Sat, 30 Mar 2013 02:30:01 GMT (envelope-from gnats) Date: Sat, 30 Mar 2013 02:30:01 GMT Message-Id: <201303300230.r2U2U1GU011744@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: Sat, 30 Mar 2013 02:30:02 -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: Fri, 29 Mar 2013 19:25:10 -0700 On Mar 29, 2013, at 7:01 PM, Darren Pilgrim = wrote: > Yes, that would be the only way to know for sure which module is the = culprit. It's time-intensive, but it would be worth it to hunt down the = stale perl module. You could install them in dependency groups. At = least that way you can pare it down to a handful for which you must test = one by one, instead of all 600. I have no idea where to start with that. Is there a way to query for = what port requires a module? I keep searching but it seems like = everything is geared to find what ports you need to install rather than = what ports rely on X. The smarter option would have been to check dates = in /var/db/pkg and see what was updated when this started. But it looks = like every perl module was touched on March 22, with just a few on March = 23 =97 the ones that postgrey depends on. p5-IO was installed updated on = the 22nd. I would like to know what ports depend on that.=20 -- Paul Beard Are you trying to win an argument or solve a problem?=20