Bug#725461: batik: FTBFS: Unable to find a javac compiler

Vincent Fourmond fourmond at debian.org
Thu Oct 17 13:07:16 UTC 2013


  Hi,

  [currently at a congress, hence not very on top of Debian things]

On Wed, Oct 16, 2013 at 8:28 PM, Markus Koschany <apo at gambaru.de> wrote:
> The current svn revision still recommends default-jre because of the
> included wrapper scripts squiggle, rasterizer, ttf2svg and svgpp. The
> recommendation for default-jre is the only thing that bothers me. The
> current dependencies on jre-headless go against the current java policy
> but the current package also needs a working JRE to run the
> aforementioned wrapper scripts. I think recommending default-jre is a
> kind of compromise here.

  Excatly...

> I agree with Emmanuel Bourg's comment from the list that it is more
> reasonable to split the package in libbatik-java and batik. I have done
> this locally and all reverse dependencies (except osmosis that FTBFS
> because of another bug) still build fine. Though I'm not 100% sure if
> one of those r-deps expects one of the wrapper scripts to be included in
> libbatik-java, otherwise it would be simple.

  This is the sensible thing to do, and one I should have done ages
ago, but evaluating the impact on rdeps/build-rdeps is far from
trivial, so this is not a change to be acted too lightly -- and one of
the reasons why I refrained from doing so, mostly because I didn't
have the time to look.

> Hence I think uploading the current changes would be a good idea and I
> will attach a patch for #566901 soon.

  I don't have the time to review the patch right now. I can have a
look this week-end, if you want more eyes, but if you feel confident
about the current state, I don't mind an upload as-is.

  Cheers, and sorry for the lack of timely feedback.

      Vincent



More information about the pkg-java-maintainers mailing list