Vasudev Kamath escreveu isso aí:
Antonio thanks for fixing the issue.
Actually this is a packaging problem: the tests for Ruby 1.8 are being
run against the compiled extension for Ruby 1.9.
$: 'lib' 'ext/mri' '.'
If I remember correctly this line was added because when I was trying
Antonio thanks for fixing the issue.
Actually this is a packaging problem: the tests for Ruby 1.8 are being
run against the compiled extension for Ruby 1.9.
$: 'lib' 'ext/mri' '.'
If I remember correctly this line was added because when I was trying
to build the package with tests enabled
tags 633302 + pending
thanks
Hello,
Cédric Boutillier escreveu isso aí:
Hi,
I investigated this a little bit. The problem occurs during this call:
lambda { BCrypt::Password.create(nil) }.should_not
raise_error(BCrypt::Errors::InvalidSecret)
in the password_spec.rb test file.
It
Hi,
Currently I don't have access to any Debian machine (atleast for a
month or so), also I'm a ruby novice and I may need help here.
I request help from the Debian Ruby Extras team (CCed).
Thanking you,
On Sat, Jul 9, 2011 at 4:49 PM, Aurelien Jarno aure...@debian.org wrote:
Package:
Hi,
I investigated this a little bit. The problem occurs during this call:
lambda { BCrypt::Password.create(nil) }.should_not
raise_error(BCrypt::Errors::InvalidSecret)
in the password_spec.rb test file.
It seems that the value (10) of the BCrypt::Engine::DEFAULT_COST constant
is to high
5 matches
Mail list logo
