Bug#805172: RFS: vim-command-t/1.13-2 [ITP]

Hmm, something isn't too happy :(

command-t.vim could not load the C extension

Please see INSTALLATION and TROUBLE-SHOOTING in the help

Vim Ruby version: 2.1.5-p273

Expected version: 2.2.3-p173

For more information type: :help command-t

Press ENTER or type command to continue

So.. my pbuilder has ruby 2.2.3

but my vim is linked to libruby2.1.5

$ ldd /usr/bin/vim | grep ruby

libruby-2.1.so.2.1 => /usr/lib/x86_64-linux-gnu/libruby-2.1.so.2.1 (0x00007f891aef3000)

But, I have libruby2.2

So, how do you tell this package to only depend on a vim that is linked to ruby2.2

or how do you tell command-t to link to the vim it knows about.

On Tue, Nov 24, 2015 at 10:51 PM Sam Morris <sam@robots.org.uk> wrote:

On Tue, 2015-11-24 at 11:35 +0000, Craig Small wrote:
>
> On Mon, Nov 16, 2015 at 1:21 AM Sam Morris <sam@robots.org.uk> wrote:
> > I am looking for a sponsor for my package "vim-command-t"
> I tried building it but it looks like you are missing a dependency.
>
>
> make[1]: Entering directory '/build/vim-command-t-1.13'
> cd ruby/command-t && ruby extconf.rb
> mkmf.rb can't find header files for ruby at
> /usr/lib/ruby/include/ruby.h
> debian/rules:7: recipe for target 'override_dh_auto_configure' failed
> make[1]: *** [override_dh_auto_configure] Error 1
> make[1]: Leaving directory '/build/vim-command-t-1.13'
> debian/rules:4: recipe for target 'build' failed
> make: *** [build] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
>
> - Craig

Thanks for letting me know--seems I had ruby2.2-dev still installed on
my machine so didn't notice the missing dependency. I've uploaded 1.13-
3 with the additional build-dependency added.

--
Sam Morris <https://robots.org.uk/>
CAAA AA1A CA69 A83A 892B 1855 D20B 4202 5CDA 27B9