From owner-freebsd-gnome@FreeBSD.ORG Sun Jan 6 16:15:56 2008 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB57A16A419 for ; Sun, 6 Jan 2008 16:15:56 +0000 (UTC) (envelope-from reichcc@comcast.net) Received: from QMTA05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by mx1.freebsd.org (Postfix) with ESMTP id 80A2613C447 for ; Sun, 6 Jan 2008 16:15:56 +0000 (UTC) (envelope-from reichcc@comcast.net) Received: from OMTA02.westchester.pa.mail.comcast.net ([76.96.62.19]) by QMTA05.westchester.pa.mail.comcast.net with comcast id ZrxP1Y00A0QuhwU0500Z00; Sun, 06 Jan 2008 16:04:56 +0000 Received: from [IPv6:::ffff:192.168.5.236] ([98.197.59.235]) by OMTA02.westchester.pa.mail.comcast.net with comcast id Zs4h1Y00754X7Ua3N00000; Sun, 06 Jan 2008 16:04:44 +0000 X-Authority-Analysis: v=1.0 c=1 a=aiIX5UjjAAAA:8 a=eg-rh4C4Jq0S9TzvjPsA:9 a=hPFbg9xHTafAV4IUmO8A:7 a=3-9B69mO5ZDjJfhCg-hKZEPsEeUA:4 a=3SmO1NJXDBsA:10 From: Patrick Reich To: freebsd-gnome@freebsd.org Content-Type: text/plain Date: Sun, 06 Jan 2008 10:05:05 -0600 Message-Id: <1199635505.7420.10.camel@descartes.bluewinds.org> Mime-Version: 1.0 X-Mailer: Evolution 2.12.2 Content-Transfer-Encoding: 7bit Subject: Evolution and the timezone patch X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jan 2008 16:15:56 -0000 Hi everyone, I checked the archives and found something about a patch for Evolution not starting up the first time due to an off by one error when looking up timezones. Robert Noland posted a patch here http://bugzilla.gnome.org/show_bug.cgi?id=492426 As of a portsnap pull yesterday and a build from scratch of gnome2, I encountered the same behavior. Has this patch been applied to the ports tree or is there a commit delay until after the upcoming releases? If it has been applied, is there a workaround? Note that I am not with this machine at present and probably will not be again until the middle of the week. Thank you all, Patrick