From: Gaute Hope <eg@gaute.vetsj.com>
To: "Sup Talk" <sup-talk@rubyforge.org>,
"Philipp Überbacher" <hollunder@lavabit.com>
Subject: Re: [sup-talk] exception --- RuntimeError from thread: poll after loading inbox
Date: Tue, 22 Nov 2011 00:48:09 +0100 [thread overview]
Message-ID: <1321919182-sup-3332@qwerzila> (raw)
In-Reply-To: <1321913598-sup-6512@eris>
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
Excerpts from Philipp Überbacher's message of 2011-11-21 23:15:21 +0100:
> Excerpts from Michael Stapelberg's message of 2011-11-21 22:18:36 +0100:
> > Hi Philipp,
> >
> > Excerpts from Philipp Überbacher's message of 2011-11-21 20:16:28 +0000:
> > > The last sup release definitely doesn't work with ruby 1.9.3.
> > Use the git version, that works with 1.9.3, see my post at
> > http://rubyforge.org/pipermail/sup-devel/2011-November/001256.html
> > (and replace the mangled " at " with @)
> >
> > Best regards,
> > Michael
>
> Thanks Michael.
> Since you're on 1.9.3 I assume you're an arch user as well? If so, did
> you manage to create a PKGBUILD that uses those instructions? It's just
> that I rather have a package that I can uninstall again if necessary.
>
> Regards,
> Philipp
I used this work-around (patch attached):
http://stackoverflow.com/questions/4932881/gemcutter-rake-build-now-throws-undefined-method-write-for-syckemitter
which enables me to install it as normal with 'gem'.
- Gaute
[-- Attachment #2: 0001-Require-psych-in-Rakefile-to-avoid-syck-error-when-c.patch --]
[-- Type: application/octet-stream, Size: 577 bytes --]
From 8e6f7552ca5e3b3b0ecd56990098feff417ba0d5 Mon Sep 17 00:00:00 2001
From: Gaute Hope <eg@gaute.vetsj.com>
Date: Tue, 22 Nov 2011 00:26:27 +0100
Subject: [PATCH] Require psych in Rakefile to avoid syck error when compiling
gem
---
Rakefile | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/Rakefile b/Rakefile
index cdf2273..e041c1b 100644
--- a/Rakefile
+++ b/Rakefile
@@ -30,6 +30,7 @@ task :upload_report do |t|
end
$:.push "lib"
+require 'psych'
require 'rubygems'
require_relative "sup-files"
require_relative "sup-version"
--
1.7.7.3
next prev parent reply other threads:[~2011-11-21 22:51 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 [this message]
[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
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=1321919182-sup-3332@qwerzila \
--to=eg@gaute.vetsj.com \
--cc=hollunder@lavabit.com \
--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