Package: sup-mail
Version: 0.9-1
Severity: normal
The new sup provides a new experimental Xapian backend to replace
Ferret, as detailed in the release announcement[0].
Unfortunately, the sup-mail package doesn't depend in any way on
libxapian-ruby1.8, so you end up with a backtrace if you try to use it:
% SUP_INDEX=xapian sup-sync --changed maildir:/home/micah/Maildir/INBOX
/usr/lib/ruby/1.8/sup/xapian_index.rb:1:in `require': no such file to load --
xapian (LoadError)
from
/usr/lib/ruby/1.8/sup/xapian_index.rb:1
from
/usr/lib/ruby/1.8/sup/index.rb:179:in `require'
from
/usr/lib/ruby/1.8/sup/index.rb:179
from /usr/lib/ruby/1.8/sup.rb:279:in
`require'
from /usr/lib/ruby/1.8/sup.rb:279
from /usr/bin/sup-sync:5:in `require'
from /usr/bin/sup-sync:5
I'm not sure if libxapian-ruby1.8 should be a Depends, Recommends or
Suggests, but it should be one of those!
micah
0. http://rubyforge.org/pipermail/sup-announce/2009/000002.html
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-vserver-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
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.5.1-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.4-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.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 [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
