Jeff Breidenbach [EMAIL PROTECTED] said: > Hi, I did a little digging. Package gcj-3.4 was removed > from Debian Unstable on Aug 14, 2005 because it was > "Not Built by Source"
I also did some digging. I found the same removal message and then tracked down a gcj maintainer IRC. He simply said: <doko> moconnor: we only want to have one gcj version So, that's that. Also, all the gcj-3.4 bugs were reassigned to gcj-4.0. > * Swig sounds like it is progressing just fine. I was able to build PyLucene with what will be SWIG 1.3.28. However, PyLucene failed to load. So work is needed there but at least it's not generating bad stuff, that's a plus. > >PyLucene only works with Python 2.4 so to make use of it > >ensure you are using /usr/bin/python2.4 and not /usr/bin/python. > > * Mathew, the PyLucene module will not be found if one tries to > import it from python 2.3 right? I don't have the PyLucene package > in front of me to double check this. Correct. It goes in /usr/lib/python2.4/site-packages/. I figured this was a fine place b/c it is where python2.4-elementtree puts itself. > * I guess backports.org is still an open question. > > Anyway, great job on getting this far with the sarge packages. > Matthew, you've already made a significant positive difference, and > I'm already hearing positive comments. Most recently from a hacker > at PARC (my employer) who is actively migrating an internal application > called UpLib from Java Lucene towards PyLucene. Cool. I submitted the repository to http://www.apt-get.org as well. As asked around and it looks like the backports.org path is as you describe: unstable or testing packages which get backported. -matthew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]