From mboxrd@z Thu Jan  1 00:00:00 1970
Received: by 10.86.87.8 with SMTP id k8cs53217fgb;
        Mon, 8 Mar 2010 15:13:09 -0800 (PST)
Received: by 10.224.95.202 with SMTP id e10mr208323qan.171.1268089988678;
        Mon, 08 Mar 2010 15:13:08 -0800 (PST)
Return-Path: <sup-devel-bounces@rubyforge.org>
Received: from rubyforge.org (rubyforge.org [205.234.109.19])
        by mx.google.com with ESMTP id 2si12720993qwi.21.2010.03.08.15.13.08;
        Mon, 08 Mar 2010 15:13:08 -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 F1B971588062;
	Mon,  8 Mar 2010 18:13:07 -0500 (EST)
Received: from entry.masanjin.net (masanjin.net [209.20.72.13])
	by rubyforge.org (Postfix) with ESMTP id D5DFA18582CE
	for <sup-devel@rubyforge.org>; Mon,  8 Mar 2010 18:05:20 -0500 (EST)
Received: from localhost ([127.0.0.1] helo=entry.masanjin.net)
	by entry.masanjin.net with esmtp (Exim 4.69)
	(envelope-from <roundup-admin@masanjin.net>) id 1Nom0k-0003J1-2o
	for sup-devel@rubyforge.org; Mon, 08 Mar 2010 18:05:19 -0500
MIME-Version: 1.0
To: sup-devel@rubyforge.org
From: anonymous <sup-bugs@masanjin.net>
Date: Mon, 08 Mar 2010 23:05:18 +0000
Precedence: bulk
X-Roundup-Name: Sup issue tracker
X-Roundup-Loop: hello
X-Roundup-Version: 1.4.10
Message-Id: <1268089517.99.0.931999852916.issue74@masanjin.net>
X-Roundup-issue-status: unread
X-Roundup-issue-priority: bug
In-Reply-To: <1268089517.99.0.931999852916.issue74@masanjin.net>
Subject: [sup-devel] [issue74] sup-dump producing empty file in latest
	release
X-BeenThere: sup-devel@rubyforge.org
X-Mailman-Version: 2.1.12
Reply-To: Sup issue tracker <sup-bugs@masanjin.net>,
	Sup developer discussion <sup-devel@rubyforge.org>
List-Id: Sup developer discussion <sup-devel.rubyforge.org>
List-Unsubscribe: <http://rubyforge.org/mailman/options/sup-devel>,
	<mailto:sup-devel-request@rubyforge.org?subject=unsubscribe>
List-Archive: <http://rubyforge.org/pipermail/sup-devel>
List-Post: <mailto:sup-devel@rubyforge.org>
List-Help: <mailto:sup-devel-request@rubyforge.org?subject=help>
List-Subscribe: <http://rubyforge.org/mailman/listinfo/sup-devel>,
	<mailto:sup-devel-request@rubyforge.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sup-devel-bounces@rubyforge.org
Errors-To: sup-devel-bounces@rubyforge.org


New submission from anonymous:

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 :(

----------
messages: 187
nosy: anonymous
priority: bug
ruby_version: 1.8.5
status: unread
sup_version: 0.11/next
title: sup-dump producing empty file in latest release

_________________________________________
Sup issue tracker <sup-bugs@masanjin.net>
<http://masanjin.net/sup-bugs/issue74>
_________________________________________
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel