Just force the install and forget about it. ...or read on, and then force the install.
Look at the real error report:
089: t\die-in-setup.t ............... 090: t\die-in-setup.t ............... 1/1 # Failed test 'die in setu +p caused test method to fail' 091: # at t\die-in-setup.t line 28. 092: # STDERR is: 093: # # Failed test 'setup_method (for test method 'test') died (oo +ps - we died)' 094: # # at t\die-in-setup.t line 27. 095: # # (in Foo->setup_method) 096: # 097: # not: 098: # # Failed test 'setup_method (for test method 'test') died (oo +ps - we died)' 099: # 100: # # at t/die-in-setup.t line 27. 101: # 102: # # (in Foo->setup_method) 103: # 104: # as expected 105: t\die-in-setup.t ............... Failed 1/1 subtests
In other words, the test failed because the output was:
Failed test 'setup_method (for test method 'test') died (oops - we die +d)' at t\die-in-setup.t line 27. (in Foo->setup_method)
...when the expected output was...
Failed test 'setup_method (for test method 'test') died (oops - we die +d)' at t/die-in-setup.t line 27. (in Foo->setup_method)
The test failed over the placement of three newlines -- possibly a line-endings cross-platform incompatibility. It's an innocuous failure at worst (and really rather silly).
So by all means, force the install using sisyphus's suggestion above.
Dave
In reply to Re: Padre Install: Warning: prerequisite Debug::Client 0.20 not found.
by davido
in thread Padre Install: Warning: prerequisite Debug::Client 0.20 not found.
by tjdexter1
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |