Skip Menu |

This queue is for tickets about the POE CPAN distribution.

Report information
The Basics
Id: 50907
Status: resolved
Priority: 0/
Queue: POE

People
Owner: Nobody in particular
Requestors: dolmen [...] cpan.org
Cc: JDB [...] cpan.org
AdminCc:

Bug Information
Severity: Important
Broken in:
  • 1.007
  • 1.020
  • 1.266
  • 1.267
  • 1.268
  • 1.269
  • 1.280
Fixed in: (no value)



Subject: t/30_loops/select/connect_errors.t failure on Win32 (blocks ActiveState PPM auto-packaging)
Log as reported by ActiveState: ----------------- # Failed test 'timeout for connection' # at C:\cpanfly\var\megalib\POE\Test\Loops/connect_errors.pm line 61. t/30_loops/select/connect_errors.t ................ 1..3 ok 1 - found unused port: 3001 not ok 2 - timeout for connection ok 3 - run() returned successfully Failed 1/3 subtests ----------------- The full build trace can be found here: http://ppm4.activestate.com/MSWin32-x86/5.10/1000/R/RC/RCAPUTO/POE-1.280.d/log-20091015T022333.txt An unfortunate consequence of this bug is that POE::Wheel::Run::Win32 is not available anymore as ActiveState PPM because its release 0.18 is a dummy package which require POE 1.280 (due to the merge of P::W::R::W in P::W::R) but the latest available POE release in the PPM repository is 1.006. All POE auto-build reports on ActiveState are here: http://ppm4.activestate.com/idx/PO.html -- Olivier Mengué - http://o.mengue.free.fr/
Workaround to install POE::Wheel::Run::Win32 0.16: ppm install http://ppm4.activestate.com/MSWin32-x86/5.10/1000/B/BI/BINGOS/POE-Wheel-Run-Win32-0.16.ppd
Now, POE-1.006.tar.gz has been removed from CPAN (only available on BackPan.perl.org). This makes harder for a developer to build/test/distribute portable POE-based applications: - only 1.280 is available from CPAN for Unixes and Strawberry Perl - only up to 1.006 is avaibable as PPM for ActivePerl Requiring a particular version for all platforms is hard because it will require that some users have to manually build POE. -- Olivier Mengué - http://o.mengue.free.fr/
Resolved as of revision 2756.  Will be part of the next release.  Thanks for the bug report.