Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: "Jason O'Conal" <jason.oconal@ieee.org>
To: sup-talk@rubyforge.org
Subject: [sup-talk] (no subject)
Date: Sat, 10 Dec 2011 13:38:30 +1030	[thread overview]
Message-ID: <CAFMfzmCP+dHNY5n8He9ZOYPx6xDtAh2BC82O94cekf-P8r6TXw@mail.gmail.com> (raw)

Hi,

I've been having trouble getting sup to work with my gmail account
downloaded by offlineimap. I have set up everything according to the
tutorial available at
http://sup.rubyforge.org/wiki/wiki.pl?GmailOfflineImapSmtp

I can't get sup-sync to run. I get the following error message:

/usr/lib/ruby/1.8/yaml.rb:133:in `transfer': invalid subclass (TypeError)
        from /usr/lib/ruby/1.8/yaml.rb:133:in `node_import'
        from /usr/lib/ruby/1.8/yaml.rb:133:in `load'
        from /usr/lib/ruby/1.8/yaml.rb:133:in `load'
        from /usr/lib/ruby/1.8/yaml.rb:144:in `load_file'
        from /usr/lib/ruby/1.8/yaml.rb:143:in `open'
        from /usr/lib/ruby/1.8/yaml.rb:143:in `load_file'
        from /usr/lib64/ruby/gems/1.8/gems/sup-0.12.1/lib/sup.rb:136:in
`load_yaml_obj'
        from /usr/lib64/ruby/gems/1.8/gems/sup-0.12.1/lib/sup.rb:266:in
`load_config'
        from /usr/lib64/ruby/gems/1.8/gems/sup-0.12.1/lib/sup.rb:157:in `start'
        from /usr/lib64/ruby/gems/1.8/gems/sup-0.12.1/bin/sup-sync:80
        from /usr/bin/sup-sync:19:in `load'
        from /usr/bin/sup-sync:19

I have tried to search for others with this error, but can't find
anything relevant (tried only using folders without spaces to no
avail). Any ideas?


Kind regards,

Jason O'Conal
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


             reply	other threads:[~2011-12-10  3:32 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-10  3:08 Jason O'Conal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-11-15  0:49 Matthias Vallentin
2010-11-15  1:42 ` Edward Z. Yang
2010-11-15  6:57   ` Matthias Vallentin
2010-11-15  8:06     ` Helge Titlestad
2010-11-20 19:04       ` Matthias Vallentin
2010-11-21  1:10         ` Tero Tilus
2010-11-21  1:51           ` Matthias Vallentin
2010-11-15  1:46 ` Ben Walton
2010-11-15  1:50 ` Matias Aguirre
2009-06-08  0:02 Ben Walton
2009-06-11 23:50 ` Ben Walton
2009-06-12  3:44   ` William Morgan
2009-06-12 13:15     ` Ben Walton
2009-06-12 18:23 ` William Morgan
2009-06-01  1:01 Ben Walton
2009-06-01  1:04 ` Ben Walton
2009-06-01  2:13 ` Ben Walton
2009-06-04  2:04 ` Ross Macduff
2009-02-16  6:45 Michael John Stipicevic
2009-02-16  6:45 Michael John Stipicevic
2009-02-16  6:45 Michael John Stipicevic
2009-02-16  6:45 Michael John Stipicevic
2009-02-16  6:45 Michael John Stipicevic
2009-02-16  6:45 Michael John Stipicevic
2009-02-16  6:45 Michael John Stipicevic
2009-02-16  6:44 Michael John Stipicevic
2009-02-16  6:27 Michael John Stipicevic
2009-02-16  6:25 Michael John Stipicevic
2009-02-16  6:25 Michael John Stipicevic
2009-02-16  6:25 Michael John Stipicevic
2009-02-16  6:25 Michael John Stipicevic
2009-02-16  6:25 Michael John Stipicevic
2009-02-16  6:25 Michael John Stipicevic
2009-02-16  6:25 Michael John Stipicevic
2009-02-16  8:53 ` Ian Smith
2009-02-16 14:08   ` William Morgan
2009-02-16 14:42     ` Mike Stipicevic
2009-02-16  6:25 Michael John Stipicevic
2008-01-05 19:29 thefed

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=CAFMfzmCP+dHNY5n8He9ZOYPx6xDtAh2BC82O94cekf-P8r6TXw@mail.gmail.com \
    --to=jason.oconal@ieee.org \
    --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