Created attachment 859425 [details] suggested patch Description of problem: I think it is always right to patch upstream code, if there is any, rather than doing it My Way™ Version-Release number of selected component (if applicable): bitlbee-3.2.1-2
Matěj, looks fine.
bitlbee-3.2.1-3.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/bitlbee-3.2.1-3.el6
bitlbee-3.2.1-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/bitlbee-3.2.1-3.fc20
bitlbee-3.2.1-3.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/bitlbee-3.2.1-3.fc19
bitlbee-3.2.1-3.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/bitlbee-3.2.1-3.el5
Package bitlbee-3.2.1-3.el6: * 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 bitlbee-3.2.1-3.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1402/bitlbee-3.2.1-3.el6 then log in and leave karma (feedback).
bitlbee-3.2.1-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
bitlbee-3.2.1-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
bitlbee-3.2.1-3.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.