> > I have uploaded the Bouncy Caslte crypto library for Java to:
> > 
> >    http://debian.frogcircus.org/packages/
> > 
> > Currently I am only creating libbcprov-java, as the other packages
> > need the jar to by signed by a trusted CA (libbcprov-java needs that to
> > in order to be used as a trusted security provider).
> > 
> > I invite any interested parties to provide me feedback on this package
> > before I upload it next week.
> > 
> > It is currently slated for contrib instead of main, as no free JVM can
> > pass all of the regression tests. I've included notes on the failed
> > tests in README.Debian. If anyone has any specific suggestions on how to
> > go about resolving these problems upstream, I would love to hear them.
> 
> Did you report those bugs to the classpath mailing list?

No, that is what I was trying to ask how to do. I know the specific test
cases that fail, but assumed that I should dig deeper into the code to
find the root cause prior to reporting it. How much detail should I
gather prior to reporting it (given my current time constraints I could
report it with little detail now, but won't have time to dig into it
more myself for a while). Also running with kaffe gave different
failures than running with sablevm and gij (all failed on the same test
cases, in different ways); I'm not sure quite what to think of that.

> I'd like to help but I'm very busy and it takes me a lot of time to
> build with non-free jdk (I'm on ppc, did not generate the ibm jbk debian
> package - yeah, it's bad!)

Actually, this builds with free-java-sdk. :-) It is simply that a couple
test cases fail when executed with free JVMs.

> If you don't find nobody to review your package, I'll try to review it
> next week,

I've sent it to my sponsor, but I was also hoping to get feedback from
someone within the Java community. It would be great if you could take a
look and give me some pointers.

Charles

-- 
Five
Hundred
Thousand
Men
Use
Burma-Shave
http://burma-shave.org/jingles/1930/five

Attachment: signature.asc
Description: Digital signature

Reply via email to