From: Johannes Janosovits <johannes@walnutempire.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] exception --- RuntimeError from thread: poll after loading inbox
Date: Tue, 29 Nov 2011 23:19:21 +0100 [thread overview]
Message-ID: <1322604971-sup-3350@myhost> (raw)
In-Reply-To: <4ED5431B.2000407@walnutempire.de>
Excerpts from Johannes Janosovits's message of 2011-11-29 21:39:55 +0100:
> On 11/09/2011 08:52 PM, Gaute Hope wrote:
> > Excerpts from Gaute Hope's message of 2011-11-09 20:25:13 +0100:
> >> I am getting the same error now, after upgraded ruby and gems..
> >>
> >> bin/sup-sync:11: warning: method redefined; discarding old to_s
> >> /home/gaute/dev/ruby/sup.git/lib/sup.rb:18:in `id': wrong id called on
> > This seems to be due to the new yamler 'psych', by requiring the old one
> > 'sych' before 'yaml' it can be loaded.
> >
> > The proper fix is to expect content to be represented the way 'psych'
> > does it. This is not the same as the old way.
> >
> > Also the gem spec date was in the wrong format, see both attached
> > patches.
> >
> > - Gaute
> >
> >
> > _______________________________________________
> > sup-talk mailing list
> > sup-talk@rubyforge.org
> > http://rubyforge.org/mailman/listinfo/sup-talk
> This doesn't fix it for me, see http://pastebin.com/mZjR1Hap
>
> Sup was built from git and installed by "gem install sup". Anybody else
> running into these Problems?
>
> regards,
> Johannes
Sorry for the inconvenience, for some reason the installed files (in
/usr/lib/ruby/..... ) were still old and contained the bug. Perhaps sup
wasn't uninstalled properly and gem didn't update the files. Anyway, I
fixed the bug as proposed and sup runs again (Thanks for the patch)
regards,
Johannes
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-11-29 22:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 9:17 hollunder
2011-11-07 21:27 ` Tero Tilus
2011-11-08 9:57 ` hollunder
2011-11-09 19:25 ` Gaute Hope
2011-11-09 19:52 ` Gaute Hope
2011-11-18 19:34 ` hollunder
2011-11-21 20:36 ` Gaute Hope
2011-11-21 20:16 ` Philipp Überbacher
2011-11-21 21:18 ` Michael Stapelberg
2011-11-21 22:15 ` Philipp Überbacher
2011-11-21 22:24 ` Michael Stapelberg
2011-11-22 8:39 ` Philipp Überbacher
2011-11-21 23:48 ` Gaute Hope
[not found] ` <1321953145-sup-1447@eris>
2011-11-22 15:10 ` Gaute Hope
2011-11-18 20:55 ` Michael Stapelberg
2011-11-19 0:33 ` [sup-talk] small patch and build error hollunder
2011-11-21 20:29 ` Gaute Hope
2011-11-29 20:39 ` [sup-talk] exception --- RuntimeError from thread: poll after loading inbox Johannes Janosovits
2011-11-29 22:19 ` Johannes Janosovits [this message]
2011-12-17 18:47 ` Hamish D
2011-11-08 13:39 ` 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=1322604971-sup-3350@myhost \
--to=johannes@walnutempire.de \
--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