Source: libsaxon-java
Version: 1:6.5.5-12
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):
> fakeroot debian/rules binary
> dh binary --with javahelper --with maven-repo-helper
> dh_testroot
> dh_prep
> dh_install
> mh_install
> jh_installjavadoc
> dh_installdocs
> dh_installchangelogs
> dh_installexamples
> 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(0x55e8dc67e1a0),
> "META-INF/MANIFEST.MF") called at /usr/bin/jh_manifest line 297
>
> main::update_jar("debian/libsaxon-java/usr/share/java/saxon-jdom-6.5.5.jar",
> undef) called at /usr/bin/jh_manifest line 209
> Could not read manifest from
> debian/libsaxon-java/usr/share/java/saxon-jdom-6.5.5.jar (2): at
> /usr/bin/jh_manifest line 298.
> make: *** [debian/rules:13: binary] Error 255
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/libsaxon-java_6.5.5-12_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.
