Description of problem: The perl-text-CSV package in EPEL6 is an old version that is impacted by CPAN bug #58356: https://rt.cpan.org/Public/Bug/Display.html?id=58356 This causes broken CSV files to be generated when using the quote_space option is disabled and CSV fields have embedded commas. This was fixed in version 1.18 of Text::CSV. I would suggest upgrading the package to version 1.21 or higher. Simply rebuilding the 1.21 perl-Text-CSV source RPM from Fedora 15 on RHEL6 worked perfectly for me. Version-Release number of selected component (if applicable): 1.16-2.el6 How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
perl-Text-CSV-1.16-2.el6.1 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/perl-Text-CSV-1.16-2.el6.1
Package perl-Text-CSV-1.16-2.el6.1: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing perl-Text-CSV-1.16-2.el6.1' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-0312/perl-Text-CSV-1.16-2.el6.1 then log in and leave karma (feedback).
Please note that I cherry-picked the patch instead of rebasing to a later version so that I ensure bug-to-bug compatibility and minimize possibilities of regression in behavior that can be relied upon. Please test.
Thank you, but the problem with patching this is that I've started using this line in my perl code to ensure that it won't run on a system that will produce broken output: use Text::CSV 1.18; This just requires a minimum version of 1.18 for the module, but it will fail on this patched version. Note that Text:CSV 1.21 was a stable version all the way from the end of 2010 until 1.30 was released in June 2013. It might also require an update of Text::CSV_XS though.
perl-Text-CSV-1.16-2.el6.1 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.