From: gui-gui@netcourrier.com
To: supmua@googlegroups.com
Subject: Broken sup after gem update
Date: Tue, 24 Feb 2015 17:18:31 +0100 (CET) [thread overview]
Message-ID: <ea-mime-54eca457-b48-47aefade@www-1.netcourrier.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1469 bytes --]
Hello,
I updated my gems yesterday, and since then sup doesn't work and throw the following error:
/home/guiniol/.gem/ruby/2.2.0/gems/sup-0.21.0/lib/sup.rb:30:in `yaml_properties': undefined method `yaml_tag' for Redwood::MBox:Class (NoMethodError)
from /home/guiniol/.gem/ruby/2.2.0/gems/sup-0.21.0/lib/sup/mbox.rb:10:in `<class:MBox>'
from /home/guiniol/.gem/ruby/2.2.0/gems/sup-0.21.0/lib/sup/mbox.rb:6:in `<module:Redwood>'
from /home/guiniol/.gem/ruby/2.2.0/gems/sup-0.21.0/lib/sup/mbox.rb:4:in `<top (required)>'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:69:in `require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:69:in `require'
from /home/guiniol/.gem/ruby/2.2.0/gems/sup-0.21.0/lib/sup.rb:423:in `<top (required)>'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:69:in `require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:69:in `require'
from /home/guiniol/.gem/ruby/2.2.0/gems/sup-0.21.0/bin/sup:21:in `<top (required)>'
from /home/guiniol/.gem/ruby/2.2.0/bin/sup:23:in `load'
from /home/guiniol/.gem/ruby/2.2.0/bin/sup:23:in `<main>'
I didn't notice immediatly so I'm not sure which gems where updated, but there were only a few. I imagine redwood was one of them?
Anyhow, I'm not sure if anyone else is seeing this or if there's a problem with my config, but if anyone has a solution, I'm interested.
--
Guillaume
[-- Attachment #2: Type: text/html, Size: 1890 bytes --]
next reply other threads:[~2015-02-24 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 16:18 gui-gui [this message]
2015-03-11 3:04 ` [sup] " Joe Schlimmer
2015-03-11 20:10 ` gui-gui
2015-03-11 21:03 ` Matthieu Rakotojaona
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=ea-mime-54eca457-b48-47aefade@www-1.netcourrier.com \
--to=gui-gui@netcourrier.com \
--cc=supmua@googlegroups.com \
/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