Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#529188: sup-mail: ncurses-ruby1.8 upgrade breaks search

0 views
Skip to first unread message

Jack Hill

unread,
May 17, 2009, 6:30:13 PM5/17/09
to
Package: sup-mail
Version: 0.7-1
Severity: normal

When libncurses-ruby1.8 was upgraded from version 1.1-3 to 1.2.2-1 search (via \ from within sup) breaks. Instead of
providing a search prompt sup crashes with the error ruby: symbol lookup error: /usr/lib/ruby/1.8/x86_64-linux/ncurses_bin.so: undefined symbol: funcall

Manualy downgrading libncurses-ruby1.8 to version 1.1-3 fixes the problem.

-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages sup-mail depends on:
ii libchronic-ruby 0.2.3-1 natural language date parser
ii libferret-ruby1.8 0.11.6-2 full text search engine library fo
ii libgettext-ruby1.8 1.93.0-1 Gettext for ruby1.8
ii libhighline-ruby 1.4.0-1 High-level interactive IO Ruby lib
ii liblockfile-ruby 1.4.3-2 create NFS-safe lockfiles
ii libmime-types-ruby 1.15-2 guess MIME type of files
ii libncurses-ruby 1.2.2-1 ruby Extension for the ncurses C l
ii libnet-ssh-ruby1.8 1.1.2-1 pure ruby module that emulates an
ii librmail-ruby1.8 0.17-1 lightweight mail library for Ruby
ii libtrollop-ruby 1.9-1 command-line argument processing l
ii ruby 4.2 An interpreter of object-oriented

sup-mail recommends no packages.

sup-mail suggests no packages.

-- no debconf information

--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Decklin Foster

unread,
Jul 4, 2009, 10:30:16 AM7/4/09
to
severity 529188 important
reassign 529188 libncurses-ruby1.8
merge 532431 529188
thanks

Excerpts from Jack Hill's message of Sun May 17 18:06:15 -0400 2009:


> When libncurses-ruby1.8 was upgraded from version 1.1-3 to 1.2.2-1 search (via
> \ from within sup) breaks. Instead of
> providing a search prompt sup crashes with the error ruby: symbol lookup error:
> /usr/lib/ruby/1.8/x86_64-linux/ncurses_bin.so: undefined symbol: funcall
>
> Manualy downgrading libncurses-ruby1.8 to version 1.1-3 fixes the problem.

This appears to be an issue in ncurses-ruby; until it is updated, I've placed
updated packages at http://apt.rupamsunyata.org/sup/ (0.1 is just the new,
fixed upstream version; 0.2 also uses ncursesw).
--
things change.
dec...@red-bean.com

Michael Ablassmeier

unread,
Jul 4, 2009, 11:50:15 AM7/4/09
to
hi,

On Sat, Jul 04, 2009 at 02:18:09PM +0000, Debian Bug Tracking System wrote:
> > severity 529188 important
> Bug#529188: sup-mail: ncurses-ruby1.8 upgrade breaks search
> Severity set to `important' from `normal'
>
> > reassign 529188 libncurses-ruby1.8
> Bug#529188: sup-mail: ncurses-ruby1.8 upgrade breaks search
> Bug reassigned from package `sup-mail' to `libncurses-ruby1.8'.
>
> > merge 532431 529188
> Bug#529188: sup-mail: ncurses-ruby1.8 upgrade breaks search
> Bug#532431: ruby: symbol lookup error: /usr/lib/ruby/1.8/x86_64-linux/ncurses_bin.so: undefined symbol: funcall
> Merged 529188 532431.

this has been fixed as with 1.2.3:

+ * $Id: ncurses_wrap.c,v 1.17 2009/06/25 21:53:57 t-peters Exp $
*
* This file was adapted from the original ncurses header file which
* has the following copyright statements:
@@ -210,7 +210,7 @@
/// Portable (1.8,1.9) determination of array length (calling #length)
long rbncurs_array_length(VALUE array)
{
- return NUM2LONG(funcall(array, rb_intern("length"), 0));
+ return NUM2LONG(rb_funcall(array, rb_intern("length"), 0));
}


but 1.2.3 also seems to include some debugging code which was (i think
accidentaly left in the code:

+ FILE * f = fopen("/tmp/xlog","a");
+ fprintf(f, "Callig select\n");
+ fclose(f);

ill talk to upstream and upload a new version as soon as he releases it without
this code (i dont want to mess around with dpatch just for those 3 lines).

bye,
- michael

0 new messages