The latest version of Directory::Queue on CPAN is now 1.1. This is the version to use everywhere. Please upgrade in EPEL.
perl-Directory-Queue-1.1-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/perl-Directory-Queue-1.1-1.el5
perl-Directory-Queue-1.1-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/perl-Directory-Queue-1.1-1.fc15
perl-Directory-Queue-1.1-1.el4 has been submitted as an update for Fedora EPEL 4. https://admin.fedoraproject.org/updates/perl-Directory-Queue-1.1-1.el4
perl-Directory-Queue-1.1-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/perl-Directory-Queue-1.1-1.el6
perl-Directory-Queue-1.1-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/perl-Directory-Queue-1.1-1.fc14
Package perl-Directory-Queue-1.1-1.el4: * should fix your issue, * was pushed to the Fedora EPEL 4 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing perl-Directory-Queue-1.1-1.el4' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/perl-Directory-Queue-1.1-1.el4 then log in and leave karma (feedback).
perl-Directory-Queue-1.1-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
perl-Directory-Queue-1.1-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
perl-Directory-Queue-1.1-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.
perl-Directory-Queue-1.1-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-Directory-Queue-1.1-1.el4 has been pushed to the Fedora EPEL 4 stable repository. If problems still persist, please make note of it in this bug report.