You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pylucene-dev@lucene.apache.org by Andi Vajda <va...@apache.org> on 2009/12/03 18:55:52 UTC
[VOTE] Release PyLucene 3.0.0-1 (rc2) (nag)
This vote is still open. We need one more +1 PMC vote before PyLucene 3.0.0
can be released.
Thanks !
Andi..
---------- Forwarded message ----------
Date: Sun, 29 Nov 2009 16:02:50 -0800 (PST)
From: Andi Vajda <va...@apache.org>
Reply-To: pylucene-dev@lucene.apache.org, Andi Vajda <va...@apache.org>
To: pylucene-dev@lucene.apache.org, general@lucene.apache.org
Subject: [VOTE] Release PyLucene 3.0.0-1 (rc2)
New artifacts for this release were made to include a fix for building on
Windows with MSVC.
-----------
With the recent release of Java Lucene 3.0.0, a PyLucene 3.0.0-1 release
closely tracking it is ready.
ATTENTION: Lucene Java 3.0.0 has seen many changes to its API. While Java
users can methodically port their code from Lucene 2.9.1 to
Lucene 3.0.0 by watching for and eliminating deprecation warnings
while compiling their code against the Lucene 2.9.1 release, no
such luxury is afforded to Python users. APIs that were
deprecated in Lucene 2.x have been removed from Lucene 3.0.0 and
will trigger Python runtime errors in applications coded with
PyLucene 2.x. Please, refer to Lucene's 3.0.0 changelist [2], in
particular to its API changes section [3], for all the details.
Release candidate 2 of PyLucene 3.0.0-1 is available from:
http://people.apache.org/~vajda/staging_area/
A list of changes in this release can be seen at:
http://svn.apache.org/repos/asf/lucene/pylucene/trunk/CHANGES
http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES
Please vote to release these artifacts as PyLucene 3.0.0-1.
Thanks !
Andi..
ps: the KEYS file for PyLucene release signing is at:
http://svn.apache.org/repos/asf/lucene/pylucene/dist/KEYS
http://people.apache.org/~vajda/staging_area/KEYS
[1] http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x88E27CA20ED7633F
[2] http://lucene.apache.org/java/3_0_0/changes/Changes.html
[3] http://lucene.apache.org/java/3_0_0/changes/Changes.html#3.0.0.api_changes
Re: [VOTE] Release PyLucene 3.0.0-1 (rc2) (nag)
Posted by Andi Vajda <va...@apache.org>.
On Tue, 8 Dec 2009, Grant Ingersoll wrote:
> +1
Thanks Grant.
This vote has now passed with 6 +1 and no -1.
The release is under way.
Andi..
>
> On Dec 3, 2009, at 12:55 PM, Andi Vajda wrote:
>
>>
>> This vote is still open. We need one more +1 PMC vote before PyLucene 3.0.0 can be released.
>>
>> Thanks !
>>
>> Andi..
>>
>> ---------- Forwarded message ----------
>> Date: Sun, 29 Nov 2009 16:02:50 -0800 (PST)
>> From: Andi Vajda <va...@apache.org>
>> Reply-To: pylucene-dev@lucene.apache.org, Andi Vajda <va...@apache.org>
>> To: pylucene-dev@lucene.apache.org, general@lucene.apache.org
>> Subject: [VOTE] Release PyLucene 3.0.0-1 (rc2)
>>
>>
>> New artifacts for this release were made to include a fix for building on Windows with MSVC.
>>
>> -----------
>>
>> With the recent release of Java Lucene 3.0.0, a PyLucene 3.0.0-1 release closely tracking it is ready.
>>
>> ATTENTION: Lucene Java 3.0.0 has seen many changes to its API. While Java
>> users can methodically port their code from Lucene 2.9.1 to
>> Lucene 3.0.0 by watching for and eliminating deprecation warnings
>> while compiling their code against the Lucene 2.9.1 release, no
>> such luxury is afforded to Python users. APIs that were
>> deprecated in Lucene 2.x have been removed from Lucene 3.0.0 and
>> will trigger Python runtime errors in applications coded with
>> PyLucene 2.x. Please, refer to Lucene's 3.0.0 changelist [2], in
>> particular to its API changes section [3], for all the details.
>>
>> Release candidate 2 of PyLucene 3.0.0-1 is available from:
>>
>> http://people.apache.org/~vajda/staging_area/
>>
>> A list of changes in this release can be seen at:
>> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/CHANGES
>> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES
>>
>> Please vote to release these artifacts as PyLucene 3.0.0-1.
>>
>> Thanks !
>>
>> Andi..
>>
>> ps: the KEYS file for PyLucene release signing is at:
>> http://svn.apache.org/repos/asf/lucene/pylucene/dist/KEYS
>> http://people.apache.org/~vajda/staging_area/KEYS
>>
>> [1] http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x88E27CA20ED7633F
>> [2] http://lucene.apache.org/java/3_0_0/changes/Changes.html
>> [3] http://lucene.apache.org/java/3_0_0/changes/Changes.html#3.0.0.api_changes
>
> --------------------------
> Grant Ingersoll
> http://www.lucidimagination.com/
>
> Search the Lucene ecosystem (Lucene/Solr/Nutch/Mahout/Tika/Droids) using Solr/Lucene:
> http://www.lucidimagination.com/search
>
Re: [VOTE] Release PyLucene 3.0.0-1 (rc2) (nag)
Posted by Andi Vajda <va...@apache.org>.
On Tue, 8 Dec 2009, Grant Ingersoll wrote:
> +1
Thanks Grant.
This vote has now passed with 6 +1 and no -1.
The release is under way.
Andi..
>
> On Dec 3, 2009, at 12:55 PM, Andi Vajda wrote:
>
>>
>> This vote is still open. We need one more +1 PMC vote before PyLucene 3.0.0 can be released.
>>
>> Thanks !
>>
>> Andi..
>>
>> ---------- Forwarded message ----------
>> Date: Sun, 29 Nov 2009 16:02:50 -0800 (PST)
>> From: Andi Vajda <va...@apache.org>
>> Reply-To: pylucene-dev@lucene.apache.org, Andi Vajda <va...@apache.org>
>> To: pylucene-dev@lucene.apache.org, general@lucene.apache.org
>> Subject: [VOTE] Release PyLucene 3.0.0-1 (rc2)
>>
>>
>> New artifacts for this release were made to include a fix for building on Windows with MSVC.
>>
>> -----------
>>
>> With the recent release of Java Lucene 3.0.0, a PyLucene 3.0.0-1 release closely tracking it is ready.
>>
>> ATTENTION: Lucene Java 3.0.0 has seen many changes to its API. While Java
>> users can methodically port their code from Lucene 2.9.1 to
>> Lucene 3.0.0 by watching for and eliminating deprecation warnings
>> while compiling their code against the Lucene 2.9.1 release, no
>> such luxury is afforded to Python users. APIs that were
>> deprecated in Lucene 2.x have been removed from Lucene 3.0.0 and
>> will trigger Python runtime errors in applications coded with
>> PyLucene 2.x. Please, refer to Lucene's 3.0.0 changelist [2], in
>> particular to its API changes section [3], for all the details.
>>
>> Release candidate 2 of PyLucene 3.0.0-1 is available from:
>>
>> http://people.apache.org/~vajda/staging_area/
>>
>> A list of changes in this release can be seen at:
>> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/CHANGES
>> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES
>>
>> Please vote to release these artifacts as PyLucene 3.0.0-1.
>>
>> Thanks !
>>
>> Andi..
>>
>> ps: the KEYS file for PyLucene release signing is at:
>> http://svn.apache.org/repos/asf/lucene/pylucene/dist/KEYS
>> http://people.apache.org/~vajda/staging_area/KEYS
>>
>> [1] http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x88E27CA20ED7633F
>> [2] http://lucene.apache.org/java/3_0_0/changes/Changes.html
>> [3] http://lucene.apache.org/java/3_0_0/changes/Changes.html#3.0.0.api_changes
>
> --------------------------
> Grant Ingersoll
> http://www.lucidimagination.com/
>
> Search the Lucene ecosystem (Lucene/Solr/Nutch/Mahout/Tika/Droids) using Solr/Lucene:
> http://www.lucidimagination.com/search
>
Re: [VOTE] Release PyLucene 3.0.0-1 (rc2) (nag)
Posted by Grant Ingersoll <gs...@apache.org>.
+1
On Dec 3, 2009, at 12:55 PM, Andi Vajda wrote:
>
> This vote is still open. We need one more +1 PMC vote before PyLucene 3.0.0 can be released.
>
> Thanks !
>
> Andi..
>
> ---------- Forwarded message ----------
> Date: Sun, 29 Nov 2009 16:02:50 -0800 (PST)
> From: Andi Vajda <va...@apache.org>
> Reply-To: pylucene-dev@lucene.apache.org, Andi Vajda <va...@apache.org>
> To: pylucene-dev@lucene.apache.org, general@lucene.apache.org
> Subject: [VOTE] Release PyLucene 3.0.0-1 (rc2)
>
>
> New artifacts for this release were made to include a fix for building on Windows with MSVC.
>
> -----------
>
> With the recent release of Java Lucene 3.0.0, a PyLucene 3.0.0-1 release closely tracking it is ready.
>
> ATTENTION: Lucene Java 3.0.0 has seen many changes to its API. While Java
> users can methodically port their code from Lucene 2.9.1 to
> Lucene 3.0.0 by watching for and eliminating deprecation warnings
> while compiling their code against the Lucene 2.9.1 release, no
> such luxury is afforded to Python users. APIs that were
> deprecated in Lucene 2.x have been removed from Lucene 3.0.0 and
> will trigger Python runtime errors in applications coded with
> PyLucene 2.x. Please, refer to Lucene's 3.0.0 changelist [2], in
> particular to its API changes section [3], for all the details.
>
> Release candidate 2 of PyLucene 3.0.0-1 is available from:
>
> http://people.apache.org/~vajda/staging_area/
>
> A list of changes in this release can be seen at:
> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/CHANGES
> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES
>
> Please vote to release these artifacts as PyLucene 3.0.0-1.
>
> Thanks !
>
> Andi..
>
> ps: the KEYS file for PyLucene release signing is at:
> http://svn.apache.org/repos/asf/lucene/pylucene/dist/KEYS
> http://people.apache.org/~vajda/staging_area/KEYS
>
> [1] http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x88E27CA20ED7633F
> [2] http://lucene.apache.org/java/3_0_0/changes/Changes.html
> [3] http://lucene.apache.org/java/3_0_0/changes/Changes.html#3.0.0.api_changes
--------------------------
Grant Ingersoll
http://www.lucidimagination.com/
Search the Lucene ecosystem (Lucene/Solr/Nutch/Mahout/Tika/Droids) using Solr/Lucene:
http://www.lucidimagination.com/search
Re: [VOTE] Release PyLucene 3.0.0-1 (rc2) (nag)
Posted by Grant Ingersoll <gs...@apache.org>.
+1
On Dec 3, 2009, at 12:55 PM, Andi Vajda wrote:
>
> This vote is still open. We need one more +1 PMC vote before PyLucene 3.0.0 can be released.
>
> Thanks !
>
> Andi..
>
> ---------- Forwarded message ----------
> Date: Sun, 29 Nov 2009 16:02:50 -0800 (PST)
> From: Andi Vajda <va...@apache.org>
> Reply-To: pylucene-dev@lucene.apache.org, Andi Vajda <va...@apache.org>
> To: pylucene-dev@lucene.apache.org, general@lucene.apache.org
> Subject: [VOTE] Release PyLucene 3.0.0-1 (rc2)
>
>
> New artifacts for this release were made to include a fix for building on Windows with MSVC.
>
> -----------
>
> With the recent release of Java Lucene 3.0.0, a PyLucene 3.0.0-1 release closely tracking it is ready.
>
> ATTENTION: Lucene Java 3.0.0 has seen many changes to its API. While Java
> users can methodically port their code from Lucene 2.9.1 to
> Lucene 3.0.0 by watching for and eliminating deprecation warnings
> while compiling their code against the Lucene 2.9.1 release, no
> such luxury is afforded to Python users. APIs that were
> deprecated in Lucene 2.x have been removed from Lucene 3.0.0 and
> will trigger Python runtime errors in applications coded with
> PyLucene 2.x. Please, refer to Lucene's 3.0.0 changelist [2], in
> particular to its API changes section [3], for all the details.
>
> Release candidate 2 of PyLucene 3.0.0-1 is available from:
>
> http://people.apache.org/~vajda/staging_area/
>
> A list of changes in this release can be seen at:
> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/CHANGES
> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES
>
> Please vote to release these artifacts as PyLucene 3.0.0-1.
>
> Thanks !
>
> Andi..
>
> ps: the KEYS file for PyLucene release signing is at:
> http://svn.apache.org/repos/asf/lucene/pylucene/dist/KEYS
> http://people.apache.org/~vajda/staging_area/KEYS
>
> [1] http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x88E27CA20ED7633F
> [2] http://lucene.apache.org/java/3_0_0/changes/Changes.html
> [3] http://lucene.apache.org/java/3_0_0/changes/Changes.html#3.0.0.api_changes
--------------------------
Grant Ingersoll
http://www.lucidimagination.com/
Search the Lucene ecosystem (Lucene/Solr/Nutch/Mahout/Tika/Droids) using Solr/Lucene:
http://www.lucidimagination.com/search
Re: [VOTE] Release PyLucene 3.0.0-1 (rc2) (nag)
Posted by Sujan Shakya <su...@gmail.com>.
On Wed, Dec 9, 2009 at 8:18 AM, Andi Vajda <va...@apache.org> wrote:
>
> On Fri, 4 Dec 2009, Sujan Shakya wrote:
>
> PyLucene 3.0.0 worked for me as well in FreeBSD 7.0. So +1 vote from my
>> side.
>>
>> But I needed to configure and change some paths.
>>
>> In jcc/setup.py, the flags I added for FreeBSD are:
>>
>> JDK = {
>> 'freebsd7': '/usr/local/diablo-jdk1.6.0',
>> }
>> INCLUDES = {'freebsd7': ['%(freebsd7)s/include' %(JDK),
>> '%(freebsd7)s/include/freebsd' %(JDK)],
>> }
>> CFLAGS = {
>> 'freebsd7': ['-fno-strict-aliasing', '-Wno-write-strings'],
>> }
>> DEBUG_CFLAGS = {
>> 'freebsd7': ['-O0', '-g', '-DDEBUG'],
>> }
>> LFLAGS = {
>> 'freebsd7': ['-L%(freebsd7)s/jre/lib/i386' %(JDK), '-ljava',
>> '-L%(freebsd7)s/jre/lib/i386/client' %(JDK), '-ljvm',
>>
>> '-Wl,-rpath=%(freebsd7)s/jre/lib/i386:%(freebsd7)s/jre/lib/i386/server'
>> %(JDK)],
>> }
>> JAVAC = {
>> 'freebsd7': ['javac'],
>> }
>>
>> Shared object "libverify.so", required by "libjava.so", needs to be
>> linked.
>> So, I add the following to /etc/rc.conf:
>>
>> ldconfig -m /usr/local/diablo-jdk1.6.0/jre/lib/i386/
>>
>
> Thank you for the freebsd7 changes, I added to them jcc/setup.py on trunk.
> There was a discrepancy between -rpath and -L in LFLAGS where you're using
> client in one and server in the other. I opted for client but, of course,
> that can be changed.
>
Yes I should have used client one. That was my mistake. :)
>
> About requiring libverify.so, you might be able to get away with adding it
> to the link line in LFLAGS as well so that you then don't have to play the
> ldconfig -m trick. So I added -lverify into the LFLAGS.
>
> Could you please try it out and see if you still need the ldconfig -m
> treatment ? This is checked in to trunk rev 888682.
>
Yes that worked. After adding -lverify in LFLAGS, I no longer needed
ldconfig -m treatment.
Thanks.
>
> Thanks !
>
> Andi..
/suzan
Sent from Kathmandu, Nepal
Re: [VOTE] Release PyLucene 3.0.0-1 (rc2) (nag)
Posted by Andi Vajda <va...@apache.org>.
On Fri, 4 Dec 2009, Sujan Shakya wrote:
> PyLucene 3.0.0 worked for me as well in FreeBSD 7.0. So +1 vote from my
> side.
>
> But I needed to configure and change some paths.
>
> In jcc/setup.py, the flags I added for FreeBSD are:
>
> JDK = {
> 'freebsd7': '/usr/local/diablo-jdk1.6.0',
> }
> INCLUDES = {'freebsd7': ['%(freebsd7)s/include' %(JDK),
> '%(freebsd7)s/include/freebsd' %(JDK)],
> }
> CFLAGS = {
> 'freebsd7': ['-fno-strict-aliasing', '-Wno-write-strings'],
> }
> DEBUG_CFLAGS = {
> 'freebsd7': ['-O0', '-g', '-DDEBUG'],
> }
> LFLAGS = {
> 'freebsd7': ['-L%(freebsd7)s/jre/lib/i386' %(JDK), '-ljava',
> '-L%(freebsd7)s/jre/lib/i386/client' %(JDK), '-ljvm',
>
> '-Wl,-rpath=%(freebsd7)s/jre/lib/i386:%(freebsd7)s/jre/lib/i386/server'
> %(JDK)],
> }
> JAVAC = {
> 'freebsd7': ['javac'],
> }
>
> Shared object "libverify.so", required by "libjava.so", needs to be linked.
> So, I add the following to /etc/rc.conf:
>
> ldconfig -m /usr/local/diablo-jdk1.6.0/jre/lib/i386/
Thank you for the freebsd7 changes, I added to them jcc/setup.py on trunk.
There was a discrepancy between -rpath and -L in LFLAGS where you're using
client in one and server in the other. I opted for client but, of course,
that can be changed.
About requiring libverify.so, you might be able to get away with adding it
to the link line in LFLAGS as well so that you then don't have to play the
ldconfig -m trick. So I added -lverify into the LFLAGS.
Could you please try it out and see if you still need the ldconfig -m
treatment ? This is checked in to trunk rev 888682.
Thanks !
Andi..
Re: [VOTE] Release PyLucene 3.0.0-1 (rc2) (nag)
Posted by Sujan Shakya <su...@gmail.com>.
Hi, PyLucene users,
PyLucene 3.0.0 worked for me as well in FreeBSD 7.0. So +1 vote from my
side.
But I needed to configure and change some paths.
In jcc/setup.py, the flags I added for FreeBSD are:
JDK = {
'freebsd7': '/usr/local/diablo-jdk1.6.0',
}
INCLUDES = {
'freebsd7': ['%(freebsd7)s/include' %(JDK),
'%(freebsd7)s/include/freebsd' %(JDK)],
}
CFLAGS = {
'freebsd7': ['-fno-strict-aliasing', '-Wno-write-strings'],
}
DEBUG_CFLAGS = {
'freebsd7': ['-O0', '-g', '-DDEBUG'],
}
LFLAGS = {
'freebsd7': ['-L%(freebsd7)s/jre/lib/i386' %(JDK), '-ljava',
'-L%(freebsd7)s/jre/lib/i386/client' %(JDK), '-ljvm',
'-Wl,-rpath=%(freebsd7)s/jre/lib/i386:%(freebsd7)s/jre/lib/i386/server'
%(JDK)],
}
JAVAC = {
'freebsd7': ['javac'],
}
Shared object "libverify.so", required by "libjava.so", needs to be linked.
So, I add the following to /etc/rc.conf:
ldconfig -m /usr/local/diablo-jdk1.6.0/jre/lib/i386/
Then in Makefile, I needed to do one change:
PREFIX_PYTHON=/usr/local (instead of /usr)
Then instead of make, I needed to run:
gmake
sudo gmake install
sudo gmake test
With all these, I could run pylucene well.
I hope these changes be added in the next release version so that other
FreeBSD users have very less to configure.
Thanks
/suzan
Re: [VOTE] Release PyLucene 3.0.0-1 (rc2) (nag)
Posted by Helmut Jarausch <ja...@igpm.rwth-aachen.de>.
PyLucene-3 works just fine here.
The patch of python_setuptools havily depends on the
installed version of Python (of course)
I had to adapt it a bit.
It would be nice if there were a different solution
(Why don't the Python developers accept this patch for mainstream?)
So, +1 from me, too.
Helmut.
--
Helmut Jarausch
Lehrstuhl fuer Numerische Mathematik
RWTH - Aachen University
D 52056 Aachen, Germany
Re: [VOTE] Release PyLucene 3.0.0-1 (rc2) (nag)
Posted by Helmut Jarausch <ja...@igpm.rwth-aachen.de>.
PyLucene-3 works just fine here.
The patch of python_setuptools havily depends on the
installed version of Python (of course)
I had to adapt it a bit.
It would be nice if there were a different solution
(Why don't the Python developers accept this patch for mainstream?)
So, +1 from me, too.
Helmut.
--
Helmut Jarausch
Lehrstuhl fuer Numerische Mathematik
RWTH - Aachen University
D 52056 Aachen, Germany