This queue is for tickets about the App-cpanminus-reporter CPAN distribution.

Report information
The Basics
Id:
114448
Status:
new
Priority:
Low/Low

People
Owner:
Nobody in particular
Requestors:
ANDK [...] cpan.org
Cc:
SREZIC [...] cpan.org
AdminCc:

BugTracker
Severity:
(no value)
Broken in:
0.17
Fixed in:
(no value)

Attachments
pass.Mojolicious-Plugin-Args-0.05.x86_64-linux.4.3.0-1-amd64.1463517292.9320.rpt



Subject: Prerequisites missing in generated report
MIME-Version: 1.0
X-Mailer: MIME-tools 5.504 (Entity 5.504)
X-RT-Interface: Web
Message-ID: <rt-4.0.18-13421-1463518954-556.0-0-0@rt.cpan.org>
X-RT-Original-Encoding: utf-8
Content-Type: multipart/mixed; boundary="----------=_1463518954-13421-2"
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 0
Content-Disposition: inline
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: binary
Content-Length: 772
Find attached one of my first reports generated by cpanm-reporter 0.17. Two things are strange in it: (1) line 39: C<Output from '':> (2) line 77: C<No requirements found> The report has not yet arrived at cpantesters, but will eventually be there tomorrow. Watch this space to find comparable material from other testers and other reporters: http://analysis.cpantesters.org/reports_by_field?SUBMIT_xxx=Submit&distv=Mojolicious-Plugin-Args-0.05&field=meta%3Adate&field=meta%3Adate&field=meta%3Afrom&field=meta%3Aosname%2Bperl&field=meta%3Awriter&field=mod%3AMojolicious Note that CPAN::Reporter usually finds the prerequisite version of Mojolicious while cpanm-reporter only found it with version 0.11 but not on 0.12-0.17. Let me know if you need more data. Best,
Subject: pass.Mojolicious-Plugin-Args-0.05.x86_64-linux.4.3.0-1-amd64.1463517292.9320.rpt
MIME-Version: 1.0
Content-Type: application/octet-stream; name="pass.Mojolicious-Plugin-Args-0.05.x86_64-linux.4.3.0-1-amd64.1463517292.9320.rpt"
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline; filename="pass.Mojolicious-Plugin-Args-0.05.x86_64-linux.4.3.0-1-amd64.1463517292.9320.rpt"
Content-Transfer-Encoding: base64
Content-Length: 6996

Message body not shown because it is not plain text.

MIME-Version: 1.0
In-Reply-To: <rt-4.0.18-13421-1463518954-556.0-0-0@rt.cpan.org>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <rt-4.0.18-13421-1463518954-556.0-0-0@rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-11277-1463535525-912.114448-0-0@rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 577
There's more to it. Renee has started to use 0.17. http://www.cpantesters.org/cpan/report/c0f600c6-1859-11e6-844e-206c02c1fdf1 This report from Renee is showing the problem with a different twist. The report says that Mojolicious was required but not available on that test run. It marks the fact with an exclamation: ! Mojolicious 0 n/a But this cannot be true, because we ee in the error message that Mojo::JSON was there which comes with Mojolicious. Besides, if a prereq would really be missing, the report would have to be qualified as INVALID, no?
MIME-Version: 1.0
In-Reply-To: <rt-4.0.18-13421-1463518954-556.0-0-0@rt.cpan.org>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <rt-4.0.18-13421-1463518954-556.0-0-0@rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-15021-1463550582-168.114448-0-0@rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 99


This service runs on Request Tracker, is sponsored by The Perl Foundation, and maintained by Best Practical Solutions.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.