From: wmorgan-sup@masanjin.net (wmorgan-sup)
Subject: [sup-talk] oh crap, an exception
Date: Wed, 16 Jul 2008 17:00:26 -0700 [thread overview]
Message-ID: <1216248900-sup-5089@entry> (raw)
In-Reply-To: <1216111841-sup-5352@horst>
Reformatted excerpts from Georg Lehmann's message of 2008-07-15:
> After sup-add mbox+ssh://koef.xxxx.net/var/mail/grl:
> --- NoMethodError from thread: call #connect on
> mbox+ssh://koef.xxxx.net/var/mail/grl
> undefined method `shell' for #<Net::SSH::Connection::Session:0x2acd9ad1fca8>
> /opt/local/lib/ruby/gems/1.8/gems/sup-0.5/lib/sup/mbox/ssh-file.rb:175:in
> `unsafe_connect'
Hm. I actually haven't tried mbox+ssh since the very early days of Sup,
so that code has definitely experienced bitrot. I'll look into it.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-07-17 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 8:59 Georg Lehmann
2008-07-17 0:00 ` wmorgan-sup [this message]
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=1216248900-sup-5089@entry \
--to=wmorgan-sup@masanjin.net \
/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