From @ribasushi

This is a bug report for perl from ribasushi@​cpan.org,
generated with the help of perlbug 1.39 running under perl 5.10.1.

[Please describe your issue here]

Data​::Dumper now requires Test​::More 0.6, but does not say anything
about it in its META[1]. Makes Data​::Dumper non-installable on perls
before 5.8.8.

Also I noticed that your META has dynamic_config=1 while there is
nothing doing dynamic configuration.

Cheers

[1] https://metacpan.org/source/SMUELLER/Data-Dumper-2.136/META.yml

From @jkeenan

On Sat Dec 08 10​:10​:34 2012, ribasushi@​cpan.org wrote​:

This is a bug report for perl from ribasushi@​cpan.org,
generated with the help of perlbug 1.39 running under perl 5.10.1.

-----------------------------------------------------------------
[Please describe your issue here]

Data​::Dumper now requires Test​::More 0.6, but does not say anything
about it in its META[1].

True, but perhaps there's a larger problem here, viz., that we don't
have a 'test_requires' entry in any of the YAML files which accompany
modules in the core distribution.

$ find . -type f -name '*.yml' | xargs grep -n test_requires | wc -l
  0

Makes Data​::Dumper non-installable on perls
before 5.8.8.

But I doubt this is a real concern. After all​:

$ corelist Data​::Dumper
Data​::Dumper was first released with perl 5.005

So *a* Data​::Dumper can always be found for Perl 5.6. And I'm sure that
if someone really wanted to install an up-to-date Data​::Dumper on a
14-year-old, no-longer-maintained Perl 5.6, that person could simply
skip the tests which require Test​::More 0.6 (which in itself is a
relatively old version of that module).

Mis dos centavos.

Jim Keenan

The RT System itself - Status changed from 'new' to 'open'

From @ribasushi

On Sat, Dec 08, 2012 at 11​:17​:06AM -0800, James E Keenan via RT wrote​:

On Sat Dec 08 10​:10​:34 2012, ribasushi@​cpan.org wrote​:

This is a bug report for perl from ribasushi@​cpan.org,
generated with the help of perlbug 1.39 running under perl 5.10.1.

-----------------------------------------------------------------
[Please describe your issue here]

Data​::Dumper now requires Test​::More 0.6, but does not say anything
about it in its META[1].

True, but perhaps there's a larger problem here, viz., that we don't
have a 'test_requires' entry in any of the YAML files which accompany
modules in the core distribution.

$ find . -type f -name '*.yml' | xargs grep -n test_requires | wc -l
0

Makes Data​::Dumper non-installable on perls
before 5.8.8.

But I doubt this is a real concern. After all​:

$ corelist Data​::Dumper
Data​::Dumper was first released with perl 5.005

So *a* Data​::Dumper can always be found for Perl 5.6. And I'm sure that
if someone really wanted to install an up-to-date Data​::Dumper on a
14-year-old, no-longer-maintained Perl 5.6, that person could simply
skip the tests which require Test​::More 0.6 (which in itself is a
relatively old version of that module).

It is now a dual-lifed module, and *some* distributions now require a
Data​::Dumper upgrade. Hence why I filed the ticket.

From mail@steffen-mueller.net

On 12/08/2012 08​:41 PM, Peter Rabbitson wrote​:

It is now a dual-lifed module, and *some* distributions now require a
Data​::Dumper upgrade. Hence why I filed the ticket.

The ticket is valid, but would you care to submit a patch?

https://github.com/tsee/Data-Dumper

Best regards,
Steffen

From @ribasushi

On Sun, Dec 09, 2012 at 01​:21​:36AM -0800, mail@​steffen-mueller.net via RT wrote​:

On 12/08/2012 08​:41 PM, Peter Rabbitson wrote​:

It is now a dual-lifed module, and *some* distributions now require a
Data​::Dumper upgrade. Hence why I filed the ticket.

The ticket is valid, but would you care to submit a patch?

https://github.com/tsee/Data-Dumper

Absolutely. I didn't do it because was unaware of the external-to-p5p repo.
Submitting a separate patch for this as well.

Also is it customary for dual-life modules to have their bug queue pointing
to http​://rt.perl.org/perlbug/ ? I looked around the perldocs for a dual-life
manual of sorts, but couldn't find anything relevant.

Cheers

From @iabyn

On Sun, Dec 09, 2012 at 01​:32​:39PM +0100, Leon Timmermans wrote​:

On Sun, Dec 9, 2012 at 12​:26 PM, Peter Rabbitson <ribasushi@​cpan.org> wrote​:

Also is it customary for dual-life modules to have their bug queue pointing
to http​://rt.perl.org/perlbug/ ? I looked around the perldocs for a dual-life
manual of sorts, but couldn't find anything relevant.

If upstream is cpan, it should be reported in its own bugtracker
(typically rt.cpan.org). If upstream is blead it should be reported at
rt.perl.org. This doesn't appear to be documented well, since new
people often do it wrong. The status of a module can be looked up in
Porting/Maintainers.pl, there probably should be an easy to use
website to expose this information to the rest of the world.

perlbug currently prompts for the module name; then if there's an entry
for that module in %Module​::CoreList​::bug_tracker, suggests that the user
submit the bug via the specified tracker.

--
Modern art​:
  "That's easy, I could have done that!"
  "Ah, but you didn't!"

From @tsee

Data​::Dumper 2.139 with Peter's patch was just uploaded to PAUSE.

--Steffen

From [Unknown Contact. See original ticket]

Data​::Dumper 2.139 with Peter's patch was just uploaded to PAUSE.

--Steffen

@tsee - Status changed from 'open' to 'resolved'