From owner-freebsd-ports-bugs@FreeBSD.ORG Fri Mar 29 06: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 ABA40C81 for ; Fri, 29 Mar 2013 06: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 9CFC1DCC for ; Fri, 29 Mar 2013 06: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 r2T6A1XB070255 for ; Fri, 29 Mar 2013 06: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 r2T6A1f7070254; Fri, 29 Mar 2013 06:10:01 GMT (envelope-from gnats) Date: Fri, 29 Mar 2013 06:10:01 GMT Message-Id: <201303290610.r2T6A1f7070254@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: Fri, 29 Mar 2013 06: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: Thu, 28 Mar 2013 23:08:22 -0700 --Apple-Mail-BBBDAB24-12EB-4514-B60A-24C860CE312D Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable On Mar 28, 2013, at 10:20 PM, Darren Pilgrim w= rote: > There are steps between what's been done so far and a brand new system. A= complete refetch and reinstall of everything perl is one such step. >=20 Done. Still seeing it.=20 >=20 > That's more or less my point, yes. You have about 5 times as many p5 port= s as I've ever seen on one system. >=20 Hey, I don't ask for them, they're mostly dependencies called by other ports= . I could try removing them all and just installing postgrey and it's depend= encies but that never came up before now.=20 >=20 > The thing is I can't reproduce this behaviour. I even ran it on a RELENG_= 6 system and it worked fine there. And it worked fine here until, suspiciously, I lost port 25 service. Coincid= ence, I'm sure, but that's when I noticed it.=20 >=20 > But it's a PR for the mail/postgrey port. It sounds like it's reasonable t= o close this PR. I have no idea what piece of code is balking, I just know what provokes it. H= ence the wording: "mail/postgrey has surfaced a bug in perl's taint checking= ."=20 So close it. I was optimistic that filing a PR might get more than one pair o= f eyes looking at it, especially as the error wasn't in the port with which t= hey were associated.=20= --Apple-Mail-BBBDAB24-12EB-4514-B60A-24C860CE312D Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

On Mar 28, 2013, at= 10:20 PM, Darren Pilgrim <ports.maintainer@evilphi.com> wrote:

There are steps between what's been done so far and a brand new= system. A complete refetch and reinstall of everything perl is one su= ch step.

Done. S= till seeing it.

That's more or less my point, yes. You have about 5 times as many p= 5 ports as I've ever seen on one system.

Hey, I don't ask for them, they're mostly dependencies called by other p= orts. I could try removing them all and just installing postgrey and it's de= pendencies but that never came up before now.

=

The thing is I can't reproduce thi= s behaviour. I even ran it on a RELENG_6 system and it worked fine the= re.

And it worked fine here until, sus= piciously, I lost port 25 service. Coincidence, I'm sure, but that's when I n= oticed it.

But it's a PR for the mail/postgrey port. It sounds like it's r= easonable to close this PR.

I have no i= dea what piece of code is balking, I just know what provokes it. Hence the w= ording: "mail/postgrey has surfaced a bug in perl's taint c= hecking."

So close it. I was optimistic that f= iling a PR might get more than one pair of eyes looking at it, especially as= the error wasn't in the port with which they were associated.

= --Apple-Mail-BBBDAB24-12EB-4514-B60A-24C860CE312D--