-
Notifications
You must be signed in to change notification settings - Fork 561
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bleadperl v5.31.1-139-g2773b4f50f breaks MANWAR/Test-Strict-0.52.tar.gz #17109
Comments
From @andkXref: manwar/Test-Strict#30 |
From @jkeenanOn Thu, 25 Jul 2019 01:04:45 GMT, andreas.koenig.7os6VVqR@franz.ak.mind.de wrote:
Beginning with the breaking commit identified by Andreas, the test is stating that the following heredoc's perl syntax is not ok: ##### DUMMY Inline comments in the C-code for the breaking commit do indicate that perlrun is implicated. Thank you very much. |
The RT System itself - Status changed from 'new' to 'open' |
From @jkeenanOn Thu, 25 Jul 2019 02:38:13 GMT, jkeenan wrote:
And in that heredoc, it's the 'v' switch that the module is judging to be a syntax error. If that shebang line only contains '-w', then the test passes.
-- |
From @csjewell
1) I want to go 'what the?' at the combination of the v and w switches. I'm not surprised that combination of switches is now giving an error - I would have been expecting it to before this. 2) This desired behavior has been punted for a year (since 5.28.0-rc1 - it was introduced originally in 5.27.7) already. 3) An earlier version of this module was also mentioned at [perl #132577] - so the fact that this commit was coming back and might break this module has been known about for that 18 months, I would think. (It doesn't look like anybody told the module author there, however.) |
From [Unknown Contact. See original ticket]
1) I want to go 'what the?' at the combination of the v and w switches. I'm not surprised that combination of switches is now giving an error - I would have been expecting it to before this. 2) This desired behavior has been punted for a year (since 5.28.0-rc1 - it was introduced originally in 5.27.7) already. 3) An earlier version of this module was also mentioned at [perl #132577] - so the fact that this commit was coming back and might break this module has been known about for that 18 months, I would think. (It doesn't look like anybody told the module author there, however.) |
From @jkeenanOn Thu, 25 Jul 2019 01:04:45 GMT, andreas.koenig.7os6VVqR@franz.ak.mind.de wrote:
Additional CPAN modules broken by this commit: asa-1.03 ##### Revert "postpone perl_parse() exit(0) bugfix" This reverts commit 857320c, # Conflicts: perl.c | 27 ++++++++------------------- These modules have been discussed on perl5-porters list starting at https://www.nntp.perl.org/group/perl.perl5.porters/2019/07/msg255753.html. They all use Module::Install::DSL. They all PASS against the immediately preceding commit in blead but fail to configure at the commit in question. I'm inclined to think that these are cases where, though the CPAN failure can be attributed to a specific commit to blead, the commit to blead may be correct and simply exposing dodgy code in the CPAN modules, viz., use of Module::Install::DSL. Thank you very much. -- |
Looking at http://matrix.cpantesters.org/?dist=Test-Strict+0.52 it seems that the problem has gone somewhen between 5.31.2 and 5.31.3. Also, the additional CPAN modules listed in this ticket seem to pass with 5.31.7 (asa has now a new version 1.04 and ORLite does fail for all perls on my systems, unrelated to bleadperl). |
Confirmed that all CPAN distributions listed in this ticket (except ORLite) now PASS when installed with Bisecting with this invocation:
... points to the following commit:
So we can close this ticket. Thank you very much. |
Migrated from rt.perl.org#134311 (status was 'open')
Searchable as RT134311$
The text was updated successfully, but these errors were encountered: