On 7/6/15 8:03 AM, David Cantrell wrote: > On Wed, Jul 01, 2015 at 10:51:34AM -0700, Karen Etheridge wrote: >>> Absent evidence to the contrary, I'm going to put this down to something >>> else breaking the toolchain, and you're the one who noticed because >>> your code is toolchain-ish and so interacted with it. >> Does this mean that your smoker is fixed now? > > No, it means that I see no evidence that it needs fixing. > >> I've been seeing this issue a *lot*, across a lot of different >> distributions. Here are some other failures with the same issue: >> >> http://www.cpantesters.org/cpan/report/9ec56e7e-c332-11e4-af4e-59047db652c0 >> http://www.cpantesters.org/cpan/report/50166e4a-c332-11e4-a3e4-48ce7cb652c0 >> http://www.cpantesters.org/cpan/report/ca4a0030-c3fc-11e4-8ffc-88127db652c0 >> ... > > Thanks > I tracked down the issue here. The version of CPAN.pm the smokers are running need YAML to parse the MYMETA.yml file for prerequisites. The version of YAML on the smokers has bugs, and can't parse the MYMETA.yml file produced by these dists. This means that CPAN.pm has to fall back on reading _build/prereqs to get the prereqs, which Module::Build::Tiny doesn't create. This will also happen in the YAML module isn't installed at all.
My initial thought on this is that Module::Build::Tiny should create a compatible _build/prereqs if it wants to be usable on older toolchains.
