From owner-freebsd-ports@FreeBSD.ORG  Tue Dec 15 18:59:44 2009
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E57DF1065694
	for <freebsd-ports@freebsd.org>; Tue, 15 Dec 2009 18:59:44 +0000 (UTC)
	(envelope-from spambox@haruhiism.net)
Received: from mail.haruhiism.net (mail.fujibayashi.jp
	[IPv6:2001:470:9954:ffff::2])
	by mx1.freebsd.org (Postfix) with ESMTP id A4EEB8FC12
	for <freebsd-ports@freebsd.org>; Tue, 15 Dec 2009 18:59:44 +0000 (UTC)
Received: from [192.168.0.146] (corp.infobox.ru [77.221.128.82])
	(using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.haruhiism.net (Postfix) with ESMTPSA id 037B610FFB0
	for <freebsd-ports@freebsd.org>; Wed, 16 Dec 2009 03:59:43 +0900 (JST)
Message-ID: <4B27DCA4.1090308@haruhiism.net>
Date: Tue, 15 Dec 2009 21:59:48 +0300
From: Kamigishi Rei <spambox@haruhiism.net>
Organization: WIDE
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
	rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0
MIME-Version: 1.0
To: freebsd-ports@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: net-im/ejabberd 2.0.5 to 2.1.0
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Dec 2009 18:59:45 -0000

Hello,

I have a question about ejabberd port; the question is related to the 
patch that comes with revision 2.0.5_1, patch-919-fileioserver. I'd like 
to know if the crash mentioned in the commit message is repeatable, and 
what should I do to reproduce it.
I have updated the port's Makefile, plist and other patches (not 
including the aforementioned one) to use 2.1.0, and it 
builds/installs/deinstalls/runs without problems on my system 
(8.0-STABLE, amd64, Erlang R13B03).
The question is, whether the patch is still required for 2.1.0, and if 
so, I'll try to adapt it (as it does not apply cleanly now).

-- 
Kamigishi Rei
KREI-RIPE
http://fujibayashi.jp