Bug#675911: swig2.0: Wrong configuration for Java

2012-06-12 Thread Torsten Landschoff
Hi Mathieu, On 06/12/2012 08:23 AM, Mathieu Malaterre wrote: > On Mon, Jun 11, 2012 at 10:00 PM, Torsten Landschoff > wrote: >> On 06/04/2012 08:26 AM, Mathieu Malaterre wrote: >>> swig2.0 should be configured with default Java (default-jdk package). It >>> currently uses gcj-jdk >> You are right

Bug#675911: swig2.0: Wrong configuration for Java

2012-06-11 Thread Mathieu Malaterre
On Mon, Jun 11, 2012 at 10:00 PM, Torsten Landschoff wrote: > On 06/04/2012 08:26 AM, Mathieu Malaterre wrote: >> >> swig2.0 should be configured with default Java (default-jdk package). It >> currently uses gcj-jdk > > You are right. However, I fail to see how this renders the package unusable >

Bug#675911: swig2.0: Wrong configuration for Java

2012-06-11 Thread Torsten Landschoff
On 06/04/2012 08:26 AM, Mathieu Malaterre wrote: swig2.0 should be configured with default Java (default-jdk package). It currently uses gcj-jdk You are right. However, I fail to see how this renders the package unusable as the SWIG generated code should be portable among different Java versio

Bug#675911: swig2.0: Wrong configuration for Java

2012-06-03 Thread Mathieu Malaterre
Package: swig2.0 Version: 2.0.7-2 Severity: grave Justification: renders package unusable swig2.0 should be configured with default Java (default-jdk package). It currently uses gcj-jdk -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-update