Bug#764017: closure-compiler: java.lang.RuntimeException when run on architectures with gcj instead of openjdk (hurd-i386, kfreebsd-any, sparc)

[tony mancill]

On 10/05/2014 10:08 AM, Steven Chamberlain wrote:
> Hello,
> 
> tony mancill wrote:
>> Thank you for filing the bug report.  At this point (for jessie), I
>> think we should prune the supported arch list to only those platforms
>> with openjdk.
> 
> kfreebsd has openjdk-7, it's just not our default java.  And AFAIK
> having build-depends on openjdk-7-jre is not allowed.
> 
> So I think the preferred way is to build-depend on
> default-jdk (>> 2:1.7-52) - as you can see that version is only
> available on arches having openjdk-7 as default:
> https://packages.debian.org/sid/default-jre
> 
> I think this makes it easier to see (via wanna-build BD-Uninstallable
> status) that a package waits for openjdk as default.  And means it can
> build in future without change as soon as it does become available.
> 
> (the out-of-date versions must still be removed by ftpmaster after
> an upload with this change).
> 
> Thanks!
> Regards,

Hi Steven,

I don't understand how changing the B-D will have the desired effect
given that libclosure-compiler-java is an arch:all package.  Although it
would be nice to be able control this at build-time based on openjdk,
the issue is a runtime problem.

Given that the gcj-jre-headless package provides java5-runtime-headless,
we can add java6-runtime-headless to the binary package depends, which
would make the package closure-compiler uninstallable on those
architectures (until a JRE providing java6 exists).  This isn't entirely
clean, but I don't anticipate there being gcj packages that support Java
6 anytime soon.

Cheers,
tony

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20141005/65d6c2cc/attachment.sig>