From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] NoMethodError running sup-config
Date: Thu, 24 Jan 2008 16:26:50 -0800 [thread overview]
Message-ID: <1201220266-sup-191@south> (raw)
In-Reply-To: <B47C5822-EFB0-4680-9932-F8C2FAC7C78A@gmail.com>
Reformatted excerpts from Sho Fukamachi's message of 2008-01-24:
> I realise it's probably something dumb I'm doing but I did try a
> couple of times. Any clues?
Nope, this is an Official Bug. Sorry! The following minor patch should
fix it. Git master and next have been updated with this.
diff --git a/lib/sup/mbox/ssh-file.rb b/lib/sup/mbox/ssh-file.rb
index 25074be..d474636 100644
--- a/lib/sup/mbox/ssh-file.rb
+++ b/lib/sup/mbox/ssh-file.rb
@@ -122,6 +122,7 @@ class SSHFile
def seek loc; @offset = loc; end
def tell; @offset; end
def total; size; end
+ def path; @fn end
def size
if @file_size.nil? || (Time.now - @last_size_check) > SIZE_CHECK_INTERVAL
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-01-25 0:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 8:11 Sho Fukamachi
2008-01-25 0:26 ` William Morgan [this message]
2008-01-25 10:35 ` Sho Fukamachi
2008-01-30 17:14 ` William Morgan
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=1201220266-sup-191@south \
--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