Package Details: sup 0.22.1-1

Git Clone URL: https://aur.archlinux.org/sup.git (read-only)
Package Base: sup
Description: Sup is a console-based email client for people with a lot of email. Great mutt alternative.
Upstream URL: http://sup-heliotrope.github.io/
Licenses: GPL
Conflicts: sup-git
Submitter: Garoth
Maintainer: asch
Last Packager: asch
Votes: 52
Popularity: 0.000002
First Submitted: 2009-05-12 15:12
Last Updated: 2018-09-03 15:51

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 Next › Last »

Garoth commented on 2011-02-12 19:24

ruby-xapian-full*

Garoth commented on 2011-02-12 19:21

Iirc, it was something fishy like Rich Lane from the sup project needing some fixes in the ruby ncurses, so he made this package. I'm not entirely sure, it's a bit hazy. Anyway, you should be just able to change your PKGBUILD to use ruby-ncurses-full and it should work.

Anonymous comment on 2011-02-12 10:12

I believe that is because if you already have xapian-core on your system, then xapian-ruby-bindings is much smaller and it used to work just fine with sup. There may be a way to make it work with the current version of sup, but I don't know how. If anyone knows more about xapian-ruby-bindings please let me know.

hcs commented on 2011-02-12 08:38

A bit clearer but, why do this package list xapian-ruby-bindings as a dependency if it needs ruby-xapian-full?

I needed to update ld.so.conf to get ruby-xapian-full to work.

<internal:lib/rubygems/custom_require>:29:in `require': libxapian.so.22: cannot open shared object file: No such file or directory - /usr/lib/ruby/gems/1.9.1/gems/xapian-full-1.2.3/lib/_xapian.so (LoadError)

Anonymous comment on 2011-02-12 01:26

The xapian-ruby-bindings is not the official package that sup uses, ruby-xapain-full is, which is a gem. AFAIK, no gem exists for xapian-ruby-bindings and so I can't package it as a gem. I don't really know much about the xapian-ruby-bindings package. The sources just exist in a file directory on the web and I grab them from there as the previous maintainer did. xapian-ruby-bindings depends on xapian-core while ruby-xapian-full does not. If you use ruby-xapian-full(the updated version I just posted), and the just updated version ruby-ncursesw, you can update to the most recent version of ruby and everything should work. I hope I have clarified things a little.

hcs commented on 2011-02-11 22:23

I'm afraid that xapian-ruby-bindings don't seem to be a gem install either.

...Could not find RubyGem xapian-full (>= 1.1.3.1)...

Garoth commented on 2011-02-11 19:49

actually, it's up now. Tell me if it doesn't work, I might have done something to my system and then forgot

Garoth commented on 2011-02-11 19:43

It's very possible to get it working, I was poking the maintainer of ruby-gettext (in community, so it's a little more official) to switch his package to being a gem install. It looks like he's finally done this (though didn't e-mail me about it), so the sup package should be do-able now.

I'm kind of sick/tired at the moment, but I'll hopefully find the energy to throw up the new version soon

Anonymous comment on 2011-02-11 09:14

Are we there yet? Sorry, just can't wait to try it out! Thanks for your work on this!

Garoth commented on 2011-01-27 19:01

Great news everyone. The recent updates to sup and ncursesw as well as discussion with the sup devs has fixed the remaining problems that exist in sup. However, for the moment, the ruby-gettext package in community is somewhat buggy in that it doesn't install as a gem and sup can't find it! I'm asking the maintainer there to change it to a gem style package, but if he doesn't go for that, I'll either make a new package for gettext on aur or find a way to make sup add this non-gem path to its search path for libraries.

Hang tight, I have a running version of sup on Arch with Ruby 1.9. It's coming to you soon!