[Debian-med-packaging] Bug#821959: gdcm: FTBFS on hurd, but previously did

[Tobias Frost]

Am Donnerstag, den 21.04.2016, 08:03 +0200 schrieb Mathieu Malaterre:
> Hi,
> 
> On Wed, Apr 20, 2016 at 10:31 PM, Tobias Frost <tobi at debian.org>
> wrote:
> > Source: gdcm
> > Version: 2.6.3-3
> > Severity: normal
> > 
> > You package FTBFS on hurd-i386, but previously built there.
> > 
> > Buildlog:
> > https://buildd.debian.org/status/fetch.php?pkg=gdcm&arch=hurd-i386&
> > ver=2.6.3-3&stamp=1461071042
> > 
> > Snippet:
> >  Could NOT find Java: Found unsuitable version "1.5.0", but
> > required is at
> 
> Well the exact log is:
> 
> [...]
>   Could NOT find Java: Found unsuitable version "1.5.0", but required
> is at
>   least "1.7" (found /usr/bin/java)
> [...]
> 
> So apparently only hurd and hppa are using gcj:
> 
> https://packages.debian.org/unstable/default-jdk
> 
> If gcj is not going to support 1.7 API anytime soon, I believe we can
> set GDCM compilation option back to 1.5. The default 1.7 version
> checking is not mandatory (as far as I remember), but only convenient
> for me, since this is the only version I have access to.
> 
> Gert,
> 
> If you want you can change
> GDCM_JAVA_SOURCE_VERSION/GDCM_JAVA_TARGET_VERSION to 1.5 and give it
> a
> try.
> 
> -M

Thanks for the feedback
I can try this on the porterbox ASAP. If it works I'll volunteer to NMU
it accordingly, or do you prefer to upload yourself?

(if any case, it would be appreciated if this could happen quickly, as
gdcm blocks some stuff, and we currently trying hard to decruft stuff
that blocks libpng1.2 removal...)

--
tobi