Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Steven Hum <sdothum@gmail.com>
To: Steven Hum <sdothum@gmail.com>
Cc: Gaute Hope <eg@gaute.vetsj.com>, sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] sup 0.15?
Date: Sun, 10 Nov 2013 10:49:47 -0500	[thread overview]
Message-ID: <1384098458-sup-7304@luna> (raw)
In-Reply-To: <1384097900-sup-2821@luna>


Edit: regarding the rmail comment.. I noticed the sup-rmail-1.0.1 gem 
which I presume sup-0.15.0 installed.

Steven


Excerpts from Steven Hum's message of 2013-11-10 10:42:00 -0500:
> 
> Hello Gaute,
> 
> I did a gem install of 0.15.0 on a Debian Sid system and got this error:
> 
> 
> --- RuntimeError from thread: load threads for thread-index-mode
> invalid source 13
> /var/lib/gems/1.9.1/gems/sup-0.15.0/lib/sup/index.rb:237:in `block in build_message'
> /var/lib/gems/1.9.1/gems/sup-0.15.0/lib/sup/index.rb:235:in `map'
> /var/lib/gems/1.9.1/gems/sup-0.15.0/lib/sup/index.rb:235:in `build_message'
> /var/lib/gems/1.9.1/gems/sup-0.15.0/lib/sup/index.rb:161:in `block (2 levels) in each_id_by_date'
> /var/lib/gems/1.9.1/gems/sup-0.15.0/lib/sup/thread.rb:338:in `call'
> /var/lib/gems/1.9.1/gems/sup-0.15.0/lib/sup/thread.rb:338:in `block in load_n_threads'
> /var/lib/gems/1.9.1/gems/sup-0.15.0/lib/sup/index.rb:161:in `block in each_id_by_date'
> /var/lib/gems/1.9.1/gems/sup-0.15.0/lib/sup/index.rb:284:in `block in each_id'
> /var/lib/gems/1.9.1/gems/sup-0.15.0/lib/sup/index.rb:284:in `each'
> /var/lib/gems/1.9.1/gems/sup-0.15.0/lib/sup/index.rb:284:in `each_id'
> /var/lib/gems/1.9.1/gems/sup-0.15.0/lib/sup/index.rb:161:in `each_id_by_date'
> /var/lib/gems/1.9.1/gems/sup-0.15.0/lib/sup/thread.rb:334:in `load_n_threads'
> /var/lib/gems/1.9.1/gems/sup-0.15.0/lib/sup/modes/thread_index_mode.rb:674:in `load_n_threads'
> (eval):12:in `load_n_threads'
> /var/lib/gems/1.9.1/gems/sup-0.15.0/lib/sup/modes/thread_index_mode.rb:658:in `block in load_n_threads_background'
> /var/lib/gems/1.9.1/gems/sup-0.15.0/lib/sup.rb:87:in `block in reporting_thread'
> 
> 
> Gem version 0.14.1.1 works fine on Debian Sid (rmail did not appear to 
> be installed with 0.15.0 but that doesn't seem to be related to the 
> above error).
> 
> Regards,
> Steven
> 
> Excerpts from Gaute Hope's message of 2013-11-05 02:51:42 -0500:
> > hi there,
> > 
> > any objections to releasing sup 0.15 (I figured it deserves a whole new
> > version number!) with maildir-syncback as it is now? Is it ready to be
> > released into the wild?
> > 
> > (maildir-syncback is now in 'develop' - go ahead and test if you
> > haven't)
> > 
> > Cheers, Gaute
> > 
> 

-- 
"Truth or die."

Steven Hum  
5 - 28 Gilmour St  
Ottawa, ON K2P 0N3  
email sdothum@gmail.com  
tel 613.237.9058  


  reply	other threads:[~2013-11-10 15:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05  7:51 Gaute Hope
2013-11-05 19:36 ` [sup-devel] " Matthieu Rakotojaona
2013-11-10 15:42 ` Steven Hum
2013-11-10 15:49   ` Steven Hum [this message]
2013-11-10 19:45   ` Gaute Hope
2013-11-11 13:18     ` Steven Hum
2013-11-11 13:31       ` Gaute Hope
2013-11-12 19:42       ` Eric Weikl
2013-11-13  0:47         ` Steven Hum
2013-12-01 16:17           ` Eric Weikl

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=1384098458-sup-7304@luna \
    --to=sdothum@gmail.com \
    --cc=eg@gaute.vetsj.com \
    --cc=sup-devel@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