From owner-freebsd-ports-bugs@FreeBSD.ORG Mon Jun 6 11:50:12 2011 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5938B106564A for ; Mon, 6 Jun 2011 11:50:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 48D368FC0A for ; Mon, 6 Jun 2011 11:50:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p56BoCjb080747 for ; Mon, 6 Jun 2011 11:50:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p56BoCfe080746; Mon, 6 Jun 2011 11:50:12 GMT (envelope-from gnats) Date: Mon, 6 Jun 2011 11:50:12 GMT Message-Id: <201106061150.p56BoCfe080746@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Gerard Seibert Cc: Subject: Re: ports/157256: perl-5.14.0 breaks mail/p5-Mail-SpamAssassin X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Gerard Seibert List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2011 11:50:12 -0000 The following reply was made to PR ports/157256; it has been noted by GNATS. From: Gerard Seibert To: bug-followup@FreeBSD.org, jpc@porterclark.com Cc: Subject: Re: ports/157256: perl-5.14.0 breaks mail/p5-Mail-SpamAssassin Date: Mon, 6 Jun 2011 07:41:12 -0400 I had a similar problem with two ports. The solution was to get the: Port: p5-IO-Socket-INET6-2.65 updated to: Port: p5-IO-Socket-INET6-2.67 Path: /usr/ports/net/p5-IO-Socket-INET6 Info: Perl module with object interface to AF_INET6 domain sockets That corrected the problem. You might want to verify that any other CPAN modules that your application uses are also fully updated. Some CPAN port maintainers, including me, have become somewhat lax in that department. Contact the port maintainer if you find a newer version. Apparently, the latest version of Perl is somewhat picky about the version of the modules it uses.