On Sun, 23 Feb 2020 15:14:33 +0100 Lucas Nussbaum <lu...@debian.org> wrote:
> Source: terraintool
> Version: 1.13-2
> 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>>'
> > docbook-to-man debian/manpage.sgml > terraintool.1
> > dh_installman
> > make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> >    dh_icons
> >    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(0x55d144afbe08), 
> > "META-INF/MANIFEST.MF") called at /usr/bin/jh_manifest line 297
> >     
> > main::update_jar("debian/terraintool/usr/share/terraintool/terraintool.jar",
> >  Debian::Javahelper::Manifest=HASH(0x55d144afc450)) called at 
> > /usr/bin/jh_manifest line 209
> > Could not read manifest from 
> > debian/terraintool/usr/share/terraintool/terraintool.jar (2):  at 
> > /usr/bin/jh_manifest line 298.
> > make: *** [debian/rules:9: binary] Error 255
> 
> The full build log is available from:
>    http://qa-logs.debian.net/2020/02/22/terraintool_1.13-2_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.
> 
> Hi,

Is this still happening?
I couldn't reproduce this error in any way.
It was built in amd64 with a clean sid jail, a VM instance, cowbuilder and
also a docker container and the package was built (and rebuilt) successfully
everytime.
Is it possible, maybe, the error was caused by another package that was fixed?
(just wondering)

Reply via email to