From owner-freebsd-ports-bugs@FreeBSD.ORG Fri Mar 29 19:20: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 AB2CC136 for ; Fri, 29 Mar 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 9CD8373F for ; Fri, 29 Mar 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 r2TJK1w0020783 for ; Fri, 29 Mar 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 r2TJK1pL020782; Fri, 29 Mar 2013 19:20:01 GMT (envelope-from gnats) Date: Fri, 29 Mar 2013 19:20:01 GMT Message-Id: <201303291920.r2TJK1pL020782@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: Fri, 29 Mar 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: Fri, 29 Mar 2013 12:11:45 -0700 On 2013-03-29 11:02, Paul Beard wrote: > I really can't get my mind around how this happens: how can I remove > the file by deinstalling, verify that it's gone, reinstall from a > cleaned port directory, and end up with a file with an almost 4 year > old timestamp? I'm not sure about the timestamp, but the path to the older Socket.pm doesn't exist on any of my systems. I hate to sound like a broken record, but I really do think you have a broken perl install. Now I think you have a broken perl install that won't be fixed without wiping out your entire perl install (perl, p5 modules, and everything that uses perl), deleting distfiles, deleting work dirs, portsnapping a fresh tree, then reinstalling perl and p5 modules *only* by way of dependencies from other ports.