On Tue, Sep 25, 2012 at 02:25:04PM +0100, Alex Young wrote:
> On 25/09/12 13:31, berta...@ptitcanardnoir.org wrote:
> >>On Wed, Aug 3, 2011 at 2:09 PM, James Healy<ji...@deefa.com>  wrote:
> >>>JRuby 1.6.3 is available upstream and includes official support for ruby
> >>>1.9 syntax. Are there any plans to package 1.6.x?
> >
> >>yes, but every helping hand is welcome!
> >
> >Is there a place where this plans are documented? What are they? I might
> >be interested to help. I've already started a bit, but don't know java
> >that much and hit some symbols not found errors at compilation time.
> >
> The work was done to repackage jruby- in June: 
> http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/2012-June/039090.html

Yeah, I saw this message. Well done.
> It had no response. I presume that's because it re-ships the jars it
> requires rather than depending on existing Debian packages where
> they're available.  If I were to suggest a starting point, it would
> be to get its dependencies up to date.

I agree, shipping the jars from the upstream source is quite a violation
of Debian's policy, so this upload won't be accepted I think.

I've already begun to repackage some of its dependencies. I actually did
upgrade (privately, as a matter to test the 1.6.8 packaging) :

 * libjaffl-java
 * libjcodings-java
 * libjffi-java & libjffi-jni
 * libbytelist-java

However, even with this upgraded package I have hard time being able to
package jruby 1.6. I'm not very used to java I admit. I still get like 7
errors of unresolved symbols with this upgraded deps. All of them happen
in org.jruby.ext.posix.{POSIX,LibC}, and I have hard time understanding
why given my lame java knowledge...

I upgraded this packages considering the dependencies that fedora enforced
for its jruby 1.6 package, which can be found at :


I'll give another try latter.


This is the maintainer address of Debian's Java team
Please use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to