Module::Build 0.36 introduced a new ( Generated ) file, 'MYMETA.yml' which is emitted into the build directory during src_compile. Modules developed prior to the advent of 0.36 will have no consideration for this fact, and some modules ( ie: Term-ProgressBar ) contain MANIFEST/Signature tests that rely on comparing the directory state with the file system, and upon finding this new file, fail the test ( ie: http://www.nntp.perl.org/group/perl.cpan.testers/2009/10/msg5660339.html ) The solution to this upstream is not entirely obvious to me yet, I believe it requires individual module authors adapting their releases to work with the latest Module::Build. In the meantime, my recommendation is to rm the signature/manifest .t files and avoid that specific check. It would be nice to have a method in the eclass that handles this so the modification work for maintainers is minimised, ie: src_unpack(){ perl-module_src_unpack; module_build_rm_manifest "t/0-signature.t" } where module_build_rm_manifest calls has_version to check for module_build versions installed, and upon seeing 0.36 or higher, removes the specified files. I believe were going to incur this problem multiple times in future for people running FEATURES="test" and if we do we can block on this metabug
I've removed the signature test from dev-perl/Term-ProgessBar.
I remember i tested all Module-Build packages and there were no further problems. I close this bug now Thanks
