From owner-freebsd-ports-bugs@FreeBSD.ORG Wed Aug 14 17:30:04 2013 Return-Path: Delivered-To: freebsd-ports-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 558B4F89 for ; Wed, 14 Aug 2013 17:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 426F1294B for ; Wed, 14 Aug 2013 17:30:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r7EHU3hU055184 for ; Wed, 14 Aug 2013 17:30:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r7EHU3UF055183; Wed, 14 Aug 2013 17:30:03 GMT (envelope-from gnats) Date: Wed, 14 Aug 2013 17:30:03 GMT Message-Id: <201308141730.r7EHU3UF055183@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org Cc: From: Darren Pilgrim Subject: Re: ports/181291: [PATCH] mail/postgrey: make postgrey work with perl 5.18 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: Wed, 14 Aug 2013 17:30:04 -0000 The following reply was made to PR ports/181291; it has been noted by GNATS. From: Darren Pilgrim To: Yasuhiro KIMURA Cc: bug-followup@FreeBSD.org Subject: Re: ports/181291: [PATCH] mail/postgrey: make postgrey work with perl 5.18 Date: Wed, 14 Aug 2013 13:27:24 -0400 Yahuhiro, Thank you for the patch. This should be fixed upstream; but I'm not opposed to a temporary local patch. I am out of town the rest of August. I will spin up a remote VM and test out the patch later this week. In the meantime, would you submit this to David's github as a follow-up to the open issue? Regards, Darren Pilgrim