Description of problem: Please build pidgin for EPEL 9. The libpurple-devel package is at least a build-time dependency of the bitlbee, purple-telegram and purple-skypeweb packages. Version-Release number of selected component (if applicable): pidgin-2.14.8-2.fc36 Actual results: No pidgin in EPEL 9. Expected results: pidgin-2.14.8-2.el9 or better ;-) Additional info: Please let me know if you are not interested in maintaining the package on EPEL 9 branch.
https://pagure.io/releng/fedora-scm-requests/issue/41282
The following deps are unsatisfied in RHEL-9: 'gtkspell-devel' 'libgnt-devel' 'libidn-devel' 'meanwhile-devel' 'pkgconfig(avahi-glib)' 'pkgconfig(farstream-0.2)'
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36.
I believe the libidn requirement can be overcome by using libidn2 instead, which is available. Unfortunately RHEL isn't shipping its headers for avahi-glib. Is it possible to use this package instead, at least for the build environment? http://dfw.mirror.rackspace.com/almalinux/9/devel/x86_64/os/Packages/avahi-glib-devel-0.8-12.el9.x86_64.rpm
(In reply to Ladar Levison from comment #4) > I believe the libidn requirement can be overcome by using libidn2 instead, > which is available. > > Unfortunately RHEL isn't shipping its headers for avahi-glib. Is it possible > to use this package instead, at least for the build environment? > > http://dfw.mirror.rackspace.com/almalinux/9/devel/x86_64/os/Packages/avahi- > glib-devel-0.8-12.el9.x86_64.rpm I am afraid we can only use what's available in RHEL/EPEL.
(In reply to Jaroslav Škarvada from comment #5) > I am afraid we can only use what's available in RHEL/EPEL. While the answer indeed isn't wrong at all, it unfortunately does not point out the possibility to request of adding avahi-glib-devel to CRB 9 (which I did via bug #2181679 now), as documented at https://docs.fedoraproject.org/en-US/epel/epel-policy-missing-sub-packages/#long_term. Additionally, I followed https://docs.fedoraproject.org/en-US/epel/epel-policy-missing-sub-packages/#short_term to get things rolling, because I need libpurple(-devel) and pidgin in EPEL 9 now. The avahi-glib-devel package is available in EPEL 9 (via buildroot override) now. Thus from my point of view the next steps are: Branching and building libgnt, submitting as update for EPEL 9 (with buildroot override), building latest pidgin and submitting as update for EPEL 9.
Thank you for building libgnt for EPEL 9. As far as I can see the package is submitted for stable. Is there anything now which prevents from building the latest pidgin for EPEL 9? There is an active buildroot override for libgnt already.
Meanwhile libgnt was pushed to the stable repository. Anything which prevents from building the latest pidgin for EPEL 9?
(In reply to Robert Scheck from comment #8) > Meanwhile libgnt was pushed to the stable repository. Anything which > prevents from building the latest pidgin for EPEL 9? Thanks for the info, I will check it. The only thing that prevented it was my free time :)
FEDORA-EPEL-2023-ee6ec4994f has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-ee6ec4994f
FEDORA-EPEL-2023-ee6ec4994f has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-ee6ec4994f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2023-ee6ec4994f has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.