Bug #22001 for POE: Problem installing the latest version of POE

Tue Oct 10 11:57:21 2006 mikealt [...] jps.net - Ticket created

Subject:	Problem installing the latest version of POE
Date:	Tue, 10 Oct 2006 08:56:18 -0700
To:	bug-POE [...] rt.cpan.org
From:	Michael Altarriba <mikealt [...] jps.net>

Hello. I'm running Debian Stable, and trying to install the latest version of POE using "cpan". The installation fails on only one test: tests/90_regression/rt1648-tied-stderr........... # Failed test 'received STDERR despite it being tied' # in tests/90_regression/rt1648-tied-stderr.t at line 74. # Looks like you failed 1 test of 1. dubious Test returned status 1 (wstat 256, 0x100) DIED. FAILED test 1 Failed 1/1 tests, 0.00% okay I've attached two files... one is the output of "perl -v", and the other is the full output of executing "cpan POE". I'd like to install POE without forcing it, or at least find out whether the problem I'm seeing is due to POE or my own setup. I can be reached at <mikealt@jps.net>. If there are further tests I can do to help diagnose this problem, I'll be more than happy to do so. Thanks for your help...

Message body is not shown because it is too large.

This is perl, v5.8.4 built for i386-linux-thread-multi Copyright 1987-2004, Larry Wall Perl may be copied only under the terms of either the Artistic License or the GNU General Public License, which may be found in the Perl 5 source kit. Complete documentation for Perl, including FAQ lists, should be found on this system using `man perl' or `perldoc perl'. If you have access to the Internet, point your browser at http://www.perl.com/, the Perl Home Page.

Tue Oct 17 02:48:19 2006 RCAPUTO [...] cpan.org - Correspondence added

This seems like a platform- or perl-version sensitive issue. I don't know how I'm going to solve it without being able to reproduce it. Not that I haven't tried: I don't have 5.8.4 built, but I tried the test with some version I happen to have lying around: 1) poerbook:~/projects/poe/poe% /sw/perl/583-multi/bin/perl -Ilib tests/90_regression/rt1648-tied-stderr.t1..1 ok 1 - should receive STDERR even when tied 1) poerbook:~/projects/poe/poe% /sw/perl/583-single/bin/perl -Ilib tests/90_regression/rt1648-tied-stderr.t 1..1 ok 1 - should receive STDERR even when tied 1) poerbook:~/projects/poe/poe% /sw/perl/562-multi/bin/perl -Ilib tests/90_regression/rt1648-tied-stderr.t 1..1 Cannot redirect into tied STDERR. Untying it at tests/90_regression/rt1648-tied-stderr.t line 48 ok 1 - should receive STDERR even when tied 1) poerbook:~/projects/poe/poe% /sw/perl/586-multi/bin/perl -Ilib tests/90_regression/rt1648-tied-stderr.t 1..1 ok 1 - should receive STDERR even when tied I appreciate any help you can provide.

Tue Oct 17 02:48:20 2006 The RT System itself - Status changed from 'new' to 'open'

Sun Oct 29 21:31:13 2006 RCAPUTO [...] cpan.org - Correspondence added

Bug reject. I can't duplicate the problem, and the reporter isn't responding.

Sun Oct 29 21:31:17 2006 RCAPUTO [...] cpan.org - Status changed from 'open' to 'rejected'

Sun Oct 29 22:34:59 2006 mikealt [...] jps.net - Correspondence added

Subject:	Re: [rt.cpan.org #22001] Problem installing the latest version of POE
Date:	Sun, 29 Oct 2006 19:33:19 -0800
To:	bug-POE [...] rt.cpan.org
From:	Michael Altarriba <mikealt [...] jps.net>

Given that the only response I've received is this: "This seems like a platform- or perl-version sensitive issue. I don't know how I'm going to solve it without being able to reproduce it. Not that I haven't tried: I don't have 5.8.4 built, but I tried the test with some version I happen to have lying around:" and given that my request for suggestions as to how this bug could be further diagnosed was unanswered, I assumed that the maintainer was saying, in effect, "It works for me.", and was not particularly interested in pursuing the matter further. I would still be willing to provide assistance, assuming someone could give me some insight as to how I could go about doing so. In short, the reporter didn't respond because, so far as I could tell, no response was asked for. via RT wrote: Show quoted text

> <URL: http://rt.cpan.org/Ticket/Display.html?id=22001 > > > Bug reject. I can't duplicate the problem, and the reporter isn't > responding. > >

Sun Oct 29 22:35:00 2006 The RT System itself - Status changed from 'rejected' to 'open'

Mon Jan 01 14:36:09 2007 RCAPUTO [...] cpan.org - Correspondence added

On Sun Oct 29 22:34:59 2006, mikealt@jps.net wrote: Show quoted text

> Given that the only response I've received is this: > > "This seems like a platform- or perl-version sensitive issue. I don't > know how I'm going to solve it without being able to reproduce it. Not > that I haven't tried: I don't have 5.8.4 built, but I tried the test > with some version I happen to have lying around:" > > and given that my request for suggestions as to how this bug could be > further diagnosed was unanswered, I assumed that the maintainer was > saying, in effect, "It works for me.", and was not particularly > interested in pursuing the matter further.

I also closed with "I appreciate any help you can provide." Please accept my apology for not being more specific about needing help or the kind of help I need. To be perfectly clear, I need help on this one. Without the ability to reproduce this problem, I cannot track it down and fix it. To make debugging this possible, I'll need one of two things: 1. Access to a system where I can reproduce and debug the problem myself. 2. Access to someone who can reproduce the problem and do some old-fashioned debugging to, at the very least, isolate its cause. There's no magic bullet here. Someone (possibly me) will need to track the error from the test failure back to its source. Once the source is isolated, I can help determine whether it's a flaw in POE or Perl (probably by comparing the broken behavior with that on a working system). I may be able to supply an experimental fix or workaround. Once verified, the fix can be applied and released. Please help if you can, either by providing an account on your system, lightly debugging the problem yourself, or suggesting something better. If you can't do any of these things, I'll close the ticket again and wait for a report from someone who can. People are more likely to report a new problem than one already on file, so closing dead-end tickets tends to be more helpful than leaving them open. Thank you.

Tue Feb 27 01:31:01 2007 xantus+cpan [...] xantus.org - Correspondence added

From:

XANTUS [...] cpan.org

Please check out the latest svn copy and confirm that this is fixed. Thanks! David On Mon Jan 01 14:36:09 2007, RCAPUTO wrote: Show quoted text

> On Sun Oct 29 22:34:59 2006, mikealt@jps.net wrote:

> > Given that the only response I've received is this: > > > > "This seems like a platform- or perl-version sensitive issue. I don't > > know how I'm going to solve it without being able to reproduce it. Not > > that I haven't tried: I don't have 5.8.4 built, but I tried the test > > with some version I happen to have lying around:" > > > > and given that my request for suggestions as to how this bug could be > > further diagnosed was unanswered, I assumed that the maintainer was > > saying, in effect, "It works for me.", and was not particularly > > interested in pursuing the matter further.

> > I also closed with "I appreciate any help you can provide." Please > accept my apology for not being more specific about needing help or the > kind of help I need. > > To be perfectly clear, I need help on this one. Without the ability to > reproduce this problem, I cannot track it down and fix it. > > To make debugging this possible, I'll need one of two things: > > 1. Access to a system where I can reproduce and debug the problem myself. > > 2. Access to someone who can reproduce the problem and do some > old-fashioned debugging to, at the very least, isolate its cause. > > There's no magic bullet here. Someone (possibly me) will need to track > the error from the test failure back to its source. Once the source is > isolated, I can help determine whether it's a flaw in POE or Perl > (probably by comparing the broken behavior with that on a working > system). I may be able to supply an experimental fix or workaround. > Once verified, the fix can be applied and released. > > Please help if you can, either by providing an account on your system, > lightly debugging the problem yourself, or suggesting something better. > > If you can't do any of these things, I'll close the ticket again and > wait for a report from someone who can. People are more likely to > report a new problem than one already on file, so closing dead-end > tickets tends to be more helpful than leaving them open. > > Thank you.

Sun Jul 22 01:39:53 2007 RCAPUTO [...] cpan.org - Correspondence added

I regret that I must re-reject this ticket. I have not been able to reproduce the problem after all this time. I know this doesn't confirm the absence of a problem, but it does prevent me from doing anything about it. If you still would like me to check into this, please set up an account for me on the machine where the problem happens. Send the account particulars directly to rcaputo@cpan.org rather than via this ticket. I'll be happy to log in and have a look. Thank you.

Sun Jul 22 01:39:57 2007 RCAPUTO [...] cpan.org - Status changed from 'open' to 'rejected'

Sun Jul 22 14:54:54 2007 maltarriba [...] comcast.net - Correspondence added

CC:	" via RT" <bug-POE [...] rt.cpan.org>
Subject:	Re: [rt.cpan.org #22001] Problem installing the latest version of POE
Date:	Sun, 22 Jul 2007 18:54:21 +0000
To:	bug-POE [...] rt.cpan.org, mikealt [...] jps.net
From:	maltarriba [...] comcast.net

I very much appreciate all of your hard work and attention. Please feel free to close the ticket... I am using a new, up to date setup, and very much doubt this problem will re-surface. Show quoted text

-------------- Original message ---------------------- From: " via RT" <bug-POE@rt.cpan.org>

> > <URL: http://rt.cpan.org/Ticket/Display.html?id=22001 > > > I regret that I must re-reject this ticket. I have not been able to > reproduce the problem after all this time. I know this doesn't confirm > the absence of a problem, but it does prevent me from doing anything > about it. > > If you still would like me to check into this, please set up an account > for me on the machine where the problem happens. Send the account > particulars directly to rcaputo@cpan.org rather than via this ticket. > I'll be happy to log in and have a look. > > Thank you.

Sun Jul 22 14:54:56 2007 The RT System itself - Status changed from 'rejected' to 'open'

Sun Jul 22 19:34:07 2007 RCAPUTO [...] cpan.org - Status changed from 'open' to 'resolved'