Build error: No ingredient version satisfies build dependency x 24

1

Perl build suddenly has missing dependencies

My ActivePerl 5.28 build has suddenly stopped building because of 24 missing dependencies. Any ideas?

  • No ingredient version satisfies build dependency language/perl Dist::CheckConflicts >= 0.2 (of requirement language/perl DateTime-Locale)
  • No ingredient version satisfies build dependency language/perl File::ShareDir::Install >= 0.6 (of requirement language/perl DateTime-Locale)
  • No ingredient version satisfies runtime dependency language/perl File::Which >= 1.9 (of requirement language/perl Devel-NYTProf)
  • No ingredient version satisfies build dependency language/perl Dist::CheckConflicts >= 0.2 (of requirement language/perl Package-Stash)
  • No ingredient version satisfies build dependency language/perl ExtUtils::CBuilder >= 0.27 (of requirement language/perl Params-Util)
  • No ingredient version satisfies runtime dependency language/perl List::Util >= 1.9 (of requirement language/perl Test-Deep)
  • No ingredient version satisfies runtime dependency language/perl Scalar::Util >= 1.9 (of requirement language/perl Test-Deep)
  • No ingredient version satisfies runtime dependency language/perl Algorithm::Diff >= 1.19 (of requirement language/perl Text-Diff)
  • No ingredient version satisfies runtime dependency language/perl Socket:: >= 2.7 (of requirement language/perl Net-Ping)
  • No ingredient version satisfies build dependency language/perl Test::SubCalls >= 1.7 (of requirement language/perl PPI)
  • No ingredient version satisfies runtime dependency language/perl List::MoreUtils >= 0.16 (of requirement language/perl PPI)
  • No ingredient version satisfies build dependency language/perl File::ShareDir::Install >= 0.3 (of requirement language/perl File-ShareDir)
  • No ingredient version satisfies build dependency language/perl Test::Script >= 1.5 (of requirement language/perl File-Which)
  • No ingredient version satisfies build dependency language/perl Dist::CheckConflicts >= 0.2 (of requirement language/perl DateTime)
  • No ingredient version satisfies build dependency language/perl CPAN::Meta >= 2.14 (of requirement language/perl Module-Build)
  • No ingredient version satisfies runtime dependency language/perl ExtUtils::CBuilder >= 0.27 (of requirement language/perl Module-Build)
  • No ingredient version satisfies build dependency language/perl ExtUtils::InstallPaths >= 0.2 (of requirement language/perl Module-Build-Tiny)
  • No ingredient version satisfies build dependency language/perl Dist::CheckConflicts >= 0.2 (of requirement language/perl Moose)
  • No ingredient version satisfies runtime dependency language/perl HTTP::Request::Common >= 6.3 (of requirement language/perl HTML-Form)
  • No ingredient version satisfies build dependency language/perl List::MoreUtils >= 0.19 (of requirement language/perl Perl-Critic)
  • No ingredient version satisfies runtime dependency language/perl B::Keywords >= 1.5 (of requirement language/perl Perl-Critic)
  • No ingredient version satisfies runtime dependency language/perl List::MoreUtils >= 0.19 (of requirement language/perl Perl-Critic)
  • No ingredient version satisfies runtime dependency language/perl PPIx::Regexp >= 0.27 (of requirement language/perl Perl-Critic)
  • No ingredient version satisfies runtime dependency language/perl version:: >= 0.77 (of requirement language/perl Perl-Critic)
1 Like
2

That looks like it’s erroring on all the old style version numbers.
There was an update applied recently that revised the way version numbers were reported in the asset library. You will probably find that all of those versions are still available, but need to be manually updated to point to the same version number reported in the new format.
For example, the recipe is looking for Socket >= 2.7 whereas the new reported version number for that component is 2.027

1 Like
3

Different failure

Thanks. Unfortunately the build failed agaiain, this time for a different reason.

I couldn’t see any of the required versions available in the drop-downs in the Configuration tab, so I reverted it to version 5.26.3 and then back to 5.28.1 to force a full rebuild.

Now I get a different build error, even though 299 of 299 packages successfully built.

Reason: The build encountered an unexpected error. Please consult the build log for more details… Build failures: ModulesAndLibs. Command exits with 2: gzip -c -d C:\Temp/distfiles/CPAN/platform-sources/data-acquisition/6af0b3cc2efa99e7463a48bfb046c5aaca1c77c9249bd1680962918c191ff850/Test2-Suite-0.000120.tar.gz | tar xf - stopped at C:/build/camel/lib/ActiveState/Build/Utils.pm line 276.

  • One or more artifacts failed to build or were skipped

  • The build encountered an unexpected error. Please consult the build log for more details… Build failures: ModulesAndLibs. Command exits with 2: gzip -c -d C:\Temp/distfiles/CPAN/platform-sources/data-acquisition/6af0b3cc2efa99e7463a48bfb046c5aaca1c77c9249bd1680962918c191ff850/Test2-Suite-0.000120.tar.gz | tar xf - stopped at C:/build/camel/lib/ActiveState/Build/Utils.pm line 276.

2 Likes
4

That’s a transient back end error. For Windows builds, we’re getting a lot of them with the latest version of the builder. We’re working on a solution for the bottleneck that has been exposed by the update.

If you change something and get the build restarted it will get another chance, and that’s often enough. You might see the same thing again on a different module though.

5

Our problem on the back end has been worked around. I poked your project to get it restarted.

6

Perfect, thanks. Successfully downloaded the latest build.

1 Like
7

Fix damages administration (owner)