> 1) libsvn-java no longer builds with Debian's mix of ecj/gcj.  The
> developers all use Sun Java, of course, and their response is "gcj?
> You've got to be kidding."  I still have to figure out how to fix that,
> which isn't all that easy, given that I'm not a Java programmer, but I
> at least know what the immediate problem is.

Still a problem.

> 2) The python bindings don't build properly when building outside the
> source tree.  Apparently upstream doesn't test this very much.
> 
> 3) Same for the ruby bindings.

Both fixed.  The ruby bindings were a big pain, though.

> 4) The lenny library freeze is _very_ soon.  I don't know if I'll have
> time to fix the above problems, plus update other random things for
> 1.5, plus work out the inevitable FTBFS on random architectures, before
> that happens.

Still a problem, but I uploaded to experimental to get something out
there.  I disabled libsvn-java since it doesn't build, I'll reenable it
when I am able to fix it.
-- 
Peter Samuelson | org-tld!p12n!peter | http://p12n.org/

Attachment: signature.asc
Description: Digital signature

Reply via email to