* [sup-talk] exception --- RuntimeError from thread: poll after loading inbox
@ 2011-11-07 9:17 hollunder
2011-11-07 21:27 ` Tero Tilus
2011-11-08 13:39 ` Mark Alexander
0 siblings, 2 replies; 21+ messages in thread
From: hollunder @ 2011-11-07 9:17 UTC (permalink / raw)
To: sup-talk
Hi there,
since yesterday sup crashes after running offlineimap.
I wonder what component is at fault.
This happened after an upgrade of some libraries, but it's not easy to
roll back. It would really help if I know what component is causing this.
Here's the whole log of the update in question:
[2009-12-07 03:59] installed filesystem (2009.07-1)
[2009-12-07 03:59] installed dbus-core (1.2.16-1)
[2009-12-07 03:59] installed dcron (3.2-4)
[2009-12-07 03:59] installed dhcpcd (5.1.3-1)
[2009-12-07 03:59] installed dialog (1.1_20080819-3)
[2009-12-07 03:59] installed diffutils (2.8.1-6)
[2009-12-07 03:59] installed file (5.03-2)
[2009-12-07 03:59] installed gawk (3.1.7-1)
[2009-12-07 03:59] installed gdbm (1.8.3-6)
[2009-12-07 03:59] installed gen-init-cpio (2.6.17-3)
[2009-12-07 03:59] installed gettext (0.17-3)
[2009-12-07 03:59] installed pcre (8.00-1)
[2009-12-07 03:59] installed grep (2.5.4-3)
[2009-12-07 03:59] installed perl (5.10.1-5)
[2009-12-07 03:59] installed groff (1.20.1-3)
[2009-12-07 03:59] installed sed (4.2.1-1)
[2009-12-07 03:59] installed grub (0.97-16)
[2009-12-07 03:59] installed hdparm (9.27-1)
[2009-12-07 03:59] installed libusb (0.1.12-3)
[2009-12-07 03:59] installed glib2 (2.22.2-1)
[2009-12-07 03:59] installed udev (146-2)
[2009-12-07 03:59] installed net-tools (1.60-14)
[2009-12-07 03:59] installed kbd (1.15-2)
[2009-12-07 03:59] installed sysvinit (2.86-5)
[2009-12-07 03:59] installed initscripts (2009.08-1)
[2009-12-07 03:59] installed iputils (20071127-2)
[2009-12-07 03:59] installed jfsutils (1.1.14-1)
[2009-12-07 03:59] installed kernel26-firmware (2.6.31-1)
[2009-12-07 03:59] installed module-init-tools (3.11.1-1)
[2009-12-07 03:59] installed klibc (1.5.15-3)
[2009-12-07 03:59] installed klibc-extras (2.5-4)
[2009-12-07 03:59] installed klibc-udev (141-3)
[2009-12-07 03:59] installed klibc-module-init-tools (3.8-1)
[2009-12-07 03:59] installed klibc-kbd (1.15.20080312-10)
[2009-12-07 03:59] installed mkinitcpio (0.5.26-1)
Any hints appreciated,
regards,
Philipp
$ sup
[2011-11-07 10:05:25 +0100] ERROR: oh crap, an exception
----------------------------------------------------------------
I'm very sorry. It seems that an error occurred in Sup. Please
accept my sincere apologies. Please submit the contents of
/home/murks/.sup/exception-log.txt and a brief report of the
circumstances to http://masanjin.net/sup-bugs/ so that I might
address this problem. Thank you!
Sincerely,
William
----------------------------------------------------------------
--- RuntimeError from thread: poll after loading inbox
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/index.rb:551:in `find_docid'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/index.rb:556:in `find_doc'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/index.rb:566:in `get_entry'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/index.rb:196:in `block in
build_message'
/usr/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/index.rb:575:in
`synchronize'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/index.rb:196:in
`build_message'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/util.rb:609:in
`method_missing'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/poll.rb:159:in `block in
poll_from'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/maildir.rb:106:in `block
(2 levels) in poll'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/maildir.rb:105:in `each'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/maildir.rb:105:in
`each_with_index'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/maildir.rb:105:in `block
in poll'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/maildir.rb:90:in `each'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/maildir.rb:90:in `poll'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/poll.rb:155:in `poll_from'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/poll.rb:113:in `block (2
levels) in do_poll'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/poll.rb:103:in `each'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/poll.rb:103:in `block in
do_poll'
<internal:prelude>:10:in `synchronize'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/poll.rb:102:in `do_poll'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/util.rb:609:in
`method_missing'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/modes/poll-mode.rb:15:in
`poll'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/poll.rb:49:in
`poll_with_sources'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/poll.rb:68:in `poll'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/util.rb:609:in
`method_missing'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/bin/sup:212:in `block (2 levels)
in <module:Redwood>'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup.rb:78:in `block in
reporting_thread'
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [sup-talk] exception --- RuntimeError from thread: poll after loading inbox
2011-11-07 9:17 [sup-talk] exception --- RuntimeError from thread: poll after loading inbox hollunder
@ 2011-11-07 21:27 ` Tero Tilus
2011-11-08 9:57 ` hollunder
2011-11-08 13:39 ` Mark Alexander
1 sibling, 1 reply; 21+ messages in thread
From: Tero Tilus @ 2011-11-07 21:27 UTC (permalink / raw)
To: Sup users
hollunder, 2011-11-07 11:17:
> I wonder what component is at fault.
Looks like it fails when adding new messages from maildir to index.
Somehow term_docids for the id of newly received message yields more
than one documents from index. Could it be that one of the new
messages in your maildir has a mangled message id?
I'm not familiar with offlineimap. You might need some extra steps or
a completely different approach here, but: You could try to (back up
and temporarily) move new messages out of your inbox (using mutt etc)
and then retry with sup.
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [sup-talk] exception --- RuntimeError from thread: poll after loading inbox
2011-11-07 21:27 ` Tero Tilus
@ 2011-11-08 9:57 ` hollunder
2011-11-09 19:25 ` Gaute Hope
0 siblings, 1 reply; 21+ messages in thread
From: hollunder @ 2011-11-08 9:57 UTC (permalink / raw)
To: Sup users
> hollunder, 2011-11-07 11:17:
>> I wonder what component is at fault.
>
> Looks like it fails when adding new messages from maildir to index.
> Somehow term_docids for the id of newly received message yields more
> than one documents from index. Could it be that one of the new
> messages in your maildir has a mangled message id?
>
> I'm not familiar with offlineimap. You might need some extra steps or
> a completely different approach here, but: You could try to (back up
> and temporarily) move new messages out of your inbox (using mutt etc)
> and then retry with sup.
>
> --
> Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
> _______________________________________________
> sup-talk mailing list
> sup-talk@rubyforge.org
> http://rubyforge.org/mailman/listinfo/sup-talk
>
>
Thanks,
I'll try that kind of stuff if I manage to, never used another mail reader
than sup.
Anyway, today a new ruby update came along and even after rebuilding
everything I could think of, including sup, sup doesn't start anymore. Not
sure it's the same issue.
Also tried sup-git, but it doesn't seem to build at all.
$ sup
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': iconv will
be deprecated in the future, use String#encode instead.
/usr/lib/ruby/gems/1.9.1/gems/gettext-2.1.0/lib/gettext/runtime/locale_path.rb:20:
Use RbConfig instead of obsolete and deprecated Config.
[2011-11-08 10:48:46 +0100] ERROR: oh crap, an exception
----------------------------------------------------------------
I'm very sorry. It seems that an error occurred in Sup. Please
accept my sincere apologies. Please submit the contents of
/home/murks/.sup/exception-log.txt and a brief report of the
circumstances to http://masanjin.net/sup-bugs/ so that I might
address this problem. Thank you!
Sincerely,
William
----------------------------------------------------------------
--- RuntimeError from thread: main
wrong id called on
{"uri"=>"maildir:/home/murks/.imap/lavabit_murks_local/Inbox",
"usual"=>true, "archived"=>false, "id"=>1, "labels"=>["murks_lavabit",
"personal"]}
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup.rb:18:in `id'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/source.rb:207:in `block
(2 levels) in load_sources'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/source.rb:207:in `map'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/source.rb:207:in `block
in load_sources'
/usr/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/source.rb:206:in
`load_sources'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/util.rb:609:in
`method_missing'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/index.rb:92:in `load'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/util.rb:609:in
`method_missing'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/bin/sup:154:in `<module:Redwood>'
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/bin/sup:69:in `<top (required)>'
/usr/bin/sup:19:in `load'
/usr/bin/sup:19:in `<main>'
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [sup-talk] exception --- RuntimeError from thread: poll after loading inbox
2011-11-07 9:17 [sup-talk] exception --- RuntimeError from thread: poll after loading inbox hollunder
2011-11-07 21:27 ` Tero Tilus
@ 2011-11-08 13:39 ` Mark Alexander
1 sibling, 0 replies; 21+ messages in thread
From: Mark Alexander @ 2011-11-08 13:39 UTC (permalink / raw)
To: hollunder; +Cc: sup-talk
Excerpts from hollunder's message of Mon Nov 07 04:17:05 -0500 2011:
> since yesterday sup crashes after running offlineimap.
I don't know if my experience is helpful at all, but I tried
offlineimap a couple of years ago and had to abandon it, because it
was altering the mail store (deleting messages, mainly) and sup didn't
like that. I was using an older version of sup at the time, and
perhaps newer versions are suppose to handle this situation better.
But I went back to fetchmail + maildrop, and have had very few
problems since. It just seems safer to not use tools that can alter
mail directories after they've been populated.
The couple of times I've had sup crash on me, I fixed the problem by
using sup-dump followed by sup-sync --restore (which preserves
labels).
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [sup-talk] exception --- RuntimeError from thread: poll after loading inbox
2011-11-08 9:57 ` hollunder
@ 2011-11-09 19:25 ` Gaute Hope
2011-11-09 19:52 ` Gaute Hope
0 siblings, 1 reply; 21+ messages in thread
From: Gaute Hope @ 2011-11-09 19:25 UTC (permalink / raw)
To: Sup users
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
{"uri"=>"maildir:///home/gaute/.mail/gaute.vetsj.com/Gmail.All_Mail",
"usual"=>true, "archived"=>false, "id"=>3, "labels"=>["inbox"]}
(RuntimeError)
from /home/gaute/dev/ruby/sup.git/lib/sup/source.rb:207:in `block (2
levels) in load_sources'
from /home/gaute/dev/ruby/sup.git/lib/sup/source.rb:207:in `map'
from /home/gaute/dev/ruby/sup.git/lib/sup/source.rb:207:in `block in
load_sources'
from /usr/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
from /home/gaute/dev/ruby/sup.git/lib/sup/source.rb:206:in `load_sources'
from /home/gaute/dev/ruby/sup.git/lib/sup/util.rb:572:in `method_missing'
from /home/gaute/dev/ruby/sup.git/lib/sup/index.rb:96:in `load'
from bin/sup-sync:100:in `<main>'
(same error when trying to start sup).
Also Ruby GPGME 2.0 seems to not be compatible with old API.
- gaute
On Tue, Nov 8, 2011 at 10:57 AM, <hollunder@lavabit.com> wrote:
>> hollunder, 2011-11-07 11:17:
>>> I wonder what component is at fault.
>>
>> Looks like it fails when adding new messages from maildir to index.
>> Somehow term_docids for the id of newly received message yields more
>> than one documents from index. Could it be that one of the new
>> messages in your maildir has a mangled message id?
>>
>> I'm not familiar with offlineimap. You might need some extra steps or
>> a completely different approach here, but: You could try to (back up
>> and temporarily) move new messages out of your inbox (using mutt etc)
>> and then retry with sup.
>>
>> --
>> Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
>> _______________________________________________
>> sup-talk mailing list
>> sup-talk@rubyforge.org
>> http://rubyforge.org/mailman/listinfo/sup-talk
>>
>>
>
> Thanks,
> I'll try that kind of stuff if I manage to, never used another mail reader
> than sup.
> Anyway, today a new ruby update came along and even after rebuilding
> everything I could think of, including sup, sup doesn't start anymore. Not
> sure it's the same issue.
>
> Also tried sup-git, but it doesn't seem to build at all.
>
> $ sup
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': iconv will
> be deprecated in the future, use String#encode instead.
> /usr/lib/ruby/gems/1.9.1/gems/gettext-2.1.0/lib/gettext/runtime/locale_path.rb:20:
> Use RbConfig instead of obsolete and deprecated Config.
> [2011-11-08 10:48:46 +0100] ERROR: oh crap, an exception
> ----------------------------------------------------------------
> I'm very sorry. It seems that an error occurred in Sup. Please
> accept my sincere apologies. Please submit the contents of
> /home/murks/.sup/exception-log.txt and a brief report of the
> circumstances to http://masanjin.net/sup-bugs/ so that I might
> address this problem. Thank you!
>
> Sincerely,
> William
> ----------------------------------------------------------------
> --- RuntimeError from thread: main
> wrong id called on
> {"uri"=>"maildir:/home/murks/.imap/lavabit_murks_local/Inbox",
> "usual"=>true, "archived"=>false, "id"=>1, "labels"=>["murks_lavabit",
> "personal"]}
> /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup.rb:18:in `id'
> /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/source.rb:207:in `block
> (2 levels) in load_sources'
> /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/source.rb:207:in `map'
> /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/source.rb:207:in `block
> in load_sources'
> /usr/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
> /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/source.rb:206:in
> `load_sources'
> /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/util.rb:609:in
> `method_missing'
> /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/index.rb:92:in `load'
> /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/util.rb:609:in
> `method_missing'
> /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/bin/sup:154:in `<module:Redwood>'
> /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/bin/sup:69:in `<top (required)>'
> /usr/bin/sup:19:in `load'
> /usr/bin/sup:19:in `<main>'
>
>
>
>
> _______________________________________________
> sup-talk mailing list
> sup-talk@rubyforge.org
> http://rubyforge.org/mailman/listinfo/sup-talk
>
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [sup-talk] exception --- RuntimeError from thread: poll after loading inbox
2011-11-09 19:25 ` Gaute Hope
@ 2011-11-09 19:52 ` Gaute Hope
2011-11-18 19:34 ` hollunder
` (3 more replies)
0 siblings, 4 replies; 21+ messages in thread
From: Gaute Hope @ 2011-11-09 19:52 UTC (permalink / raw)
To: Sup Talk
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
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
[-- Attachment #2: 0001-Use-correct-date-format-for-gem-spec.patch --]
[-- Type: application/octet-stream, Size: 862 bytes --]
From b0611fdff831a4ca7c973b96690c176bc82ad48c Mon Sep 17 00:00:00 2001
From: Gaute Hope <eg@gaute.vetsj.com>
Date: Wed, 9 Nov 2011 20:43:25 +0100
Subject: [PATCH 1/2] Use correct date format for gem spec
---
Rakefile | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Rakefile b/Rakefile
index 860f69b..cdf2273 100644
--- a/Rakefile
+++ b/Rakefile
@@ -38,7 +38,7 @@ require 'rake/gempackagetask.rb'
spec = Gem::Specification.new do |s|
s.name = %q{sup}
s.version = SUP_VERSION
- s.date = Time.now.to_s
+ s.date = Time.now.strftime "%Y-%m-%d"
s.authors = ["William Morgan"]
s.email = %q{wmorgan-sup@masanjin.net}
s.summary = %q{A console-based email client with the best features of GMail, mutt, and emacs. Features full text search, labels, tagged operations, multiple buffers, recent contacts, and more.}
--
1.7.7.3
[-- Attachment #3: 0002-Use-old-syck-module-for-YAML-parsing.patch --]
[-- Type: application/octet-stream, Size: 499 bytes --]
From e4bcb6b373dac4954d5bb64707e8aca6595f66e6 Mon Sep 17 00:00:00 2001
From: Gaute Hope <eg@gaute.vetsj.com>
Date: Wed, 9 Nov 2011 20:43:49 +0100
Subject: [PATCH 2/2] Use old 'syck' module for YAML parsing
---
lib/sup.rb | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/lib/sup.rb b/lib/sup.rb
index 169b73e..74d5cde 100644
--- a/lib/sup.rb
+++ b/lib/sup.rb
@@ -1,4 +1,5 @@
require 'rubygems'
+require 'syck'
require 'yaml'
require 'zlib'
require 'thread'
--
1.7.7.3
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [sup-talk] exception --- RuntimeError from thread: poll after loading inbox
2011-11-09 19:52 ` Gaute Hope
@ 2011-11-18 19:34 ` hollunder
2011-11-21 20:36 ` Gaute Hope
2011-11-18 20:55 ` Michael Stapelberg
` (2 subsequent siblings)
3 siblings, 1 reply; 21+ messages in thread
From: hollunder @ 2011-11-18 19:34 UTC (permalink / raw)
To: Sup Talk
Hi Gaute,
thanks for fixing stuff.
I tried to build from your git repo
(git://gitorious.org/sup/gautehs-mainline.git, branch:gauteisrunning).
However, it doesn't build, same as sup from the main repo. Do you know
what the problem isor how to fix it? Here's the build-ouput:
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': iconv will
be deprecated in the future, use String#encode instead.
/usr/lib/ruby/gems/1.9.1/gems/gettext-2.1.0/lib/gettext/runtime/locale_path.rb:20:
Use RbConfig instead of obsolete and deprecated Config.
[2011-11-18 20:22:06 +0100] WARNING: rake/gempackagetask is deprecated.
Use rubygems/package_task instead
mkdir -p pkg
mkdir -p pkg
mkdir -p pkg/sup-999
rm -f pkg/sup-999/CONTRIBUTORS
ln CONTRIBUTORS pkg/sup-999/CONTRIBUTORS
rm -f pkg/sup-999/README.txt
ln README.txt pkg/sup-999/README.txt
rm -f pkg/sup-999/LICENSE
ln LICENSE pkg/sup-999/LICENSE
rm -f pkg/sup-999/History.txt
ln History.txt pkg/sup-999/History.txt
rm -f pkg/sup-999/ReleaseNotes
ln ReleaseNotes pkg/sup-999/ReleaseNotes
mkdir -p pkg/sup-999/bin
rm -f pkg/sup-999/bin/sup
ln bin/sup pkg/sup-999/bin/sup
rm -f pkg/sup-999/bin/sup-add
ln bin/sup-add pkg/sup-999/bin/sup-add
rm -f pkg/sup-999/bin/sup-cmd
ln bin/sup-cmd pkg/sup-999/bin/sup-cmd
rm -f pkg/sup-999/bin/sup-config
ln bin/sup-config pkg/sup-999/bin/sup-config
rm -f pkg/sup-999/bin/sup-dump
ln bin/sup-dump pkg/sup-999/bin/sup-dump
rm -f pkg/sup-999/bin/sup-import-dump
ln bin/sup-import-dump pkg/sup-999/bin/sup-import-dump
rm -f pkg/sup-999/bin/sup-recover-sources
ln bin/sup-recover-sources pkg/sup-999/bin/sup-recover-sources
rm -f pkg/sup-999/bin/sup-server
ln bin/sup-server pkg/sup-999/bin/sup-server
rm -f pkg/sup-999/bin/sup-sync
ln bin/sup-sync pkg/sup-999/bin/sup-sync
rm -f pkg/sup-999/bin/sup-sync-back
ln bin/sup-sync-back pkg/sup-999/bin/sup-sync-back
rm -f pkg/sup-999/bin/sup-tweak-labels
ln bin/sup-tweak-labels pkg/sup-999/bin/sup-tweak-labels
mkdir -p pkg/sup-999/lib
rm -f pkg/sup-999/lib/sup.rb
ln lib/sup.rb pkg/sup-999/lib/sup.rb
mkdir -p pkg/sup-999/lib/sup
rm -f pkg/sup-999/lib/sup/hook.rb
ln lib/sup/hook.rb pkg/sup-999/lib/sup/hook.rb
rm -f pkg/sup-999/lib/sup/buffer.rb
ln lib/sup/buffer.rb pkg/sup-999/lib/sup/buffer.rb
rm -f pkg/sup-999/lib/sup/maildir.rb
ln lib/sup/maildir.rb pkg/sup-999/lib/sup/maildir.rb
rm -f pkg/sup-999/lib/sup/undo.rb
ln lib/sup/undo.rb pkg/sup-999/lib/sup/undo.rb
rm -f pkg/sup-999/lib/sup/util.rb
ln lib/sup/util.rb pkg/sup-999/lib/sup/util.rb
rm -f pkg/sup-999/lib/sup/search.rb
ln lib/sup/search.rb pkg/sup-999/lib/sup/search.rb
rm -f pkg/sup-999/lib/sup/draft.rb
ln lib/sup/draft.rb pkg/sup-999/lib/sup/draft.rb
rm -f pkg/sup-999/lib/sup/keymap.rb
ln lib/sup/keymap.rb pkg/sup-999/lib/sup/keymap.rb
rm -f pkg/sup-999/lib/sup/message.rb
ln lib/sup/message.rb pkg/sup-999/lib/sup/message.rb
rm -f pkg/sup-999/lib/sup/rfc2047.rb
ln lib/sup/rfc2047.rb pkg/sup-999/lib/sup/rfc2047.rb
rm -f pkg/sup-999/lib/sup/client.rb
ln lib/sup/client.rb pkg/sup-999/lib/sup/client.rb
rm -f pkg/sup-999/lib/sup/crypto.rb
ln lib/sup/crypto.rb pkg/sup-999/lib/sup/crypto.rb
rm -f pkg/sup-999/lib/sup/logger.rb
ln lib/sup/logger.rb pkg/sup-999/lib/sup/logger.rb
rm -f pkg/sup-999/lib/sup/colormap.rb
ln lib/sup/colormap.rb pkg/sup-999/lib/sup/colormap.rb
rm -f pkg/sup-999/lib/sup/sent.rb
ln lib/sup/sent.rb pkg/sup-999/lib/sup/sent.rb
rm -f pkg/sup-999/lib/sup/message-chunks.rb
ln lib/sup/message-chunks.rb pkg/sup-999/lib/sup/message-chunks.rb
rm -f pkg/sup-999/lib/sup/label.rb
ln lib/sup/label.rb pkg/sup-999/lib/sup/label.rb
rm -f pkg/sup-999/lib/sup/idle.rb
ln lib/sup/idle.rb pkg/sup-999/lib/sup/idle.rb
rm -f pkg/sup-999/lib/sup/update.rb
ln lib/sup/update.rb pkg/sup-999/lib/sup/update.rb
rm -f pkg/sup-999/lib/sup/poll.rb
ln lib/sup/poll.rb pkg/sup-999/lib/sup/poll.rb
rm -f pkg/sup-999/lib/sup/horizontal-selector.rb
ln lib/sup/horizontal-selector.rb pkg/sup-999/lib/sup/horizontal-selector.rb
rm -f pkg/sup-999/lib/sup/textfield.rb
ln lib/sup/textfield.rb pkg/sup-999/lib/sup/textfield.rb
rm -f pkg/sup-999/lib/sup/mbox.rb
ln lib/sup/mbox.rb pkg/sup-999/lib/sup/mbox.rb
rm -f pkg/sup-999/lib/sup/thread.rb
ln lib/sup/thread.rb pkg/sup-999/lib/sup/thread.rb
rm -f pkg/sup-999/lib/sup/server.rb
ln lib/sup/server.rb pkg/sup-999/lib/sup/server.rb
rm -f pkg/sup-999/lib/sup/tagger.rb
ln lib/sup/tagger.rb pkg/sup-999/lib/sup/tagger.rb
rm -f pkg/sup-999/lib/sup/mode.rb
ln lib/sup/mode.rb pkg/sup-999/lib/sup/mode.rb
rm -f pkg/sup-999/lib/sup/contact.rb
ln lib/sup/contact.rb pkg/sup-999/lib/sup/contact.rb
rm -f pkg/sup-999/lib/sup/time.rb
ln lib/sup/time.rb pkg/sup-999/lib/sup/time.rb
rm -f pkg/sup-999/lib/sup/protocol.rb
ln lib/sup/protocol.rb pkg/sup-999/lib/sup/protocol.rb
rm -f pkg/sup-999/lib/sup/person.rb
ln lib/sup/person.rb pkg/sup-999/lib/sup/person.rb
rm -f pkg/sup-999/lib/sup/source.rb
ln lib/sup/source.rb pkg/sup-999/lib/sup/source.rb
rm -f pkg/sup-999/lib/sup/interactive-lock.rb
ln lib/sup/interactive-lock.rb pkg/sup-999/lib/sup/interactive-lock.rb
rm -f pkg/sup-999/lib/sup/account.rb
ln lib/sup/account.rb pkg/sup-999/lib/sup/account.rb
rm -f pkg/sup-999/lib/sup/index.rb
ln lib/sup/index.rb pkg/sup-999/lib/sup/index.rb
mkdir -p pkg/sup-999/lib/sup/modes
rm -f pkg/sup-999/lib/sup/modes/thread-view-mode.rb
ln lib/sup/modes/thread-view-mode.rb
pkg/sup-999/lib/sup/modes/thread-view-mode.rb
rm -f pkg/sup-999/lib/sup/modes/person-search-results-mode.rb
ln lib/sup/modes/person-search-results-mode.rb
pkg/sup-999/lib/sup/modes/person-search-results-mode.rb
rm -f pkg/sup-999/lib/sup/modes/label-search-results-mode.rb
ln lib/sup/modes/label-search-results-mode.rb
pkg/sup-999/lib/sup/modes/label-search-results-mode.rb
rm -f pkg/sup-999/lib/sup/modes/scroll-mode.rb
ln lib/sup/modes/scroll-mode.rb pkg/sup-999/lib/sup/modes/scroll-mode.rb
rm -f pkg/sup-999/lib/sup/modes/console-mode.rb
ln lib/sup/modes/console-mode.rb pkg/sup-999/lib/sup/modes/console-mode.rb
rm -f pkg/sup-999/lib/sup/modes/resume-mode.rb
ln lib/sup/modes/resume-mode.rb pkg/sup-999/lib/sup/modes/resume-mode.rb
rm -f pkg/sup-999/lib/sup/modes/buffer-list-mode.rb
ln lib/sup/modes/buffer-list-mode.rb
pkg/sup-999/lib/sup/modes/buffer-list-mode.rb
rm -f pkg/sup-999/lib/sup/modes/forward-mode.rb
ln lib/sup/modes/forward-mode.rb pkg/sup-999/lib/sup/modes/forward-mode.rb
rm -f pkg/sup-999/lib/sup/modes/thread-index-mode.rb
ln lib/sup/modes/thread-index-mode.rb
pkg/sup-999/lib/sup/modes/thread-index-mode.rb
rm -f pkg/sup-999/lib/sup/modes/label-list-mode.rb
ln lib/sup/modes/label-list-mode.rb
pkg/sup-999/lib/sup/modes/label-list-mode.rb
rm -f pkg/sup-999/lib/sup/modes/compose-mode.rb
ln lib/sup/modes/compose-mode.rb pkg/sup-999/lib/sup/modes/compose-mode.rb
rm -f pkg/sup-999/lib/sup/modes/search-list-mode.rb
ln lib/sup/modes/search-list-mode.rb
pkg/sup-999/lib/sup/modes/search-list-mode.rb
rm -f pkg/sup-999/lib/sup/modes/file-browser-mode.rb
ln lib/sup/modes/file-browser-mode.rb
pkg/sup-999/lib/sup/modes/file-browser-mode.rb
rm -f pkg/sup-999/lib/sup/modes/contact-list-mode.rb
ln lib/sup/modes/contact-list-mode.rb
pkg/sup-999/lib/sup/modes/contact-list-mode.rb
rm -f pkg/sup-999/lib/sup/modes/search-results-mode.rb
ln lib/sup/modes/search-results-mode.rb
pkg/sup-999/lib/sup/modes/search-results-mode.rb
rm -f pkg/sup-999/lib/sup/modes/help-mode.rb
ln lib/sup/modes/help-mode.rb pkg/sup-999/lib/sup/modes/help-mode.rb
rm -f pkg/sup-999/lib/sup/modes/text-mode.rb
ln lib/sup/modes/text-mode.rb pkg/sup-999/lib/sup/modes/text-mode.rb
rm -f pkg/sup-999/lib/sup/modes/edit-message-async-mode.rb
ln lib/sup/modes/edit-message-async-mode.rb
pkg/sup-999/lib/sup/modes/edit-message-async-mode.rb
rm -f pkg/sup-999/lib/sup/modes/reply-mode.rb
ln lib/sup/modes/reply-mode.rb pkg/sup-999/lib/sup/modes/reply-mode.rb
rm -f pkg/sup-999/lib/sup/modes/poll-mode.rb
ln lib/sup/modes/poll-mode.rb pkg/sup-999/lib/sup/modes/poll-mode.rb
rm -f pkg/sup-999/lib/sup/modes/completion-mode.rb
ln lib/sup/modes/completion-mode.rb
pkg/sup-999/lib/sup/modes/completion-mode.rb
rm -f pkg/sup-999/lib/sup/modes/log-mode.rb
ln lib/sup/modes/log-mode.rb pkg/sup-999/lib/sup/modes/log-mode.rb
rm -f pkg/sup-999/lib/sup/modes/inbox-mode.rb
ln lib/sup/modes/inbox-mode.rb pkg/sup-999/lib/sup/modes/inbox-mode.rb
rm -f pkg/sup-999/lib/sup/modes/line-cursor-mode.rb
ln lib/sup/modes/line-cursor-mode.rb
pkg/sup-999/lib/sup/modes/line-cursor-mode.rb
rm -f pkg/sup-999/lib/sup/modes/edit-message-mode.rb
ln lib/sup/modes/edit-message-mode.rb
pkg/sup-999/lib/sup/modes/edit-message-mode.rb
cd pkg/sup-999
rake aborted!
undefined method `write' for #<Syck::Emitter:0x00000001b95900>
Tasks: TOP => gem => pkg/sup-999.gem
(See full trace by running task with --trace)
"If you're the type of person who treats email as an extension of your
long-term memory, Sup is for you."
Well, my long-term memory extension is broken for too long, the webmail
clients are getting on my nerves, so I hope sup can be made to work again.
Regards,
Philipp
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [sup-talk] exception --- RuntimeError from thread: poll after loading inbox
2011-11-09 19:52 ` Gaute Hope
2011-11-18 19:34 ` hollunder
@ 2011-11-18 20:55 ` Michael Stapelberg
2011-11-19 0:33 ` [sup-talk] small patch and build error hollunder
2011-11-29 20:39 ` [sup-talk] exception --- RuntimeError from thread: poll after loading inbox Johannes Janosovits
2011-12-17 18:47 ` Hamish D
3 siblings, 1 reply; 21+ messages in thread
From: Michael Stapelberg @ 2011-11-18 20:55 UTC (permalink / raw)
To: sup-talk
Hi Gaute,
Excerpts from Gaute Hope's message of 2011-11-09 19:52:28 +0000:
> This seems to be due to the new yamler 'psych', by requiring the old one
> 'sych' before 'yaml' it can be loaded.
FYI: I’ve pushed your commit to sup-next and sup-master. Thanks.
Best regards,
Michael
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 21+ messages in thread
* [sup-talk] small patch and build error
2011-11-18 20:55 ` Michael Stapelberg
@ 2011-11-19 0:33 ` hollunder
2011-11-21 20:29 ` Gaute Hope
0 siblings, 1 reply; 21+ messages in thread
From: hollunder @ 2011-11-19 0:33 UTC (permalink / raw)
To: sup-talk
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
Hi there again,
I have a small patch as well. This one is against sup-next and fixes a
path issue in the rakefile ("cannot load such file -- sup-files") and a
deprecation warning ("WARNING: rake/gempackagetask is deprecated. Use
rubygems/package_task instead")
However, I don't manage to build sup-next, this time with:
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': iconv will
be deprecated in the future, use String#encode instead.
/usr/lib/ruby/gems/1.9.1/gems/gettext-2.1.0/lib/gettext/runtime/locale_path.rb:20:
Use RbConfig instead of obsolete and deprecated Config.
rake aborted!
invalid date format in specification: "2011-11-19 01:30:45 +0100"
I don't quite know how to fix this one.
Regards,
Philipp
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: rakefile.patch --]
[-- Type: text/x-patch; name="rakefile.patch", Size: 386 bytes --]
--- ../sup-next/Rakefile 2011-11-19 01:15:01.091850944 +0100
+++ Rakefile 2011-11-19 01:25:10.155791337 +0100
@@ -31,9 +31,9 @@
$:.push "lib"
require 'rubygems'
-require "sup-files"
-require "sup-version"
-require 'rake/gempackagetask.rb'
+require "./sup-files"
+require "./sup-version"
+require 'rubygems/package_task.rb'
spec = Gem::Specification.new do |s|
s.name = %q{sup}
[-- Attachment #3: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [sup-talk] exception --- RuntimeError from thread: poll after loading inbox
2011-11-21 20:36 ` Gaute Hope
@ 2011-11-21 20:16 ` Philipp Überbacher
2011-11-21 21:18 ` Michael Stapelberg
0 siblings, 1 reply; 21+ messages in thread
From: Philipp Überbacher @ 2011-11-21 20:16 UTC (permalink / raw)
To: Sup Talk
Excerpts from Gaute Hope's message of 2011-11-21 21:36:42 +0100:
> Excerpts from hollunder's message of 2011-11-18 20:34:20 +0100:
> > Hi Gaute,
> > thanks for fixing stuff.
> > I tried to build from your git repo
> > (git://gitorious.org/sup/gautehs-mainline.git, branch:gauteisrunning).
> > However, it doesn't build, same as sup from the main repo. Do you know
> > what the problem isor how to fix it? Here's the build-ouput:
>
> Hi, I didn't figure this out. Maybe there is a clue in the RVM stuff
> Michael mentioned?
>
> I cheated and just manually installed the new .rb files in my gem
> installation directory.
>
> - Gaute
I rebuilt the old ruby release (1.9.2_p290) and will stick to it for
the time being, sup is the only ruby app I use anyway. I simply don't
know enough about all this ruby build stuff to fix the git build issue.
The last sup release definitely doesn't work with ruby 1.9.3.
My issue with 1.9.2_p290 turned out to be a problem with a message, but
I didn't take the time to find the specific message by deleting them one
by one. I just delete all messages from 2 days, and sup could poll
again. It was not related to the update as I initially suspected and the
update I posted was accidentally an ancient one anyway (2009).
Anyway, thanks for all of your attempts to help. I hope sup will keep up
with the changes in its environment.
Regards,
Philipp
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [sup-talk] small patch and build error
2011-11-19 0:33 ` [sup-talk] small patch and build error hollunder
@ 2011-11-21 20:29 ` Gaute Hope
0 siblings, 0 replies; 21+ messages in thread
From: Gaute Hope @ 2011-11-21 20:29 UTC (permalink / raw)
To: hollunder; +Cc: Sup Talk
Excerpts from hollunder's message of 2011-11-19 01:33:08 +0100:
> Hi there again,
> I have a small patch as well. This one is against sup-next and fixes a
> path issue in the rakefile ("cannot load such file -- sup-files") and a
> deprecation warning ("WARNING: rake/gempackagetask is deprecated. Use
> rubygems/package_task instead")
>
> However, I don't manage to build sup-next, this time with:
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': iconv will
> be deprecated in the future, use String#encode instead.
> /usr/lib/ruby/gems/1.9.1/gems/gettext-2.1.0/lib/gettext/runtime/locale_path.rb:20:
> Use RbConfig instead of obsolete and deprecated Config.
> rake aborted!
> invalid date format in specification: "2011-11-19 01:30:45 +0100"
Check out the previously attached patch 'Use correct date format for gem
spec' or commit b0611fd from 'gauteisrunning'.
- Gaute
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [sup-talk] exception --- RuntimeError from thread: poll after loading inbox
2011-11-18 19:34 ` hollunder
@ 2011-11-21 20:36 ` Gaute Hope
2011-11-21 20:16 ` Philipp Überbacher
0 siblings, 1 reply; 21+ messages in thread
From: Gaute Hope @ 2011-11-21 20:36 UTC (permalink / raw)
To: hollunder; +Cc: Sup Talk
Excerpts from hollunder's message of 2011-11-18 20:34:20 +0100:
> Hi Gaute,
> thanks for fixing stuff.
> I tried to build from your git repo
> (git://gitorious.org/sup/gautehs-mainline.git, branch:gauteisrunning).
> However, it doesn't build, same as sup from the main repo. Do you know
> what the problem isor how to fix it? Here's the build-ouput:
Hi, I didn't figure this out. Maybe there is a clue in the RVM stuff
Michael mentioned?
I cheated and just manually installed the new .rb files in my gem
installation directory.
- Gaute
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [sup-talk] exception --- RuntimeError from thread: poll after loading inbox
2011-11-21 20:16 ` Philipp Überbacher
@ 2011-11-21 21:18 ` Michael Stapelberg
2011-11-21 22:15 ` Philipp Überbacher
0 siblings, 1 reply; 21+ messages in thread
From: Michael Stapelberg @ 2011-11-21 21:18 UTC (permalink / raw)
To: sup-talk
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
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [sup-talk] exception --- RuntimeError from thread: poll after loading inbox
2011-11-21 21:18 ` Michael Stapelberg
@ 2011-11-21 22:15 ` Philipp Überbacher
2011-11-21 22:24 ` Michael Stapelberg
2011-11-21 23:48 ` Gaute Hope
0 siblings, 2 replies; 21+ messages in thread
From: Philipp Überbacher @ 2011-11-21 22:15 UTC (permalink / raw)
To: sup-talk
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
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [sup-talk] exception --- RuntimeError from thread: poll after loading inbox
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
1 sibling, 1 reply; 21+ messages in thread
From: Michael Stapelberg @ 2011-11-21 22:24 UTC (permalink / raw)
To: sup-talk
Hi Philipp,
Excerpts from Philipp Überbacher's message of 2011-11-21 22:15:21 +0000:
> Since you're on 1.9.3 I assume you're an arch user as well? If so, did
I’m not. Read the post. I’m doing this using RVM, which does not touch your
system ruby and does everything in $HOME.
> 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.
That’s not necessary. It does not touch your system.
Best regards,
Michael
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [sup-talk] exception --- RuntimeError from thread: poll after loading inbox
2011-11-21 22:15 ` Philipp Überbacher
2011-11-21 22:24 ` Michael Stapelberg
@ 2011-11-21 23:48 ` Gaute Hope
[not found] ` <1321953145-sup-1447@eris>
1 sibling, 1 reply; 21+ messages in thread
From: Gaute Hope @ 2011-11-21 23:48 UTC (permalink / raw)
To: Sup Talk, Philipp Überbacher
[-- 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
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [sup-talk] exception --- RuntimeError from thread: poll after loading inbox
2011-11-21 22:24 ` Michael Stapelberg
@ 2011-11-22 8:39 ` Philipp Überbacher
0 siblings, 0 replies; 21+ messages in thread
From: Philipp Überbacher @ 2011-11-22 8:39 UTC (permalink / raw)
To: sup-talk
Excerpts from Michael Stapelberg's message of 2011-11-21 23:24:52 +0100:
> Hi Philipp,
>
> Excerpts from Philipp Überbacher's message of 2011-11-21 22:15:21 +0000:
> > Since you're on 1.9.3 I assume you're an arch user as well? If so, did
> I’m not. Read the post. I’m doing this using RVM, which does not touch your
> system ruby and does everything in $HOME.
>
> > 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.
> That’s not necessary. It does not touch your system.
>
> Best regards,
> Michael
Thanks,
I had assumed it builds in a clean environment and installs to the
system. Great if it keeps everything separated.
Regards,
Philipp
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [sup-talk] exception --- RuntimeError from thread: poll after loading inbox
[not found] ` <1321953145-sup-1447@eris>
@ 2011-11-22 15:10 ` Gaute Hope
0 siblings, 0 replies; 21+ messages in thread
From: Gaute Hope @ 2011-11-22 15:10 UTC (permalink / raw)
To: Philipp Überbacher; +Cc: Sup Talk
Excerpts from Philipp Überbacher's message of 2011-11-22 10:18:18 +0100:
> Excerpts from Gaute Hope's message of 2011-11-22 00:48:09 +0100:
> > 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
>
> Doesn't work for me (with ruby 1.9.2 atm):
>
> patching file Rakefile
> Hunk #1 succeeded at 30 with fuzz 2.
> ==> Building the gem
> (in /home/murks/build/other/sup-git/src/gauteisrunning-build)
> rake aborted!
> uninitialized constant Rake::GemPackageTask
> /usr/lib/ruby/1.9.1/rake.rb:2482:in `const_missing'
> /home/murks/build/other/sup-git/src/gauteisrunning-build/Rakefile:61:in `<top (required)>'
> /usr/lib/ruby/1.9.1/rake.rb:2373:in `load'
> /usr/lib/ruby/1.9.1/rake.rb:2373:in `raw_load_rakefile'
> /usr/lib/ruby/1.9.1/rake.rb:2007:in `block in load_rakefile'
> /usr/lib/ruby/1.9.1/rake.rb:2058:in `standard_exception_handling'
> /usr/lib/ruby/1.9.1/rake.rb:2006:in `load_rakefile'
> /usr/lib/ruby/1.9.1/rake.rb:1991:in `run'
> /usr/bin/rake:31:in `<main>'
>
> No big deal for me atm. since I can keep ruby at 1.9.2 and stick to the
> last sup release for the time being. However, if it helps I will attempt
> to build from git with 1.9.3.
Ok. I have not tried it against 1.9.2, but it should not be required for
that anyway (?).
The best is probably to check out/pull fresh from Gitorious.
I consider this a work-around, the best option should be to get
going with 'psych' as yamler for Sup overall, and get rid of the
syck/psych mess (I don't have time to look at that at the moment thou).
- Gaute
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [sup-talk] exception --- RuntimeError from thread: poll after loading inbox
2011-11-09 19:52 ` Gaute Hope
2011-11-18 19:34 ` hollunder
2011-11-18 20:55 ` Michael Stapelberg
@ 2011-11-29 20:39 ` Johannes Janosovits
2011-11-29 22:19 ` Johannes Janosovits
2011-12-17 18:47 ` Hamish D
3 siblings, 1 reply; 21+ messages in thread
From: Johannes Janosovits @ 2011-11-29 20:39 UTC (permalink / raw)
To: sup-talk
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
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [sup-talk] exception --- RuntimeError from thread: poll after loading inbox
2011-11-29 20:39 ` [sup-talk] exception --- RuntimeError from thread: poll after loading inbox Johannes Janosovits
@ 2011-11-29 22:19 ` Johannes Janosovits
0 siblings, 0 replies; 21+ messages in thread
From: Johannes Janosovits @ 2011-11-29 22:19 UTC (permalink / raw)
To: sup-talk
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
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [sup-talk] exception --- RuntimeError from thread: poll after loading inbox
2011-11-09 19:52 ` Gaute Hope
` (2 preceding siblings ...)
2011-11-29 20:39 ` [sup-talk] exception --- RuntimeError from thread: poll after loading inbox Johannes Janosovits
@ 2011-12-17 18:47 ` Hamish D
3 siblings, 0 replies; 21+ messages in thread
From: Hamish D @ 2011-12-17 18:47 UTC (permalink / raw)
To: Gaute Hope; +Cc: Sup Talk
>> 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.
Both patches applied to next.
Hamish
^ permalink raw reply [flat|nested] 21+ messages in thread
end of thread, other threads:[~2011-12-17 18:47 UTC | newest]
Thread overview: 21+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-11-07 9:17 [sup-talk] exception --- RuntimeError from thread: poll after loading inbox 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
2011-12-17 18:47 ` Hamish D
2011-11-08 13:39 ` Mark Alexander
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox