Bug#952317: cronometer: FTBFS: error: No member named $memberName

Lucas Nussbaum lucas at debian.org
Sun Feb 23 13:36:55 GMT 2020


Source: cronometer
Version: 0.9.9+dfsg-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> 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 '/<<PKGBUILDDIR>>'
>    dh_install
>    jh_installjavadoc
>    dh_installdocs
>    dh_installchangelogs
>    dh_installman
>    dh_lintian
>    dh_perl
>    dh_link
>    jh_installlibs
>    jh_classpath
>    jh_manifest
> error: No member named $memberName 
>  at /usr/share/perl5/Archive/Zip/Archive.pm line 411.
> 	Archive::Zip::Archive::contents(Archive::Zip::Archive=HASH(0x5599124f4718), "META-INF/MANIFEST.MF") called at /usr/bin/jh_manifest line 297
> 	main::update_jar("debian/cronometer/usr/share/cronometer/usda_sr24.jar", undef) called at /usr/bin/jh_manifest line 209
> Could not read manifest from debian/cronometer/usr/share/cronometer/usda_sr24.jar (2):  at /usr/bin/jh_manifest line 298.
> make: *** [debian/rules:7: binary] Error 255

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/cronometer_0.9.9+dfsg-3_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.



More information about the pkg-java-maintainers mailing list