Thorsten, Emmanuel, thanks for your answers! On Tue, Jan 27, 2015 at 04:14:04PM +0100, Thorsten Glaser wrote: > On Tue, 27 Jan 2015, Jan Niehusmann wrote: > > > Depending on openjdk-6-jdk or openjdk-7-jdk would probably fix that > > No, as you can install several JDKs.
Yes, sure - I missed that, because I tried the builds in clean chroots, where only one JDK was installed. > > But debian java policy states "Packages must be built with default-jdk". > > You could Build-Conflicts on gcj? > > But it would be better to whitelist the OpenJDK architectures > in the Architecture field of your package. That way, the m68k > buildd admins aren’t angry at you for wasting hours of CPU time > to try to install build dependencies for something, only to > abort the build due to Build-Conflicts later. Well at least on some of the gcj architectures, the package can be compiled if openjdk is installed (and gcj is not). So I'd prefer to not exclude them, but to fix the issue somehow. On Tue, Jan 27, 2015 at 04:23:28PM +0100, Emmanuel Bourg wrote: > If your package isn't 'arch: all' you can depend on default-jdk (>= 2:1.6). Yes, that would prevent failing builds, as well. But it will also exclude gcj architectures, as on these, this dependency is not available. In fact, that's the current state: https://buildd.debian.org/status/package.php?p=jzmq So it has the same effect as Thorsten's suggestion. (With the added benefit that the package will automatically become buildable when an architecture gets updated to a more recent default-jdk.) Jan -- To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150127161132.ga27...@jannic.reliablesolutions.de
