Front page | perl.perl5.porters |
Postings from April 2018
On 03/31/2018 07:45 PM, Karl Williamson wrote: > On 03/20/2018 12:48 PM, Karl Williamson wrote: >> On 03/20/2018 12:36 PM, Sawyer X wrote: >>> >>> >>> On 03/14/2018 06:08 PM, Karl Williamson via RT wrote: >>>> On Mon, 26 Feb 2018 03:11:04 -0800, xsawyerx@gmail.com wrote: >>>>> >>>>> On 02/25/2018 01:50 AM, Leon Timmermans wrote: >>>>>> On Sat, Feb 24, 2018 at 9:08 AM, slaven@rezic.de >>>>>> <perlbug-followup@perl.org> wrote: >>>>>>> After running "install Bundle::Snapshot..." in a CPAN shell in >>>>>>> a perl 5.27.9 installation I've been left with a broken perl: >>>>>>> >>>>>>> $ perl5.27.9 -MExtUtils::MakeMaker -e1 >>>>>>> perl5.27.9: symbol lookup error: /opt/perl- >>>>>>> 5.27.9/lib/site_perl/5.27.9/x86_64-linux/auto/version/vxs/vxs.so: >>>>>>> undefined symbol: STORE_NUMERIC_LOCAL_SET_STANDARD >>>>>>> $ perl5.27.9 -MCPAN -e1 >>>>>>> perl5.27.9: symbol lookup error: /opt/perl- >>>>>>> 5.27.9/lib/site_perl/5.27.9/x86_64-linux/auto/version/vxs/vxs.so: >>>>>>> undefined symbol: STORE_NUMERIC_LOCAL_SET_STANDARD >>>>>>> $ perl5.27.9 -Mversion -MEncode -e1 >>>>>>> perl5.27.9: symbol lookup error: /opt/perl- >>>>>>> 5.27.9/lib/site_perl/5.27.9/x86_64-linux/auto/version/vxs/vxs.so: >>>>>>> undefined symbol: STORE_NUMERIC_LOCAL_SET_STANDARD >>>>>>> >>>>>>> The interesting lines in the CPAN update log are probably these: >>>>>>> >>>>>>> ... >>>>>>> vars is up to date (1.03). >>>>>>> version::regex is up to date (0.9918). >>>>>>> Running install for module 'version::vpp' >>>>>>> Checksum for >>>>>>> /home/slaven.rezic/.cpan/sources/authors/id/J/JP/JPEACOCK/version- >>>>>>> 0.9918.tar.gz ok >>>>>>> ... >>>>>>> JPEACOCK/version-0.9918.tar.gz >>>>>>> /usr/bin/make test -- OK >>>>>>> Running make install >>>>>>> ... >>>>>>> Installing /opt/perl-5.27.9/lib/site_perl/5.27.9/x86_64- >>>>>>> linux/auto/version/vxs/vxs.so >>>>>>> ... >>>>>>> version::vxs is up to date (0.9918). >>>>>>> vmsish is up to date (1.04). >>>>>>> ... >>>>>>> >>>>>>> >>>>>>> So the existence of version::vpp (which does not seem to be part of >>>>>>> newer >>>>>>> perls anymore) triggered the version.pm update, and installed a >>>>>>> version.pm >>>>>>> which is apparently incompatible with current bleadperl. >>>>>>> >>>>>>> Probably the same problem would happen if a reinstall method on >>>>>>> version >>>>>>> would be run (in a CPAN shell: test version + install_tested, with >>>>>>> cpanm: >>>>>>> cpanm --reinstall version) (not tested). >>>>>>> >>>>>>> I also noticed that vutil.c was edited in the perl core despite of >>>>>>> a notice on top of the file that it should not be edited here, but >>>>>>> in the version distribution. >>>>>>> >>>>>>> It looks like a new CPAN release of version.pm should be done. >>>>>> IMNSHO what we really need is for version to become upstream=core. >>>>>> It's far too entangled with core for anything else to make sense. >>>>> Agreed. >>>> I have heard nothing back from the maintainer. I added this to the >>>> 5.28 blockers. >>>> I'm wondering if we should proceed with a takeover of this distro. >>> >>> Let me give it a try first. >>> >> >> I sent the maintainer a personal email a few hours ago. This is my >> first attempt to reach him that way. >> > > No response None from me either. Does anyone know him and can reach out to him, please?Thread Previous