Skip Menu |

This queue is for tickets about the CPAN-YACSmoke CPAN distribution.

Report information
The Basics
Id: 32430
Status: new
Priority: 0/
Queue: CPAN-YACSmoke
People
Owner: Nobody in particular
Requestors: TIMB [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Important
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Fri Jan 18 17:05:21 2008 TIMB [...] cpan.org - Ticket created
Subject: "perl Makefile.PL" output (stdout and stderr) should be included in NA reports
If Makefile.PL doesn't create a Makefile it can be very helpful to the author to know why. For example http://search.cpan.org/src/TIMB/Memcached-libmemcached-0.1307/Makefile.PL tries to configure and build the source to a C library that's bundled with the module. If the build fails Makefile.PL warns and exit(0)'s without creating a Makefile. The configure and build is done using system with no redirection, so their should be lots of output to stdout and, if it fails, then some to stderr as well. Yet the NA reports I've seen have no output to indicate why it's an NA report: http://www.nntp.perl.org/group/perl.cpan.testers/2008/01/msg968229.html http://www.nntp.perl.org/group/perl.cpan.testers/2008/01/msg964827.html http://www.nntp.perl.org/group/perl.cpan.testers/2008/01/msg968178.html etc Naturally it would be very helpful to me to know why these builds generated an NA report. Thanks.
  Wed Jan 30 06:23:46 2008 kane [...] cpan.org - Correspondence added
Hi Tim, On Fri Jan 18 17:05:21 2008, TIMB wrote: Show quoted text
> If Makefile.PL doesn't create a Makefile it can be very helpful to the > author to know why.
[...] Show quoted text
> Yet the NA reports I've seen have no output to indicate why it's an NA > report: > http://www.nntp.perl.org/group/perl.cpan.testers/2008/01/msg968229.html > http://www.nntp.perl.org/group/perl.cpan.testers/2008/01/msg964827.html > http://www.nntp.perl.org/group/perl.cpan.testers/2008/01/msg968178.html > etc
All 3 of the above reports are actually generated by CPAN::YACSmoke, which uses the CPANPLUS API to do its work. On systems that are able to capture buffers (basically any unix system, and windows systems with IPC::Run installed), that output is available via the API. So this is *probably* a CPAN::YACSmoke issue, and perhaps we should move this ticket. Cheers, Jos
  Wed Jan 30 06:23:47 2008 The RT System itself - Status changed from 'new' to 'open'
  Wed Jan 30 06:23:48 2008 kane [...] cpan.org - Status changed from 'open' to 'stalled'
  Thu Jan 31 06:14:16 2008 TIMB [...] cpan.org - Correspondence added
Moved to CPAN-YACSmoke queue.
  Thu Jan 31 06:14:18 2008 The RT System itself - Status changed from 'stalled' to 'open'
  Thu Jan 31 06:14:19 2008 TIMB [...] cpan.org - Status changed from 'open' to 'new'
  Thu Jan 31 06:14:19 2008 TIMB [...] cpan.org - Queue changed from CPANPLUS to CPAN-YACSmoke