Bug #42606 for Variable-Magic: bleadperl warnings (git'ed blead)

Wed Jan 21 05:49:10 2009 frank.wiegand [...] gmail.com - Ticket created

Subject:

bleadperl warnings (git'ed blead)

In bleadperl, $Config::Config{perl_patchlevel} is now no longer an integer but a string like »GitLive-blead-283-g1e70e88«. This causes your Makefile.PL to throw a warning: Checking perl patchlevel... Argument "GitLive-blead-283-g1e70e88" isn't numeric in int at Makefile.PL line 18. As you are int'ing this, it may cause further problems. Thanks, Frank

Wed Jan 21 07:53:58 2009 vpit [...] cpan.org - Correspondence added

Hello, Thanks for your report. Show quoted text

> In bleadperl, $Config::Config{perl_patchlevel} is now no longer an > integer but a string like »GitLive-blead-283-g1e70e88«. > > This causes your Makefile.PL to throw a warning: > > Checking perl patchlevel... Argument "GitLive-blead-283-g1e70e88" isn't > numeric in int at Makefile.PL line 18. > > As you are int'ing this, it may cause further problems.

It won't. The patchlevel just defaults to 0, and the blead-specific features are then enabled depending on which subversion of the 5.11 branch is currently in use. This means that the latest checkout will always be OK - only older ones may report failures, and this just for devel builds. The warning isn't cosmetically appealing though, so I'll hide it. Vincent.

Wed Jan 21 07:53:59 2009 The RT System itself - Status changed from 'new' to 'open'

Wed Jan 21 11:25:00 2009 vpit [...] cpan.org - Correspondence added

Actually, the latest blead doesn't even seem to set perl_patchlevel anymore - it's always empty. So it doesn't even warn. I'll deal with if it gains another meaning, but IIRC Yves was against it.

Thu Jan 22 06:40:17 2009 frank.wiegand [...] gmail.com - Correspondence added

Subject:	Re: [rt.cpan.org #42606] bleadperl warnings (git'ed blead)
Date:	Thu, 22 Jan 2009 12:36:11 +0100
To:	bug-Variable-Magic [...] rt.cpan.org
From:	Frank Wiegand <frank.wiegand [...] gmail.com>

Am Mittwoch, den 21.01.2009, 11:25 -0500 schrieb Vincent Pit via RT: Show quoted text

> <URL: https://rt.cpan.org/Ticket/Display.html?id=42606 > > > Actually, the latest blead doesn't even seem to set perl_patchlevel > anymore - it's always empty. So it doesn't even warn.

Strange, my bleadperl does: % bleadperl -MConfig -MData::Dumper -E 'say Dumper \%Config::Config' | grep patchlevel 'patchlevel' => '11', 'perl_patchlevel' => 'GitLive-blead-283-g1e70e88', 'version_patchlevel_string' => 'version 11 subversion 0 patch GitLive-blead-283-g1e70e88', I'll have to investigate. Thanks, Frank

Thu Jan 22 09:37:08 2009 vpit [...] cpan.org - Correspondence added

Le Jeu. Jan. 22 06:40:17 2009, frank.wiegand a écrit : Show quoted text

> Am Mittwoch, den 21.01.2009, 11:25 -0500 schrieb Vincent Pit via RT:

> > <URL: https://rt.cpan.org/Ticket/Display.html?id=42606 > > > > > Actually, the latest blead doesn't even seem to set perl_patchlevel > > anymore - it's always empty. So it doesn't even warn.

> > Strange, my bleadperl does: > > % bleadperl -MConfig -MData::Dumper -E 'say Dumper \%Config::Config' | > grep patchlevel > 'patchlevel' => '11', > 'perl_patchlevel' => 'GitLive-blead-283-g1e70e88', > 'version_patchlevel_string' => 'version 11 subversion 0 > patch GitLive-blead-283-g1e70e88',

You can also say perl -V:.*patchlevel.* Show quoted text

> > I'll have to investigate. > > > Thanks, Frank >

I can't seem to find g1e70e88 in the repo anymore (see http://perl5.git.perl.org/perl.git/commit/g1e70e88). Also, 283 is an old ref - we're now at 405. Things may have changed quite a bit in between. I know Yves was experimenting on how to correctly handle this for some time. The HEAD at the time perl was built now appears in perl -V, together with hints about possible local commits and/or uncommitted changes.

Sat Feb 14 06:57:22 2009 vpit [...] cpan.org - Status changed from 'open' to 'rejected'