similar to: Deprecation

Questions are threaded into the output: ******************** #./configure --without-python checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking

I've noticed some strange results from the stemmer in the Ruby port: irb(main):003:0> @stem.stem_word("anybody") => "anybodi" irb(main):004:0> @stem.stem_word("swimmingly") => "swim" irb(main):005:0> @stem.stem_word("fiercely") => "fierc" irb(main):006:0> @stem.stem_word("fraudulently") =>

I've just noticed that the csharp bindings fail to pass make check on my machine: Smoketest.exe hangs indefinitely. I get: make check-recursive Making check in docs make[2]: Nothing to be done for `check'. make check-TESTS *** glibc detected *** /usr/bin/cli: free(): invalid pointer: 0x0002be14 *** ... and then the test pauses indefinitely. Attaching to the test with gdb shows

hi, i am newbie to xapian and am trying to get started with it in python. there is no stemmer.stem_word method in the latest python library. how do i stem words before doing doc.add_posting? is there any sample hello world code in python that i can use? thanks a lot! >>> stemmer = xapian.Stem('english') >>> stemmer. stemmer.__call__

Dear Xapian developers, I am happy to announce that the Xapian-Ruby bindings now pass all tests defined in smoketest.rb. (These tests are mostly drawn from smoketest.py; a few tests that are not applicable to the Ruby version have been removed.) I have also added Olly's patch to integrate the Ruby bindings into the automake/configure scripts. The latest version is available by anonymous

Hello, I am attempting to run the smoketest.php file from my devserver and am getting nothing but errors. It looks like it did not install correctly. Yesterday I compiled the source on os x and it appeared to install just fine, but now it is not working at all. I tried to replace the location of the xapian.php file with a hardcoded located and got a different set of errors. Here are

Hi all, I'm getting an error in the smoketest. I'm using latest Swig and Python bindings from SVN-HEAD: File "smoketest.py", line 23, in <module> import xapian File "C:\work\xapian\xapian-SVN\xapian-core\win32\Release\Python\xapian.py", line 2099, in <module> ValueRangeProcessor.__call__ = ValueRangeProcessor.__call AttributeError: type

Olly and I have been discussing details of our policy for deprecating features, and we thought it would be useful to canvas users opinions on a particular aspect. From time to time, we remove features from the library (usually because we have a better replacement). To make life easier for users, we've been following a deprecation policy, so that users are given plenty of warning of

On Wed, Apr 11, 2007 at 10:31:39AM +0100, richard wrote: > python/smoketest.py: Replace cut-and-pasted test checking code > with functions, to simplify tests. It might be simpler, but mostly because functionality has gone - you've thrown away all my carefully written failure messages! Now if a test fails, the message is very generic and you have to read the code to find out what's

I'm posting this here to help others who might be having the same issue. I maintain xapian-core ruby gem. I was trying to upgrade to 1.4.2 and had some issues. The generated makefile doesn’t work because of the following: docs/rdocs/index.html: docs/xapian.rb rm -rf docs/rdocs $(MKDIR_P) docs cd docs && $(RDOC) --op rdocs `test -f xapian.rb||echo '$(abs_srcdir)/'`xapian.rb

Currently, the SWIG generated bindings catch exceptions raised by Xapian and rethrow them using the standard SWIG error types: for example, if any Xapian::DatabaseError exception is raised, SWIG will use its standard SWIG_IOError error type to report the error. In Python, this leads to code like the following: try: db.get_document(1) except RuntimeError, e: if

Currently, the SWIG generated bindings catch exceptions raised by Xapian and rethrow them using the standard SWIG error types: for example, if any Xapian::DatabaseError exception is raised, SWIG will use its standard SWIG_IOError error type to report the error. In Python, this leads to code like the following: try: db.get_document(1) except RuntimeError, e: if

Hi all, There's been a odd bug reported to us by Daniel Menard while working on the PHP bindings: "I then tried to run the dotest target...All tests passed, except the one about get_matching_terms (smoketest.php line 94). I added this line before the exit: for ($i=0; $i<strlen($terms); $i++) echo $c=ord($terms[$i]), ' ', ($c>31?$terms[$i]:''), "\n";

I've now uploaded Xapian 1.0.1, which you can download from the usual place: http://www.xapian.org/download.php This release mainly comprises bug fixes and performance improvements. The "simple" examples (for both C++ and the bindings) have also been overhauled and now use the QueryParser and TermGenerator classes, which makes for simpler examples and should better reflect

I've now uploaded Xapian 1.0.1, which you can download from the usual place: http://www.xapian.org/download.php This release mainly comprises bug fixes and performance improvements. The "simple" examples (for both C++ and the bindings) have also been overhauled and now use the QueryParser and TermGenerator classes, which makes for simpler examples and should better reflect

On 08/24/2016 07:53 PM, Peter wrote: > On 25/08/16 13:21, Kay Schenk wrote: >> To all...yes I meant glibc, not glib. Target environment -- could be any >> version of Linux. This is for Apache OpenOffice. The buildbots we've been >> using are being decommisioned due to EOL. As a developer on that project, I >> need to be able to test and use the builds. We'll be

I installed xapian core on Centos system. On execution, I get this error message: "warning: dl() [function.dl]: xapian: Unable to initialize module Module compiled with module API=20050922, debug=0, thread-safety=0 PHP compiled with module API=20060613, debug=0, thread-safety=0 These options need to match in /usr/share/php/xapian.php on line 22." PHP 5.2.16 (cli) (built: Dec 17 2010

I thought that I installed all the bindings but seems to me that I am missing xapian.so when I try to run smoketest.php Warning: dl(): Unable to load dynamic library '/usr/lib/php/extensions/xapian.so' - /usr/lib/php/extensions/xapian.so: cannot open shared object file: No such file or directory Can somebody send me the link to the module that I need to install? Thanks, Kevin

On 08/25/2016 10:44 AM, Gordon Messmer wrote: > On 08/25/2016 09:49 AM, Kay Schenk wrote: >> I do realize the sane thing to do is to have the builbots -- >> smoketest environments -- match the production environment > > > I think the sane thing to do would be to use buildbots that support LSB: > > http://www.ludism.org/~rwhe/LSB/tutorial/tut.html Great resource!

When going through the xapian bindings yesterday, I noticed that several of the methods were not wrapped for Ruby because they were deprecated at the time the ruby bindings were created. I filed a bug (#126) saying that they should be removed entirely, which led to the suggestion from Olly that it would be good to make a semi-formal policy about deprecating features. I've written such a