Description of problem: It would be absolutely awesome if we could get rid of patches in bitlbee making it possible to work with libotr3 and switch completely to libotr4 everywhere. Given root@santiago: ~# repoquery -q --whatrequires --resolve 'libotr.so.2()(64bit)' bitlbee-otr-0:3.2.2-4.el6.x86_64 libotr-devel-0:3.2.1-1.el6.x86_64 libotr3-devel-0:3.2.1-4.el6.x86_64 pidgin-otr-0:3.2.1-1.el6.x86_64 root@santiago: ~# and that we have libotr3 in EPEL-6 for compatibility (? is it what it is for? seems kind of weird to have in the same time libotr in 3.* and libotr3 as well) I see you are also maintainer of pidgin-otr. Would it be possible to build it with libotr4 in EPEL-6?
Copr with the build is at https://copr.fedoraproject.org/coprs/mcepl/bitlbee-el6/
Just to note that even pidgin-otr from Rawhide builds without problems with libotr4 in EPEL-6. https://copr.fedoraproject.org/coprs/mcepl/bitlbee-el6/build/83409/
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version, you are encouraged to change the 'version' to a later version prior this bug is closed as described in the policy above.
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of EPEL please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.