Skip Menu |

This queue is for tickets about the Gimp CPAN distribution.

Report information
The Basics
Id: 110704
Status: resolved
Priority: 0/
Queue: Gimp

People
Owner: ETJ [...] cpan.org
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 2.31
Fixed in: 2.32



Subject: Redundant argument in sprintf (new warning in perl 5.21.x and later)
t/netplugin.t fails with newer perls because of a new unexpected warning: Redundant argument in sprintf at /tmpfs/.cpan-build/2015122812/Gimp-2.31-rUoUU1/blib/lib/Gimp/Fu.pm line 252. Additionally, there may be a Xlib warning, for example if running the tests in a vncserver environment: Xlib: extension "RANDR" missing on display ":46".
The sprintf error does not happen with 2.31_01. Thanks for the report! Is the RANDR issue still happening? If so I'll put an "unlike" in the netplugins test.
On 2016-05-02 00:04:03, ETJ wrote: Show quoted text
> The sprintf error does not happen with 2.31_01. Thanks for the report! > Is the RANDR issue still happening? If so I'll put an "unlike" in the > netplugins test.
Yes, the RANDR issue still happens (e.g. if running the tests against vncserver). With Gimp-2.31_02: ... PERL_DL_NONLAZY=1 "/opt/perl-5.18.2/bin/perl5.18.2" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t Xlib: extension "RANDR" missing on display ":32". # Failed test 'dots stderr not of concern' # at t/02-netplugin.t line 72. # 'Xlib: extension "RANDR" missing on display ":32". # ' # matches '(?^:^Xlib: extension "RANDR" missing)' # Failed test 'dots stderr not of concern' # at t/02-netplugin.t line 72. # 'Xlib: extension "RANDR" missing on display ":32". # ' # matches '(?^:^Xlib: extension "RANDR" missing)' ... etc. ...
Yes, I had made a logic error. I believe 2.31_03 fixes. Could you give it a try?
On 2016-05-02 14:57:29, ETJ wrote: Show quoted text
> Yes, I had made a logic error. I believe 2.31_03 fixes. Could you give > it a try?
I don't see any errors in 2.32, so probably it's fixed.
Agreed. Thanks for report! Closing.