From owner-freebsd-ports-bugs@FreeBSD.ORG Thu Nov 22 16:36:37 2012 Return-Path: Delivered-To: freebsd-ports-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 89000D0A for ; Thu, 22 Nov 2012 16:36:37 +0000 (UTC) (envelope-from c47g@gmx.at) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by mx1.freebsd.org (Postfix) with SMTP id CB8F88FC12 for ; Thu, 22 Nov 2012 16:36:35 +0000 (UTC) Received: (qmail invoked by alias); 22 Nov 2012 16:36:34 -0000 Received: from cm56-168-232.liwest.at (EHLO bones.gusis.at) [86.56.168.232] by mail.gmx.net (mp072) with SMTP; 22 Nov 2012 17:36:34 +0100 X-Authenticated: #9978462 X-Provags-ID: V01U2FsdGVkX1+rg6ouGSurA8G6wsJmOXMRPmBK0OyNh6YaUYxjKA CmbN3n1Fgb1nSn From: Christian Gusenbauer To: rm@freebsd.org Subject: Re: ports/173561: ports/astrolog crashes on amd64 Date: Thu, 22 Nov 2012 17:38:09 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.1-PRERELEASE; KDE/4.8.4; amd64; ; ) References: <201211211956.qALJu42N032212@freefall.freebsd.org> In-Reply-To: <201211211956.qALJu42N032212@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201211221738.09728.c47g@gmx.at> X-Y-GMX-Trusted: 0 Cc: freebsd-ports-bugs@freebsd.org X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Nov 2012 16:36:37 -0000 On Wednesday 21 November 2012 20:56:04 rm@freebsd.org wrote: > Synopsis: ports/astrolog crashes on amd64 > > State-Changed-From-To: open->feedback > State-Changed-By: rm > State-Changed-When: Wed Nov 21 19:56:04 UTC 2012 > State-Changed-Why: > Christian, thank you for submission. misc/astrolog was fixed another > way. Would you please update your ports tree and confirm that problem is > gone (w/o your patch applied)? Thank you in advance. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=173561 I've just verified that your patch solves the problem, too. Thanks, Christian.