Created attachment 1134110 [details] The patch needed for compiling. The last Version(keepassx-2.0.2) of it can be build under EL6 with one patch and some fixed on the spec file. Spec file: Patch0: keepassx-rhel6.patch %if 0%{?rhel} == 6 BuildRequires: qt4-devel >= 4.6 %endif %prep %setup -q %if 0%{?rhel} == 6 %patch0 -p1 %endif %install %make_install %find_lang %{name} --with-qt %if 0%{?rhel} == 6 rm -f %{buildroot}%{_datadir}/%{name}/translations/keepassx_en_plurals.qm %endif
I'd be hesitant to incorporate this patch as the upgrade from keepassx from 0.4 to 2.0 on other OS versions caused a fair amount of backlash as that upgrade apparently introduced interoperability problems for some users.
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.
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.