sup

A curses threads-with-tags style email client

sup-website.git

git clone https://supmua.dev/git/sup-website/

community/pipermail-archives/sup-talk/2012-05.txt (4983B) - raw

      1 From jim@gonzul.net  Tue May  1 05:00:14 2012
      2 From: jim@gonzul.net (Jim Cheetham)
      3 Date: Tue, 1 May 2012 17:00:14 +1200
      4 Subject: [sup-talk] sup dislikes gpgme on Ubuntu 12.04
      5 Message-ID: <CA+2knqsHzGNON8Cz1kHuRdTREy3M2omQUGkg7ATd+3m6sUQ6+Q@mail.gmail.com>
      6 
      7 The Ubuntu-packaged sup-mail crashes with :-
      8 
      9 [Tue May 01 16:51:14 +1200 2012] ERROR: oh crap, an exception
     10 ----------------------------------------------------------------
     11 I'm very sorry. It seems that an error occurred in Sup. Please
     12 accept my sincere apologies. Please submit the contents of
     13 /home/cheja23p/.sup/exception-log.txt and a brief report of the
     14 circumstances to http://masanjin.net/sup-bugs/ so that I might
     15 address this problem. Thank you!
     16 
     17 Sincerely,
     18 William
     19 ----------------------------------------------------------------
     20 
     21 --- NoMethodError from thread: poll after loading inbox
     22 undefined method `empty' for GPGME::Data:Class
     23 /usr/lib/ruby/1.8/sup/crypto.rb:181:in `verify'
     24 /usr/lib/ruby/1.8/sup/util.rb:618:in `send'
     25 /usr/lib/ruby/1.8/sup/util.rb:618:in `method_missing'
     26 /usr/lib/ruby/1.8/sup/message.rb:558:in `inline_gpg_to_chunks'
     27 /usr/lib/ruby/1.8/sup/message.rb:520:in `message_to_chunks'
     28 /usr/lib/ruby/1.8/sup/message.rb:259:in `load_from_source!'
     29 /usr/lib/ruby/1.8/sup/message.rb:328:in `build_from_source'
     30 /usr/lib/ruby/1.8/sup/poll.rb:158:in `poll_from'
     31 /usr/lib/ruby/1.8/sup/maildir.rb:106:in `poll'
     32 /usr/lib/ruby/1.8/sup/util.rb:615:in `each_with_index'
     33 /usr/lib/ruby/1.8/sup/maildir.rb:105:in `each'
     34 /usr/lib/ruby/1.8/sup/maildir.rb:105:in `each_with_index'
     35 /usr/lib/ruby/1.8/sup/maildir.rb:105:in `poll'
     36 /usr/lib/ruby/1.8/sup/maildir.rb:90:in `each'
     37 /usr/lib/ruby/1.8/sup/maildir.rb:90:in `poll'
     38 /usr/lib/ruby/1.8/sup/poll.rb:155:in `poll_from'
     39 /usr/lib/ruby/1.8/sup/poll.rb:113:in `do_poll'
     40 /usr/lib/ruby/1.8/sup/poll.rb:103:in `each'
     41 /usr/lib/ruby/1.8/sup/poll.rb:103:in `do_poll'
     42 /usr/lib/ruby/1.8/sup/poll.rb:102:in `synchronize'
     43 /usr/lib/ruby/1.8/sup/poll.rb:102:in `do_poll'
     44 /usr/lib/ruby/1.8/sup/util.rb:618:in `send'
     45 /usr/lib/ruby/1.8/sup/util.rb:618:in `method_missing'
     46 /usr/lib/ruby/1.8/sup/modes/poll-mode.rb:15:in `poll'
     47 /usr/lib/ruby/1.8/sup/poll.rb:49:in `poll_with_sources'
     48 /usr/lib/ruby/1.8/sup/poll.rb:68:in `poll'
     49 /usr/lib/ruby/1.8/sup/util.rb:618:in `send'
     50 /usr/lib/ruby/1.8/sup/util.rb:618:in `method_missing'
     51 /usr/bin/sup-mail:221
     52 /usr/lib/ruby/1.8/sup.rb:77:in `reporting_thread'
     53 /usr/lib/ruby/1.8/sup.rb:75:in `initialize'
     54 /usr/lib/ruby/1.8/sup.rb:75:in `new'
     55 /usr/lib/ruby/1.8/sup.rb:75:in `reporting_thread'
     56 /usr/bin/sup-mail:221
     57 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:684:in `call'
     58 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:684:in
     59 `__unprotected_load_threads'
     60 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:625:in `call'
     61 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:625:in
     62 `load_n_threads_background'
     63 /usr/lib/ruby/1.8/sup.rb:77:in `reporting_thread'
     64 /usr/lib/ruby/1.8/sup.rb:75:in `initialize'
     65 /usr/lib/ruby/1.8/sup.rb:75:in `new'
     66 /usr/lib/ruby/1.8/sup.rb:75:in `reporting_thread'
     67 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:623:in
     68 `load_n_threads_background'
     69 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:694:in
     70 `__unprotected_load_threads'
     71 (eval):12:in `load_threads'
     72 /usr/bin/sup-mail:221
     73 
     74 https://bugs.launchpad.net/debian/+source/sup-mail/+bug/890972
     75 suggests that this is very likely because Ubuntu is using ruby-gpgme
     76 version 2.0.0-1 (the replacement for libgpgme-ruby 1.0.8-3), but the
     77 changelog doesn't seem to mention anything about API changes, but does
     78 say it was packaged with the Gem2deb infrastructure.
     79 
     80 Has anyone got any suggestions for how I can get my sup working again?
     81 
     82 (*cough* besides going to heliotrope/turnsole, which is currently
     83 under investigation)
     84 
     85 -jim
     86 
     87 From matthieu.rakotojaona@gmail.com  Wed May 30 20:35:46 2012
     88 From: matthieu.rakotojaona@gmail.com (Matthieu Rakotojaona)
     89 Date: Wed, 30 May 2012 22:35:46 +0200
     90 Subject: [sup-talk] Documentation of the heliotrope API
     91 Message-ID: <CAMiZLn2ESrDxTFhfzLAH36-7gJy7oy6uCWAxKYxHD5M1A9Pe_A@mail.gmail.com>
     92 
     93 Hello everyone,
     94 
     95 While browsing the interwebs, I realized that many people are also
     96 tired of the cumbersomeness of the IMAP protocol, and a few of them
     97 has started some work on implementing what they would love to see. For
     98 instance, you can find a thread talking about it in [0] which links to
     99 a few other thoughts. What is interesting is that many people have the
    100 same approach to use JSON-over-HTTP in a RESTful manner. I think each
    101 of these implementations' problem is the same: they lack visibility to
    102 gather improvements.
    103 
    104 Seeing this, I thought that to give Heliotrope a little more
    105 visibility, we should improve the documentation a little bit. I have
    106 started [1] by the first step: the API. Feel free to comment back on
    107 this, or fork/edit the pages yourself.
    108 
    109 
    110 Cheers,
    111 
    112 -- 
    113 Matthieu RAKOTOJAONA
    114 
    115 
    116 [0] http://blog.gaborcselle.com/2010/02/how-to-replace-imap.html
    117 [1] https://github.com/rakoo/heliotrope/wiki/A-brief-overview-of-the-heliotrope-api
    118