From: Rich Lane <rlane@club.cc.cmu.edu>
To: Ned Ludd <edwardludd@gmail.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Sup-sync exception
Date: Mon, 23 Nov 2009 18:33:06 -0500 [thread overview]
Message-ID: <1259018950-sup-9876@zyrg.net> (raw)
In-Reply-To: <65a36ed50911200750q53cda26h5c5d374c6228a5a@mail.gmail.com>
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 <top (required)>'
> 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 `<top
> (required)>'
> from /usr/bin/supbin/sup-sync:19:in `load'
> from /usr/bin/supbin/sup-sync:19:in `<main>'
>
>
> [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
next prev parent reply other threads:[~2009-11-23 23:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 15:50 Ned Ludd
2009-11-21 5:18 ` Andrei Thorp
2009-11-23 23:33 ` Rich Lane [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-05 20:29 Mark Anderson
2009-11-06 15:13 ` rick.tessner
2009-11-06 20:06 ` Mark Anderson
2009-11-07 2:16 ` Anthony Martinez
2009-11-07 4:10 ` Mark Alexander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1259018950-sup-9876@zyrg.net \
--to=rlane@club.cc.cmu.edu \
--cc=edwardludd@gmail.com \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox