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 2010/12/09 23:54:11 UTC

[VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1 (take 2)

A bug was reported against the previous release artifacts that blocked the
release. The bug got fixed and new artifacts were uploaded, please vote 
again.

Thanks !

Andi..

-------------------

With the recent releases of Lucene Java 2.9.4 and 3.0.3, the PyLucene 2.9.4-1 
and 3.0.3-1 releases closely tracking them are ready.

Release candidates are 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/branches/pylucene_2_9/CHANGES
http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_0/CHANGES

All versions of PyLucene are built with the same version of JCC, currently 
version 2.7, included in these release artifacts.

A list of Lucene Java changes can be seen at:
http://svn.apache.org/repos/asf/lucene/java/branches/lucene_2_9/CHANGES.txt
http://svn.apache.org/repos/asf/lucene/java/branches/lucene_3_0/CHANGES.txt

Please vote to release these artifacts as PyLucene 2.9.4-1 and 3.0.3-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

pps: here is my +1

Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1 (take 2)

Posted by Adil Lotia <ad...@gmail.com>.
+1

new RC tested on:

adil:708 pylucene-3.0.3-1 $ sw_vers
ProductName: Mac OS X
ProductVersion: 10.5.8
BuildVersion: 9L31a

adil:709 pylucene-3.0.3-1 $ java -version
java version "1.5.0_26"
Java(TM) 2 Runtime Environment, Standard Edition (build
1.5.0_26-b03-376-9M3263)
Java HotSpot(TM) Client VM (build 1.5.0_26-156, mixed mode, sharing)

adil:710 pylucene-3.0.3-1 $ python -V
Python 2.7.1

(Note: python rev. different than when I reported the problem, but python27
used to crash it as well.)

-Adil


On Thu, Dec 9, 2010 at 2:54 PM, Andi Vajda <va...@apache.org> wrote:

>
> A bug was reported against the previous release artifacts that blocked the
> release. The bug got fixed and new artifacts were uploaded, please vote
> again.
>
> Thanks !
>
> Andi..
>
> -------------------
>
> With the recent releases of Lucene Java 2.9.4 and 3.0.3, the PyLucene
> 2.9.4-1 and 3.0.3-1 releases closely tracking them are ready.
>
> Release candidates are 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/branches/pylucene_2_9/CHANGES
>
> http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_0/CHANGES
>
> All versions of PyLucene are built with the same version of JCC, currently
> version 2.7, included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/java/branches/lucene_2_9/CHANGES.txt
> http://svn.apache.org/repos/asf/lucene/java/branches/lucene_3_0/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 2.9.4-1 and 3.0.3-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
>
> pps: here is my +1
>

Re: [VOTE] [Take 3] Release PyLucene 2.9.4-1 and 3.0.3-1

Posted by Michael McCandless <lu...@mikemccandless.com>.
+1

Mike

On Sun, Dec 12, 2010 at 7:51 PM, Andi Vajda <va...@apache.org> wrote:
>
> A patch that improves the finding of jni.h on Mac OS X was integrated.
> It made it worth blocking this release and preparing new release artifacts.
> No one voted on the [Take 2] artifacts and I hope this is not
> inconveniencing anyone.
>
> I also hope that this is it for PyLucene 2.9.4/3.0.3 :-)
>
> So please vote to release the artifacts available from
>   http://people.apache.org/~vajda/staging_area/
> as PyLucene 2.9.4 and PyLucene 3.0.3.
>
> Here is my +1
>
> Thanks !
>
> Andi..
>
> -------------------
>
> With the recent releases of Lucene Java 2.9.4 and 3.0.3, the PyLucene
> 2.9.4-1 and 3.0.3-1 releases closely tracking them are ready.
>
> Release candidates are 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/branches/pylucene_2_9/CHANGES
> http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_0/CHANGES
>
> All versions of PyLucene are built with the same version of JCC, currently
> version 2.7, included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/java/branches/lucene_2_9/CHANGES.txt
> http://svn.apache.org/repos/asf/lucene/java/branches/lucene_3_0/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 2.9.4-1 and 3.0.3-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
>
> pps: here is my +1
>
>
>

Re: [VOTE] [Take 3] Release PyLucene 2.9.4-1 and 3.0.3-1

Posted by Andi Vajda <va...@apache.org>.
On Sun, 12 Dec 2010, Andi Vajda wrote:

> A patch that improves the finding of jni.h on Mac OS X was integrated.
> It made it worth blocking this release and preparing new release artifacts.
> No one voted on the [Take 2] artifacts and I hope this is not inconveniencing 
> anyone.
>
> I also hope that this is it for PyLucene 2.9.4/3.0.3 :-)
>
> So please vote to release the artifacts available from
>   http://people.apache.org/~vajda/staging_area/
> as PyLucene 2.9.4 and PyLucene 3.0.3.
>
> Here is my +1

This now has passed.
Thank you to all who voted !

The releases should be announced shortly.

Andi..

Re: [VOTE] [Take 3] Release PyLucene 2.9.4-1 and 3.0.3-1

Posted by Andi Vajda <va...@apache.org>.
On Sun, 12 Dec 2010, Andi Vajda wrote:

> A patch that improves the finding of jni.h on Mac OS X was integrated.
> It made it worth blocking this release and preparing new release artifacts.
> No one voted on the [Take 2] artifacts and I hope this is not inconveniencing 
> anyone.
>
> I also hope that this is it for PyLucene 2.9.4/3.0.3 :-)
>
> So please vote to release the artifacts available from
>   http://people.apache.org/~vajda/staging_area/
> as PyLucene 2.9.4 and PyLucene 3.0.3.
>
> Here is my +1

This now has passed.
Thank you to all who voted !

The releases should be announced shortly.

Andi..

Re: [VOTE] [Take 3] Release PyLucene 2.9.4-1 and 3.0.3-1

Posted by Robert Muir <rc...@gmail.com>.
+1

On Sun, Dec 12, 2010 at 7:51 PM, Andi Vajda <va...@apache.org> wrote:
>
> A patch that improves the finding of jni.h on Mac OS X was integrated.
> It made it worth blocking this release and preparing new release artifacts.
> No one voted on the [Take 2] artifacts and I hope this is not
> inconveniencing anyone.
>
> I also hope that this is it for PyLucene 2.9.4/3.0.3 :-)
>
> So please vote to release the artifacts available from
>   http://people.apache.org/~vajda/staging_area/
> as PyLucene 2.9.4 and PyLucene 3.0.3.
>
> Here is my +1
>
> Thanks !
>
> Andi..
>
> -------------------
>
> With the recent releases of Lucene Java 2.9.4 and 3.0.3, the PyLucene
> 2.9.4-1 and 3.0.3-1 releases closely tracking them are ready.
>
> Release candidates are 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/branches/pylucene_2_9/CHANGES
> http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_0/CHANGES
>
> All versions of PyLucene are built with the same version of JCC, currently
> version 2.7, included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/java/branches/lucene_2_9/CHANGES.txt
> http://svn.apache.org/repos/asf/lucene/java/branches/lucene_3_0/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 2.9.4-1 and 3.0.3-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
>
> pps: here is my +1
>
>
>

Re: [VOTE] [Take 3] Release PyLucene 2.9.4-1 and 3.0.3-1

Posted by "Darren G." <da...@ontrenet.com>.
Good job Andi.

+1

On Sun, 2010-12-12 at 16:51 -0800, Andi Vajda wrote:

> A patch that improves the finding of jni.h on Mac OS X was integrated.
> It made it worth blocking this release and preparing new release artifacts.
> No one voted on the [Take 2] artifacts and I hope this is not 
> inconveniencing anyone.
> 
> I also hope that this is it for PyLucene 2.9.4/3.0.3 :-)
> 
> So please vote to release the artifacts available from
>     http://people.apache.org/~vajda/staging_area/
> as PyLucene 2.9.4 and PyLucene 3.0.3.
> 
> Here is my +1
> 
> Thanks !
> 
> Andi..
> 
> -------------------
> 
> With the recent releases of Lucene Java 2.9.4 and 3.0.3, the PyLucene 2.9.4-1 
> and 3.0.3-1 releases closely tracking them are ready.
> 
> Release candidates are 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/branches/pylucene_2_9/CHANGES
> http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_0/CHANGES
> 
> All versions of PyLucene are built with the same version of JCC, currently 
> version 2.7, included in these release artifacts.
> 
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/java/branches/lucene_2_9/CHANGES.txt
> http://svn.apache.org/repos/asf/lucene/java/branches/lucene_3_0/CHANGES.txt
> 
> Please vote to release these artifacts as PyLucene 2.9.4-1 and 3.0.3-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
> 
> pps: here is my +1
> 
> 



[VOTE] [Take 3] Release PyLucene 2.9.4-1 and 3.0.3-1

Posted by Andi Vajda <va...@apache.org>.
A patch that improves the finding of jni.h on Mac OS X was integrated.
It made it worth blocking this release and preparing new release artifacts.
No one voted on the [Take 2] artifacts and I hope this is not 
inconveniencing anyone.

I also hope that this is it for PyLucene 2.9.4/3.0.3 :-)

So please vote to release the artifacts available from
    http://people.apache.org/~vajda/staging_area/
as PyLucene 2.9.4 and PyLucene 3.0.3.

Here is my +1

Thanks !

Andi..

-------------------

With the recent releases of Lucene Java 2.9.4 and 3.0.3, the PyLucene 2.9.4-1 
and 3.0.3-1 releases closely tracking them are ready.

Release candidates are 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/branches/pylucene_2_9/CHANGES
http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_0/CHANGES

All versions of PyLucene are built with the same version of JCC, currently 
version 2.7, included in these release artifacts.

A list of Lucene Java changes can be seen at:
http://svn.apache.org/repos/asf/lucene/java/branches/lucene_2_9/CHANGES.txt
http://svn.apache.org/repos/asf/lucene/java/branches/lucene_3_0/CHANGES.txt

Please vote to release these artifacts as PyLucene 2.9.4-1 and 3.0.3-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

pps: here is my +1



[VOTE] [Take 3] Release PyLucene 2.9.4-1 and 3.0.3-1

Posted by Andi Vajda <va...@apache.org>.
A patch that improves the finding of jni.h on Mac OS X was integrated.
It made it worth blocking this release and preparing new release artifacts.
No one voted on the [Take 2] artifacts and I hope this is not 
inconveniencing anyone.

I also hope that this is it for PyLucene 2.9.4/3.0.3 :-)

So please vote to release the artifacts available from
    http://people.apache.org/~vajda/staging_area/
as PyLucene 2.9.4 and PyLucene 3.0.3.

Here is my +1

Thanks !

Andi..

-------------------

With the recent releases of Lucene Java 2.9.4 and 3.0.3, the PyLucene 2.9.4-1 
and 3.0.3-1 releases closely tracking them are ready.

Release candidates are 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/branches/pylucene_2_9/CHANGES
http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_0/CHANGES

All versions of PyLucene are built with the same version of JCC, currently 
version 2.7, included in these release artifacts.

A list of Lucene Java changes can be seen at:
http://svn.apache.org/repos/asf/lucene/java/branches/lucene_2_9/CHANGES.txt
http://svn.apache.org/repos/asf/lucene/java/branches/lucene_3_0/CHANGES.txt

Please vote to release these artifacts as PyLucene 2.9.4-1 and 3.0.3-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

pps: here is my +1



Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1 (take 2)

Posted by Bill Janssen <ja...@parc.com>.
Andi Vajda <va...@apache.org> wrote:

> >> I really want the latest up to date Mac OS X setup to build out of the
> >> box
> >
> > Sure, me too!
> 
> No, not today. Today's out of the box on 10.6 requires the setting to
> be under /Developer (without your patch).

Well, of course, that's why I sent you the patch :-).

> Downloading another Java package != out of the box. By out of the box,
> I mean current Xcode + whatever software update drops in on a regular
> basis, like the last Java update that lost the headers.

But what Apple is saying is that to install "current XCode" right now,
for Java, requires installing that extra download.  The current slogan
there is that being a Java developer on OS X requires "XCode plus
patches", apparently.

> >> ...and it seems that the current setup.py settings are the only way
> >> unless your patch get added ?

Of course, that will break on Lion when that's the latest and greatest.

> > My patch soft-codes the location of the SDK, so that it works with both
> > 10.5 and 10.6.  Though, after hearing from Swingler, I'd revise it as
> > follows (I just did this in Emacs, haven't tested it):
> 
> Ok then, provide a tested patch that works and applies out of the box
> to JCC's trunk, and that puts this code into a new helper file like is
> done for linux and windows (thus not adding pages of code to setup.py)
> and I'll integrate it.

OK, will do.  Wasn't sure about your feeling about it, or I would have
done it sooner.

> > Philosophically, I see little point in avoiding the use of an actual
> > programming language that using setup.py gives you.  Otherwise, might as
> > well use another Makefile.
> 
> You're not adressing the issue here: obscure automatic failures vs
> simple edits in setup.py to match your system.

Not going to touch that one... :-)

Bill

Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1 (take 2)

Posted by Andi Vajda <va...@apache.org>.
On Fri, 10 Dec 2010, Bill Janssen wrote:

> Andi Vajda <va...@apache.org> wrote:
>
>> Ok then, provide a tested patch that works and applies out of the box
>> to JCC's trunk, and that puts this code into a new helper file like is
>> done for linux and windows (thus not adding pages of code to setup.py)
>> and I'll integrate it.
>
> Here it is.  I happened to have both old and new Snow Leopard machines
> around to test it on, as well as my Leopard machines.  Works on all of
> them.  This applies to the trunk of pylucene.

Thanks, I integrated it with minor changes.
I also tested it on 10.6 and 10.5.

New release artifacts are under way...

Andi..

Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1 (take 2)

Posted by Bill Janssen <ja...@parc.com>.
Andi Vajda <va...@apache.org> wrote:

> Ok then, provide a tested patch that works and applies out of the box
> to JCC's trunk, and that puts this code into a new helper file like is
> done for linux and windows (thus not adding pages of code to setup.py)
> and I'll integrate it.

Here it is.  I happened to have both old and new Snow Leopard machines
around to test it on, as well as my Leopard machines.  Works on all of
them.  This applies to the trunk of pylucene.

Bill


Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1 (take 2)

Posted by Andi Vajda <va...@apache.org>.
On Fri, 10 Dec 2010, Bill Janssen wrote:

> Andi Vajda <va...@apache.org> wrote:
>
>> If I switch to Mike's recommendation then 10.6 is broken out of the box.
>> I don't know what developer package he's referring to. Can you please
>> send me the URL ?
>
> Here's what his message said:
>
> ``It may be necessary to install the "Java for Mac OS X 10.6 Update 3
> Developer Package" or "Java for Mac OS X 10.5 Update 8 Developer
> Package" from <http://connect.apple.com> under the "Java" section, to
> ensure the native headers are present in the JavaVM.framework. We are
> aware that this has caused some inconvenience for otherwise native
> projects that make use of the JNI API, and we are leaning towards just
> shipping the headers in the regular customer software update package.''
>
> That's the "developer package" he's referring to.
>
>> Yes, your patch should work on both but would it not be obsoleted by
>> the next time Apple moves these headers around again and setup.py is
>> reverted back to the /System value in consequence ?
>>
>> I really want the latest up to date Mac OS X setup to build out of the
>> box
>
> Sure, me too!

No, not today. Today's out of the box on 10.6 requires the setting to be 
under /Developer (without your patch). Downloading another Java package != 
out of the box. By out of the box, I mean current Xcode + whatever software 
update drops in on a regular basis, like the last Java update that lost the 
headers.

>> ...and it seems that the current setup.py settings are the only way
>> unless your patch get added ?
>
> My patch soft-codes the location of the SDK, so that it works with both
> 10.5 and 10.6.  Though, after hearing from Swingler, I'd revise it as
> follows (I just did this in Emacs, haven't tested it):

Ok then, provide a tested patch that works and applies out of the box to 
JCC's trunk, and that puts this code into a new helper file like is done for 
linux and windows (thus not adding pages of code to setup.py) and I'll 
integrate it.

> In other words, first look for the headers where Apple says they should
> be, then if they aren't there, look in the Developer SDK, but the SDK
> for the current version of OS X.
>
> Philosophically, I see little point in avoiding the use of an actual
> programming language that using setup.py gives you.  Otherwise, might as
> well use another Makefile.

You're not adressing the issue here: obscure automatic failures vs simple 
edits in setup.py to match your system.

Andi..

Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1 (take 2)

Posted by Bill Janssen <ja...@parc.com>.
Andi Vajda <va...@apache.org> wrote:

> If I switch to Mike's recommendation then 10.6 is broken out of the box.
> I don't know what developer package he's referring to. Can you please
> send me the URL ?

Here's what his message said:

``It may be necessary to install the "Java for Mac OS X 10.6 Update 3
Developer Package" or "Java for Mac OS X 10.5 Update 8 Developer
Package" from <http://connect.apple.com> under the "Java" section, to
ensure the native headers are present in the JavaVM.framework. We are
aware that this has caused some inconvenience for otherwise native
projects that make use of the JNI API, and we are leaning towards just
shipping the headers in the regular customer software update package.''

That's the "developer package" he's referring to.

> Yes, your patch should work on both but would it not be obsoleted by
> the next time Apple moves these headers around again and setup.py is
> reverted back to the /System value in consequence ?
>
> I really want the latest up to date Mac OS X setup to build out of the
> box

Sure, me too!

> ...and it seems that the current setup.py settings are the only way
> unless your patch get added ?

My patch soft-codes the location of the SDK, so that it works with both
10.5 and 10.6.  Though, after hearing from Swingler, I'd revise it as
follows (I just did this in Emacs, haven't tested it):

diff -u pylucene-3.0.3-1/jcc/setup.py.orig pylucene-3.0.3-1/jcc/setup.py
--- pylucene-3.0.3-1/jcc/setup.py.orig	2010-12-07 18:50:25.000000000 -0800
+++ pylucene-3.0.3-1/jcc/setup.py	2010-12-07 19:02:44.000000000 -0800
@@ -43,8 +43,23 @@
 else:
     JAVAHOME = None
 
+if platform in ("darwin"):
+    # possibly we shouldn't overwrite the platform module in the first place
+    import platform as _platform
+    import re
+    JAVAHOME = None
+    path = "/System/Library/Frameworks/JavaVM.framework/"
+    if os.path.isdir(path) and os.path.exists(os.path.join(path, "Headers", "jni.h")):
+        JAVAHOME = os.path.join(path, "Home")
+    else:
+        path = ("/Developer/SDKs/MacOSX" +
+                 re.match("[0-9]+\.[0-9]+", _platform.mac_ver()[0]).group(0) +
+                 ".sdk/System/Library/Frameworks/JavaVM.framework/Versions/Current")
+        if os.path.exists(path):
+            JAVAHOME = path
+
 JDK = {
-    'darwin': '/Developer/SDKs/MacOSX10.6.sdk/System/Library/Frameworks/JavaVM.framework/Versions/Current',
+    'darwin': JAVAHOME,
     'ipod': '/usr/include/gcc',
     'linux2': '/usr/lib/jvm/java-6-openjdk',
     'sunos5': '/usr/jdk/instances/jdk1.6.0',

In other words, first look for the headers where Apple says they should
be, then if they aren't there, look in the Developer SDK, but the SDK
for the current version of OS X.

Philosophically, I see little point in avoiding the use of an actual
programming language that using setup.py gives you.  Otherwise, might as
well use another Makefile.

Bill

Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1 (take 2)

Posted by Andi Vajda <va...@apache.org>.
On Fri, 10 Dec 2010, Bill Janssen wrote:

> Andi Vajda <va...@apache.org> wrote:
>
>> So, it's "broken on 10.6 out of the box" vs "broken on 10.5 out of the
>> box" or am I missing something else here ?
>
> (1) The patch I sent should work on both, out of the box.
>
> (2) Alternatively, if you hard-code the path as recommended by Mike
> Swingler, that should work on both (possibly requiring the additional
> download of a developer package for the headers -- but that's just part
> of installing the Java developer tools).

If I switch to Mike's recommendation then 10.6 is broken out of the box.
I don't know what developer package he's referring to. Can you please send 
me the URL ?

Yes, your patch should work on both but would it not be obsoleted by the 
next time Apple moves these headers around again and setup.py is reverted 
back to the /System value in consequence ?

I guess the crux of the issue/disagreement here is that you somehow have the 
expectation that JCC should build out of the box whereas I've always made it 
clear that the "out of the box" settings in Makefile and setup.py are only 
best guesses that need to be reviewed/edited and that any automation to make 
it build out of the box will make it harder for people to debug when said 
automation fails in obscure ways.

I really want the latest up to date Mac OS X setup to build out of the box 
and it seems that the current setup.py settings are the only way unless your 
patch get added ?

Andi..

Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1 (take 2)

Posted by Bill Janssen <ja...@parc.com>.
Andi Vajda <va...@apache.org> wrote:

> So, it's "broken on 10.6 out of the box" vs "broken on 10.5 out of the
> box" or am I missing something else here ?

(1) The patch I sent should work on both, out of the box.

(2) Alternatively, if you hard-code the path as recommended by Mike
Swingler, that should work on both (possibly requiring the additional
download of a developer package for the headers -- but that's just part
of installing the Java developer tools).

Bill

Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1 (take 2)

Posted by Andi Vajda <va...@apache.org>.
On Dec 10, 2010, at 10:24, Bill Janssen <ja...@parc.com> wrote:

> Andi Vajda <va...@apache.org> wrote:
>
>> A bug was reported against the previous release artifacts that  
>> blocked the
>> release. The bug got fixed and new artifacts were uploaded, please
>> vote again.
>
> This new candidate breaks immediately on OS X 10.5.8 (standard system
> Python, standard system Java):
>
>  /tmp 18 % cd pylucene-3.0.3-1/jcc
>  /tmp/pylucene-3.0.3-1/jcc 19 % python setup.py build
>  Traceback (most recent call last):
>    File "setup.py", line 75, in <module>
>      ''' %(JDK[platform]))
>  RuntimeError:
>
>  Java JDK directory '/Developer/SDKs/MacOSX10.6.sdk/System/Library/ 
> Frameworks/JavaVM.framework/Versions/Current' does not exist.
>
>  Please set the environment variable JCC_JDK to the correct location  
> before
>  running setup.py.
>  %
>
> Andi, if you're going to just hardcode a JDK path in for OS X,  
> please at
> least hardcode the path advised by the Apple Java engineers (see
> previous mail), instead of one that's guaranteed to break on 10.5
> machines.  I say "guaranteed", because the Xcode for 10.5 doesn't
> include a 10.6 SDK, and if it did it wouldn't fit the installed Java.

So, it's "broken on 10.6 out of the box" vs "broken on 10.5 out of the  
box" or am I missing something else here ?

Andi..

>
> Bill

Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1 (take 2)

Posted by Bill Janssen <ja...@parc.com>.
Andi Vajda <va...@apache.org> wrote:

> A bug was reported against the previous release artifacts that blocked the
> release. The bug got fixed and new artifacts were uploaded, please
> vote again.

This new candidate breaks immediately on OS X 10.5.8 (standard system
Python, standard system Java):

  /tmp 18 % cd pylucene-3.0.3-1/jcc
  /tmp/pylucene-3.0.3-1/jcc 19 % python setup.py build
  Traceback (most recent call last):
    File "setup.py", line 75, in <module>
      ''' %(JDK[platform]))
  RuntimeError: 
                       
  Java JDK directory '/Developer/SDKs/MacOSX10.6.sdk/System/Library/Frameworks/JavaVM.framework/Versions/Current' does not exist.

  Please set the environment variable JCC_JDK to the correct location before
  running setup.py.
  %

Andi, if you're going to just hardcode a JDK path in for OS X, please at
least hardcode the path advised by the Apple Java engineers (see
previous mail), instead of one that's guaranteed to break on 10.5
machines.  I say "guaranteed", because the Xcode for 10.5 doesn't
include a 10.6 SDK, and if it did it wouldn't fit the installed Java.

Bill

Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1 (take 2)

Posted by Adil Lotia <ad...@gmail.com>.
+1

new RC tested on:

adil:708 pylucene-3.0.3-1 $ sw_vers
ProductName: Mac OS X
ProductVersion: 10.5.8
BuildVersion: 9L31a

adil:709 pylucene-3.0.3-1 $ java -version
java version "1.5.0_26"
Java(TM) 2 Runtime Environment, Standard Edition (build
1.5.0_26-b03-376-9M3263)
Java HotSpot(TM) Client VM (build 1.5.0_26-156, mixed mode, sharing)

adil:710 pylucene-3.0.3-1 $ python -V
Python 2.7.1

(Note: python rev. different than when I reported the problem, but python27
used to crash it as well.)

-Adil


On Thu, Dec 9, 2010 at 2:54 PM, Andi Vajda <va...@apache.org> wrote:

>
> A bug was reported against the previous release artifacts that blocked the
> release. The bug got fixed and new artifacts were uploaded, please vote
> again.
>
> Thanks !
>
> Andi..
>
> -------------------
>
> With the recent releases of Lucene Java 2.9.4 and 3.0.3, the PyLucene
> 2.9.4-1 and 3.0.3-1 releases closely tracking them are ready.
>
> Release candidates are 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/branches/pylucene_2_9/CHANGES
>
> http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_0/CHANGES
>
> All versions of PyLucene are built with the same version of JCC, currently
> version 2.7, included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/java/branches/lucene_2_9/CHANGES.txt
> http://svn.apache.org/repos/asf/lucene/java/branches/lucene_3_0/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 2.9.4-1 and 3.0.3-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
>
> pps: here is my +1
>

Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1 (take 2)

Posted by Bill Janssen <ja...@parc.com>.
Andi Vajda <va...@apache.org> wrote:

> A bug was reported against the previous release artifacts that blocked the
> release. The bug got fixed and new artifacts were uploaded, please
> vote again.

This new candidate breaks immediately on OS X 10.5.8 (standard system
Python, standard system Java):

  /tmp 18 % cd pylucene-3.0.3-1/jcc
  /tmp/pylucene-3.0.3-1/jcc 19 % python setup.py build
  Traceback (most recent call last):
    File "setup.py", line 75, in <module>
      ''' %(JDK[platform]))
  RuntimeError: 
                       
  Java JDK directory '/Developer/SDKs/MacOSX10.6.sdk/System/Library/Frameworks/JavaVM.framework/Versions/Current' does not exist.

  Please set the environment variable JCC_JDK to the correct location before
  running setup.py.
  %

Andi, if you're going to just hardcode a JDK path in for OS X, please at
least hardcode the path advised by the Apple Java engineers (see
previous mail), instead of one that's guaranteed to break on 10.5
machines.  I say "guaranteed", because the Xcode for 10.5 doesn't
include a 10.6 SDK, and if it did it wouldn't fit the installed Java.

Bill