Description of problem: I am working on packaging ffgtk, a solution for controlling the FRITZ!Box or compatible router with Linux. It offers a rich feature list, including caller monitor and fax support. This requires a remote-capi. Capi20.new is now avaialable in the upstream isdn4k-utils. This version offers support for the traditional local capi as well as remote capi (based on plugins). According to https://bugs.launchpad.net/ubuntu/+source/isdnutils/+bug/420918 suse ships the new capi already for some time. The capi4linux rpm for Suse indeed includes the plugins. Could we please update as well? If that helps, I can work on the required changes (I already have spec file that works, but should be cleaned up a bit). Version-Release number of selected component (if applicable): Current CVS of isdn4k-utils How reproducible: NA Steps to Reproduce: NA Actual results: Expected results: Additional info:
Created attachment 395243 [details] This spec file needs some change to the Makefile, to be cleaned up
Created attachment 407693 [details] tar file with updated spec file and some aux. files
I have added a more complete spec file, based on the -68 version of isdn4k-utils. Will it be feasible to include these changes? If not, I can package the capi separately and set isdn4k-utils as conflicting, if you prefer so
isdn4k-utils-3_2-70_fc14 is built in rawhide. It now supports the capi20.new.
Hi Ngo I rebuilt the -70 RPM on my F12 and found a few small issues: 1) plugins are not loaded due to the fact that libcapi20.so.3 only looks for .so plugins. Patch attached 2) I forgot to own %{_libdir}/capi (patch to spec file attached) 3) a small addition to the template /etc/capi20.conf: added portnumber
Created attachment 412445 [details] Updated capi20.conf
Created attachment 412446 [details] Patch to the spec file, own libdir/capi, additional patch21 for plugin detection
Created attachment 412448 [details] Patch to capi20.new, so it detects the .so.x libs, rather than the .so
it's fixed in isdn4k-utils-3_2-71_fc14. Louis, could you please test it? thanks
Got the -71 from koji and rebuilt it for my F12 and tested the result. Works now as expected. thanks for the quick reponse!
isdn4k-utils-3.2-71.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/isdn4k-utils-3.2-71.fc13
isdn4k-utils-3.2-71.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/isdn4k-utils-3.2-71.fc12
isdn4k-utils-3.2-71.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update isdn4k-utils'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/isdn4k-utils-3.2-71.fc12
isdn4k-utils-3.2-71.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update isdn4k-utils'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/isdn4k-utils-3.2-71.fc13
isdn4k-utils-3.2-71.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
isdn4k-utils-3.2-71.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.