Latest Fedora delivers perl-DBIx-RunSQL 0.12. Upstream released 0.13. Please upgrade. Also please enable monitoring service to receive reports about new releases.
perl-DBIx-RunSQL-0.13-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/perl-DBIx-RunSQL-0.13-1.el5
perl-DBIx-RunSQL-0.13-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/perl-DBIx-RunSQL-0.13-1.el6
perl-DBIx-RunSQL-0.13-1.el7 has been submitted as an update for Fedora EPEL 7. https://admin.fedoraproject.org/updates/perl-DBIx-RunSQL-0.13-1.el7
perl-DBIx-RunSQL-0.13-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/perl-DBIx-RunSQL-0.13-1.fc21
perl-DBIx-RunSQL-0.13-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/perl-DBIx-RunSQL-0.13-1.fc22
Package perl-DBIx-RunSQL-0.13-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing perl-DBIx-RunSQL-0.13-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-9904/perl-DBIx-RunSQL-0.13-1.fc22 then log in and leave karma (feedback).
perl-DBIx-RunSQL-0.13-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
perl-DBIx-RunSQL-0.13-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
perl-DBIx-RunSQL-0.13-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
perl-DBIx-RunSQL-0.13-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.
perl-DBIx-RunSQL-0.13-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.