From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.86.87.8 with SMTP id k8cs65994fgb; Tue, 9 Mar 2010 02:13:47 -0800 (PST) Received: by 10.224.106.84 with SMTP id w20mr466516qao.304.1268129626647; Tue, 09 Mar 2010 02:13:46 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 7si14087401qwb.50.2010.03.09.02.13.46; Tue, 09 Mar 2010 02:13:46 -0800 (PST) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 0B338185830D; Tue, 9 Mar 2010 05:13:45 -0500 (EST) X-Greylist: delayed 352 seconds by postgrey-1.31 at rubyforge.org; Tue, 09 Mar 2010 04:54:02 EST Received: from csgmail.cad-schroer.com (csgmail.cad-schroer.de [194.187.187.195]) by rubyforge.org (Postfix) with ESMTP id C1975158806E for ; Tue, 9 Mar 2010 04:54:02 -0500 (EST) X-MDAV-Processed: csgmail.cad-schroer.com, Tue, 09 Mar 2010 10:48:09 +0100 Received: from [192.168.202.86] ([81.174.231.25]) by cad-schroer.com (csgmail.cad-schroer.com) (Cipher TLSv1:RC4-MD5:128) (MDaemon PRO v10.1.2) with ESMTP id md50002149738.msg for ; Tue, 09 Mar 2010 10:48:08 +0100 X-Spam-Processed: csgmail.cad-schroer.com, Tue, 09 Mar 2010 10:48:08 +0100 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 81.174.231.25 X-Return-Path: marcus-sup@quintic.co.uk X-Envelope-From: marcus-sup@quintic.co.uk X-MDaemon-Deliver-To: sup-devel@rubyforge.org Message-ID: <4B961955.7000306@quintic.co.uk> Date: Tue, 09 Mar 2010 09:48:05 +0000 From: marcus-sup@quintic.co.uk User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: sup-devel@rubyforge.org References: <1268089517.99.0.931999852916.issue74@masanjin.net> In-Reply-To: <1268089517.99.0.931999852916.issue74@masanjin.net> Subject: Re: [sup-devel] [issue74] sup-dump producing empty file in latest release X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org On 08/03/2010 23:05, anonymous wrote: > sup-dump produces an empty dump file with git next (0.11 is probably closest > release). I updated this morning after the release announcement and started the > process to switch to xapian. Luckily I checked the dumpfile produced because it > turned out empty:( I reported this, so if any more information is needed I'm on this list (and obviously I'm tracking it in the issue tracker). Marcus _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel