Date: Wed, 3 Apr 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: <201304031920.r33JK10A040298@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: 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201304031920.r33JK10A040298>