From owner-freebsd-ports-bugs@FreeBSD.ORG Sun Feb 3 13:20:01 2013 Return-Path: Delivered-To: freebsd-ports-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5ED4543E for ; Sun, 3 Feb 2013 13:20:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 5043B799 for ; Sun, 3 Feb 2013 13:20:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r13DK1Co099188 for ; Sun, 3 Feb 2013 13:20:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r13DK1Bj099187; Sun, 3 Feb 2013 13:20:01 GMT (envelope-from gnats) Date: Sun, 3 Feb 2013 13:20:01 GMT Message-Id: <201302031320.r13DK1Bj099187@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org Cc: From: Alex Kozlov Subject: Re: ports/174819: games/exult: Update to 1.4.9 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Alex Kozlov List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2013 13:20:01 -0000 The following reply was made to PR ports/174819; it has been noted by GNATS. From: Alex Kozlov To: green dog Cc: bug-followup@freebsd.org Subject: Re: ports/174819: games/exult: Update to 1.4.9 Date: Sun, 3 Feb 2013 15:17:34 +0200 On Sun, Jan 13, 2013 at 12:24:00PM +0400, green dog wrote: > > I don't think it's a good idea to update port to 1.4.9rc1. It's old > > and has a critical bug 'that causes random objects in the games to > > disappear forever'. > > (see http://exult.sourceforge.net , news entry from 11 February 2011). > reported on the forum like this bug is related to the work of a garbage > collector, and thus depends on the system (for example, I did not find > posts that were able to reproduce it). Perhaps, but exact cause of this bug was not found, it assumed to be fixed in recent (newer than 1.4.9rc1) snapshots. http://exult.sourceforge.net/forum/read.php?f=1&i=358191&t=358191 : "We assume it has been fixed. With the not sure way to trigger it we don't know for sure. We haven't had any negative report though ;)" I propose to wait a little longer before update because (from thread above): "There's still some bugs that we want to fix and recent changes need play tested to make sure that we didn't break anything." -- Alex