From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.117.16 with SMTP id p16cs612944agc; Thu, 15 Oct 2009 06:46:01 -0700 (PDT) Received: by 10.224.43.133 with SMTP id w5mr21595qae.376.1255614359750; Thu, 15 Oct 2009 06:45:59 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 33si208040qyk.94.2009.10.15.06.45.59; Thu, 15 Oct 2009 06:45:59 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-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-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 567E113C896E; Thu, 15 Oct 2009 09:45:59 -0400 (EDT) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id A536D18582C1 for ; Thu, 15 Oct 2009 09:45:50 -0400 (EDT) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1MyQeL-0001AX-5b for sup-talk@rubyforge.org; Thu, 15 Oct 2009 06:45:49 -0700 From: William Morgan To: sup-talk In-reply-to: <1255526768-sup-3152@tilus.net> References: <1255526768-sup-3152@tilus.net> Date: Thu, 15 Oct 2009 06:45:47 -0700 Message-Id: <1255612303-sup-410@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-talk] Sup finds ghost messages X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Reformatted excerpts from Tero Tilus's message of 2009-10-14: > sup-sync --all (using xapian) from a new source occasionally says 1-2 > messages already were in the index, even if they most certainly > weren't. I noticed this when I added sup-talk archives to my index. Can you run with -v and grep to make sure those message ids don't actually appear more than once in the mbox file? If they don't, can you isolate a particular one and use devel/console.sh to find out where Sup thinks the previous occurence is? > pps. Why bugs to this list? Why not use a tracker? (besides that sup > is awesome tracker too ;) If there's a good one out there I'd like to hear about it. We used ditz for a while because I hate clicking the mouse, but eventually it became too much effort. -- William _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk