pickle depends on gherkin 2.1.4

[ozpos]

Hi ian,
I an trying to install locomotive under debian which depends on pickle. gherkin-2.1.4 will not build local extensions however gherkin-2.4.0 build is ok.

Is it possible to unpin pickle so it can use gherkin-2.4.0 or is there some other solution ?

[ianwhite]

Hi there,

pickle depends on gherkin via cucumber, but pickle only requires cucumber >= 0.8. Therefore, I think that locomotive probably has locked its deps to that particular version.

I assume locomotive has a Gemfile, if so, try running 'bundle update gherkin"

[ozpos]

Hi thank you for the reply, I did just that:-

bundle install
Fetching source index for http://rubygems.org/
You have requested:
gherkin >= 2.4.0

The bundle currently has gherkin locked at 2.1.5.
Try running bundle update gherkin

bundle update gherkin
...
Installing gherkin (2.1.5) with native extensions /usr/local/rvm/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/installer.rb:533:in `rescue in block in build_extensions': ERROR: Failed to build gem native extension. (Gem::Installer::ExtensionBuildError)
...
However gherkin-2.4.0 builds OK?

[ozpos]

Hi, thank you for the reply.
Sorry my problem is with 2.1.5, not 2.1.4 as originally stated.

I changed locomotives gemfile to request gherkin-2.4.0 because the
native extensions for 2.4.0 build ok:-

bundle install
Fetching source index for http://rubygems.org/
You have requested:
gherkin >= 2.4.0

The bundle currently has gherkin locked at 2.1.5.
Try running |bundle update gherkin|

bundle update gherkin:-
...
Installing gherkin (2.1.5) with native extensions
/usr/local/rvm/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/installer.rb:533:in
`rescue in block in build_extensions': ERROR: Failed to build gem native
extension. (Gem::Installer::ExtensionBuildError)
...

gem_make.out:-

---

/usr/local/rvm/rubies/ruby-1.9.2-p180/bin/ruby extconf.rb
checking for main() in -lc... yes
creating Makefile

make
gcc -I.
-I/usr/local/rvm/rubies/ruby-1.9.2-p180/include/ruby-1.9.1/i686-linux
-I/usr/local/rvm/rubies/ruby-1.9.2-p180/include/ruby-1.9.1/ruby/backward
-I/usr/local/rvm/rubies/ruby-1.9.2-p180/include/ruby-1.9.1 -I.
-D_FILE_OFFSET_BITS=64 -fPIC -O3 -ggdb -Wextra -Wno-unused-parameter
-Wno-parentheses -Wpointer-arith -Wwrite-strings
-Wno-missing-field-initializers -Wno-long-long -fPIC -O0 -Wall -Werror
-o gherkin_lexer_ar.o -c gherkin_lexer_ar.c
/Users/aslakhellesoy/scm/gherkin/tasks/../ragel/i18n/ar.c.rl: In
function ‘CLexer_scan’:
/Users/aslakhellesoy/scm/gherkin/tasks/../ragel/i18n/ar.c.rl:198:29:
error: the comparison will always evaluate as ‘true’ for the address of
‘raise_lexer_error’ will never be NULL [-Werror=address]
/Users/aslakhellesoy/scm/gherkin/tasks/../ragel/i18n/ar.c.rl:198:29:
error: the comparison will always evaluate as ‘true’ for the address of
‘raise_lexer_error’ will never be NULL [-Werror=address]
cc1: all warnings being treated as errors

make: *** [gherkin_lexer_ar.o] Error 1

I am new to bundler so after some research I renamed the Gemfile.lock
file and ran bundle install and all seems ok. The new Gemfile.lock uses
gherkin-2.4.0.

Many thanks for your response and thanks for pickle.

On 15/06/11 19:23, ianwhite wrote:

Hi there,

pickle depends on gherkin via cucumber, but pickle only requires cucumber>= 0.8. Therefore, I think that locomotive probably has locked its deps to that particular version.

I assume locomotive has a Gemfile, if so, try running 'bundle update gherkin"

[niklas]

hey @ozpos, do you still have issues with gherkin regarding pickle?

[ozpos]

Hi sorry for the delay. I have not touched it for many months. I will
file your email in the relevant place so as to let you know how I get on
the next time I come to use the gem.
ozpoz

On 06/08/14 23:52, Niklas H wrote:

hey @ozpos https://github.com/ozpos, do you still have issues with
gherkin regarding pickle?

—
Reply to this email directly or view it on GitHub
#19 (comment).

[jondkinney]

Probably safe to close this issue and let it be re-opened if the problem resurfaces.

[chewi]

Yeah, I don't believe this is our issue anyway.