From owner-freebsd-ports@FreeBSD.ORG Thu Dec 1 22:46:21 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C29B106566B; Thu, 1 Dec 2011 22:46:21 +0000 (UTC) (envelope-from trs@bestpractical.com) Received: from hipster.bestpractical.com (hipster.bestpractical.com [136.248.126.165]) by mx1.freebsd.org (Postfix) with ESMTP id 66E018FC14; Thu, 1 Dec 2011 22:46:21 +0000 (UTC) Received: from [10.1.10.22] (75-147-59-54-NewEngland.hfc.comcastbusiness.net [75.147.59.54]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hipster.bestpractical.com (Postfix) with ESMTPS id A665B240FC4; Thu, 1 Dec 2011 17:26:25 -0500 (EST) Message-ID: <4ED7FF11.3000606@bestpractical.com> Date: Thu, 01 Dec 2011 17:26:25 -0500 From: Thomas Sibley User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: flo@FreeBSD.org X-Enigmail-Version: 1.3.3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org, bps-engineers@bestpractical.com Subject: FreeBSD Port: rt-3.8.11 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Dec 2011 22:46:21 -0000 Hello, Thanks for packaging RT! It appears that Makefile.cpan hasn't been updated from 3.8.8's dependencies to 3.8.11's. Consequently, RT will be broken after moving from 3.8.8 to a newer version. This was discovered while troubleshooting an RT upgrade for a customer whose system didn't have p5-Digest-SHA installed. Running `git log -p rt-3.8.8..rt-3.8.11 sbin/rt-test-dependencies.in` from RT's repo will show you the handful of changes, including a new dep and version bumps. Normally RT's Makefile target testdeps would catch incorrect module versions and missing modules before install, but it appears to be disabled by a packaging patch. If there are still reasons for disabling testdeps during install/upgrade, perhaps testdeps can be run as a packaging sanity check? If it exits with an error, a message could be reported to the user letting them know there may be a problem with the package (hopefully prompting them to file a bug report like this one). Cheers, Thomas