Since Lucene has long been superceded by Lucene2, maybe the right
thing to do is kill off this package entirely. What does the
dependency tree look like these days?
___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
Rmic has apparently drifted in and out of kaffe/GNU classpath over
time. I say we just wait for GPL Sun Java and fix it then. Or punt the
Lucene package for Lucene2 if dependencies allow it, and Lucene2 gets
into main (again, depending on GPL Sun Java)
Varun, good to hear from you again. Welcome.
--Jeff
___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Hi all,
I messed up the file permissions when uploading a
new package (jhove) to ftp-master, leading to package
rejection.
And I am too tired right now to go through the gpg-erific
file deletion procedure to try again tonight. If there is a
DD who has energy and is willing to complete the
When we went through this for Lucene 1.4.3, the trick was to compile
under main, and then make sure the regression tests passed if Sun Java
was installed. That way we knew the package was ok to ship and the
problems were all in the runtime.
But seriously, what's the ETA for Sun Java to enter
Awesome!
--Jeff
___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
An endianess problem sounds like a buffer overrun, which
presumably only happens in native code. I wonder if running kaffe
under valgrind while performing the unit test would show anything
interesting. Is GNU Classpath written in native code or in Java?
I'm available for upload tonight. Will be out eating dinner shortly,
though.
Barry, do you think we'll need to reupload after kaffe fixes unicode
(my guess is no, but the easy way to check is run the unit tests with
a Sun runtime after compiling with kaffe). In any case, it will be very
good to
I had exactly this problem, too. Removing the old eclipse-platform 2.1.x
solved it.
--Jeff
___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Package: eclipse
Version: 3.1.1-8
Severity: normal
So I went to run Eclipse on a computer that has just the Sun 1.5 JVM
and got the following:
rode:~ eclipse
searching for compatible vm...
testing /usr/lib/jvm/java-gcj...not found
testing /usr/lib/kaffe/pthreads...not found
testing
One is 347254
Btw, I didnt find the two other's bugreport about the same issue. Can
you point it?
--Jeff
___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
I temporarily do not have access to a suitable Debian build environment
to reproduce; can someone please confirm the problem?
On Wed, 29 Mar 2006 2:31 am, Daniel Schepler wrote:
Package: lucene
Version: 1.4.3-9
Severity: serious
From my pbuilder build log:
...
[javac] Compiling 160
I now see the compiler is overridden to jikes. I'm going to switch
that to javac so we can hopefully happily build on both sid and etch.
Testing now on my pbuilder chroot.
-Jeff
___
pkg-java-maintainers mailing list
Testing now on my pbuilder chroot.
Worked, but I could not get the deb out. On the other hand, pdebuild
failed for me.
___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
Has anyone successfully installed java3d such that firefox
can see it and run a 3d applet? If so, I'd sure like to know
what it takes.
Cheers,
Jeff
___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
It took forever and a day to get RMI support in kaffe - looks like other
java environments are still lagging.
--Jeff
___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
Given how much grief there's been with Lucene 1.4.x, I think it
makes sesne to package version 2.x as a separate package.
It will may also be easier to start out in contrib and use Sun
Java to build.
Jeff
___
pkg-java-maintainers mailing list
However, I would prefer it to be etch-ignored instead of set to
'important', since serious bugs are less likely to be ignored.
With all due respect, tough toenails. :)
___
pkg-java-maintainers mailing list
This bug does not have a major effect on the usability of the package
so I am therefore resetting severity to normal. It will not be ignored. After
the Sun JDK enters main (post etch), we will rebuild the package with it.
Hopefully that will resolve the intermittent build failure.
Jeff
Wonderful!
My initial suggestions are to build the JavaCC portions, don't depend
on the precompiled classes shipped with Lucene. Also, I didn't see
the tests being run; this is probably a good idea. Look through the
current Debian (or Ubuntu) rules file for ideas on how to do this.
Since this
20 matches
Mail list logo
