Date: Fri, 29 Mar 2013 19:20:01 GMT From: Darren Pilgrim <ports.maintainer@evilphi.com> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/177416: mail/postgrey has surfaced a bug in perl's taint checking Message-ID: <201303291920.r2TJK1pL020782@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/177416; it has been noted by GNATS. From: Darren Pilgrim <ports.maintainer@evilphi.com> To: Paul Beard <paulbeard@gmail.com> Cc: "bug-followup@FreeBSD.org" <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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201303291920.r2TJK1pL020782>