On Tue, Jun 16, 2009 at 9:33 PM, Elliot Shank<p...@galumph.com> wrote: > When our continuous integration machine starts with a stock 5.10.0 and tries > to upgrade M::B, CPAN.pm sees a build requirement on 0.33_01 and suspends > the build to follow the dependency, which leads to a new build with a build > requirement on 0.33_01... > > Thankfully, we've got a timeout on that build. > > So, kindly don't put M::B into the build requirements if building M::B > itself.
Interesting. The new behavior to automatically include M::B as a configure_requires if there is no configure_requires probably needs an exception from M::B itself. I haven't seen the problem myself, though that may be because I have an updated CPAN. I'll look into it on a stock 5.10. -- David
