From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.27.4 with SMTP id a4cs491573aga; Mon, 23 Nov 2009 15:33:44 -0800 (PST) Received: by 10.224.65.223 with SMTP id k31mr2833233qai.268.1259019222963; Mon, 23 Nov 2009 15:33:42 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 13si6518220qyk.97.2009.11.23.15.33.42; Mon, 23 Nov 2009 15:33:42 -0800 (PST) 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 5BB981858320; Mon, 23 Nov 2009 18:33:42 -0500 (EST) Received: from pion.club.cc.cmu.edu (PION.CLUB.CC.cmu.edu [128.237.157.88]) by rubyforge.org (Postfix) with ESMTP id 5104B18582BC for ; Mon, 23 Nov 2009 18:33:06 -0500 (EST) Received: from rlane by pion.club.cc.cmu.edu with local (Exim 4.69) (envelope-from ) id 1NCiP4-0003sx-GQ; Mon, 23 Nov 2009 18:33:06 -0500 From: Rich Lane To: Ned Ludd In-reply-to: <65a36ed50911200750q53cda26h5c5d374c6228a5a@mail.gmail.com> References: <65a36ed50911200750q53cda26h5c5d374c6228a5a@mail.gmail.com> Date: Mon, 23 Nov 2009 18:33:06 -0500 Message-Id: <1259018950-sup-9876@zyrg.net> User-Agent: Sup/git Cc: sup-talk Subject: Re: [sup-talk] Sup-sync exception 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 Excerpts from Ned Ludd's message of Fri Nov 20 10:50:47 -0500 2009: > There was a message about this a week or so ago. Did anyone ever find a fix? > > When I run "sup-sync", regardless or the source (I tried IMAP and > Maildir), I get this error: > > $ sup-sync > Scanning maildir:/home/nedludd/.mail/INBOX... > /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/lib/sup/source.rb:88:in `done?': > undefined method `>=' for true:TrueClass (NoMethodError) > from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/lib/sup/util.rb:560:in `__pass' > from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/lib/sup/util.rb:547:in > `method_missing' > from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/lib/sup/poll.rb:137:in > `each_message_from' > from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/lib/sup/util.rb:520:in > `method_missing' > from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/bin/sup-sync:146:in `block > in ' > from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/bin/sup-sync:141:in `each' > from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/bin/sup-sync:141:in ` (required)>' > from /usr/bin/supbin/sup-sync:19:in `load' > from /usr/bin/supbin/sup-sync:19:in `
' > > > [I'm on Arch with sup 0.9 and Ruby 1.9.1] Is there a cur_offset key for every source in sources.yaml? If not (or if it is nil/blank) see if setting cur_offset to 0 fixes it. _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk