Bug#832856: cronometer: FTBFS: dpkg-gencontrol: error: error occurred while parsing Depends field: default-jre | java8-runtime , jarwrapper (>=0.5), , $, {source, :Version, }, ), , (, >, =, cronometer, libjcommon-java, libjfreechart-java, libswingx-java, ,

[Lucas Nussbaum]

Source: cronometer
Version: 0.9.9+dfsg-1
Severity: serious
Tags: stretch sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/«BUILDDIR»/cronometer-0.9.9+dfsg'
> dh_link usr/share/java/cronometer.jar usr/bin/cronometer
> mkdir -p debian/cronometer/usr/share/pixmaps
> cp src/img/apple-200x200.png debian/cronometer/usr/share/pixmaps/cronometer.png
> dh_auto_install
> make[1]: Leaving directory '/«BUILDDIR»/cronometer-0.9.9+dfsg'
>    dh_install
>    jh_installjavadoc
>    dh_installdocs
>    dh_installchangelogs
>    dh_installman
>    dh_lintian
>    dh_perl
>    dh_link
>    jh_installlibs
>    jh_classpath
>    jh_manifest
>    jh_exec
>    jh_depends
>    dh_strip_nondeterminism
>    dh_compress
>    dh_fixperms
>    dh_installdeb
>    dh_gencontrol
> dpkg-gencontrol: warning: can't parse dependency $
> dpkg-gencontrol: error: error occurred while parsing Depends field: default-jre | java8-runtime , jarwrapper (>=0.5),  , $, {source, :Version, }, ),  , (, >, =,  cronometer,  libjcommon-java,  libjfreechart-java,  libswingx-java, ,
> default-jre | java6-runtime | java7-runtime
> dh_gencontrol: dpkg-gencontrol -pcronometer -ldebian/changelog -Tdebian/cronometer.substvars -Pdebian/cronometer returned exit code 255
> make: *** [binary] Error 2

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/07/28/cronometer_0.9.9+dfsg-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.