saimon
January 22, 2007, 11:18am
1
Hi Dave,
I’ve been getting some segment faults while running my tests using
0.10.14 gem so I decided to package the gem locally to add -dH and
generate core dumps for you.
So I followed instructions here
http://ferret.davebalmain.com/trac/wiki/DownloadCurrent and first off
ran the tests.
I’m getting the following failures. (see this pastie
Parked at Loopia ).
I don’t suppose these are expected but I thought I may as well let you
know.
Regards,
Saimon
saimon
January 22, 2007, 12:01pm
3
What’s also strange when using the locally packaged gem is the
following:
saimon@iris ~/tmp $ irb
require ‘rubygems’
=> false
require_gem ‘ferret’,‘>= 0.10.14.1’ #I packaged it as
=> true
require ‘ferret’
=> false
Ferret
=> Ferret
Ferret::Index
=> Ferret::Index
Ferret::Index::FieldInfos
NameError: uninitialized constant Ferret::Index::FieldInfos
from (irb):7
For some reason it can’t find Ferret::Index::FieldInfos. ???
Maybe it’s the way I packaged it but I simply did:
I just used gem package REL=0.10.14.1
sudo gem install pkg/ferret-0.10.14.1.gem
Regards,
Saimon
Saimon M. wrote:
Saimon M. wrote:
Hi Dave,
I’ve been getting some segment faults while running my tests using
0.10.14 gem so I decided to package the gem locally to add -dH and
generate core dumps for you.
So I followed instructions here
http://ferret.davebalmain.com/trac/wiki/DownloadCurrent and first off
ran the tests.
I’m getting the following failures. (see this pastie
Parked at Loopia ).
I don’t suppose these are expected but I thought I may as well let you
know.
Regards,
Saimon
Also:
saimon@iris ~/tmp $ irb
require ‘rubygems’
=> false
require_gem ‘ferret’, ‘>=0.10.14’
=> true
puts Ferret::VERSION
0.9.6
=> nil
saimon
January 22, 2007, 6:26pm
4
William M. wrote:
Excerpts from Saimon M.'s message of Mon Jan 22 03:01:05 -0800 2007:
NameError: uninitialized constant Ferret::Index::FieldInfos
from (irb):7
For some reason it can’t find Ferret::Index::FieldInfos. ???
This, and the Ferret::VERSION thing, are both symptomatic of you having
packaged 0.9.6 rather than 0.10.14.
The SVN directions on the Ferret page are wrong. You actually need to
do
svn co svn://www.davebalmain.com/exp ferret
to get the latest version
Hi William,
Actually what I downloaded was :
svn co svn://davebalmain.com/ferret/tags/REL-0.10.14 ferret_0.10.4
and Ferret::VERSION was 0.9.6 in that version.
Is this still not correct?
saimon
January 22, 2007, 5:55pm
5
Excerpts from Saimon M.'s message of Mon Jan 22 03:01:05 -0800 2007:
NameError: uninitialized constant Ferret::Index::FieldInfos
from (irb):7
For some reason it can’t find Ferret::Index::FieldInfos. ???
This, and the Ferret::VERSION thing, are both symptomatic of you having
packaged 0.9.6 rather than 0.10.14.
The SVN directions on the Ferret page are wrong. You actually need to
do
svn co svn://www.davebalmain.com/exp ferret
to get the latest version
saimon
January 23, 2007, 10:38am
6
On Mon, Jan 22, 2007 at 06:26:43PM +0100, Saimon M. wrote:
The SVN directions on the Ferret page are wrong. You actually need to
svn co svn://davebalmain.com/ferret/tags/REL-0.10.14 ferret_0.10.4
and Ferret::VERSION was 0.9.6 in that version.
Is this still not correct?
it should state the correct versipn, at least my 0.10.14 installed via
rubygems does:
irb(main):001:0> require ‘rubygems’
=> true
irb(main):002:0> require ‘ferret’
=> true
irb(main):003:0> Ferret::VERSION
=> “0.10.14”
irb(main):004:0>
Jens
–
webit! Gesellschaft für neue Medien mbH www.webit.de
Dipl.-Wirtschaftsingenieur Jens Krämer [email protected]
Schnorrstraße 76 Tel +49 351 46766 0
D-01069 Dresden Fax +49 351 46766 66
saimon
January 22, 2007, 7:45pm
7
Excerpts from Saimon M.'s message of Mon Jan 22 09:26:43 -0800 2007:
svn co svn://davebalmain.com/ferret/tags/REL-0.10.14 ferret_0.10.4
and Ferret::VERSION was 0.9.6 in that version.
Is this still not correct?
Hm. I’m not sure at this point. There’s an svn log message there saying
that Dave tagged release 0.10.14, but the code sure looks like 0.9.6.
The code in the svn repository I pointed to looks much more recent.
I could be completely confused though.