this software is definitely needed as an included rpm. Routers from AVM are used very often - I think it is the leading manufactorer in Germany. ffgtk is supported by AVM. ffgtk is in the official repository of opensuse and fedora and there is a running repository for debian systems (with derivates) and it runs very well on all this systems.
Target Milestone: --- => Mageia 2
Source RPM: ffgtk => ffgtk 0.8.1, libcapi3.0.5a
Version: Cauldron => 2
Status: NEW => ASSIGNEDCC: (none) => doktor5000Version: 2 => CauldronAssignee: bugsquad => doktor5000Target Milestone: Mageia 2 => ---Source RPM: ffgtk 0.8.1, libcapi3.0.5a => (none)
CC: (none) => post4aws
I agree as well that this rpm is in need. I tried to build it m own but i couldnt get a capi20=> working and this is in need.
CC: (none) => timo
CC: (none) => ueberall
No need to get "capi20=> working" whatever you mean by that ... We already have isdn4k-utils-devel which provides this, but it doesn't contain a pkg-config .pc file so it is not detected, as can be seen: configure:12109: $PKG_CONFIG --exists --print-errors "capi20" Package capi20 was not found in the pkg-config search path. Perhaps you should add the directory containing `capi20.pc' to the PKG_CONFIG_PATH environment variable No package 'capi20' found So if noone volunteers to take maintainership and makes the necessary changes for isdn4k-utils i'm afraid i can't add ffgtk. And i can't take on more packages, sorry.
Component: New RPM package request => Installer
not good news. As it is, wait and see and use as long as any other distribution. I think I look again at LMDE ...
CC: post4aws => (none)
Reassigning to bugsquad as we need an updated isdn4k-utils package first (which is also unmaintained, so chances are pretty small this will ever get fixed).
Status: ASSIGNED => NEWAssignee: doktor5000 => bugsquad
Note that for telephony, using the SIP-connection that is also built-into most FritzBox routers probably is easier than dealing with capi (I only know of one capi-soft-phone and that is ant-phone (not packaged in mageia) And for using just the capi via tcp, mISDN /libcapi20 can do the trick (while isdn4k-utils themselves are no longer necessary, the capi20 that is part of it needs an update). Finally, another solution to use remote-capi is to use fbrcapi - but as that is also not packaged, more or less the same situation. Priority should be to get updated capi20 and matching mISDN user-space capi (that then also offers a software-dsp to enable faxing) & kernel-modules into mageia. I assume the tool just needs a working capi20, so that would be covered as well. isdn4k-utils/capi20 as shipped with mageia 3 really is outdated (still want capifs that doesn't exist for ages, and the capi-udev rules are also not working.. ISDN is dying....
CC: (none) => lohmaier+mageia
Depends on: (none) => 10228
You may also want to have a look at Bug #14276: "Please provide libcapi20-3 (updated for modular design supporting rcapi/remote-capi)"
CC: (none) => h.goebel
Please next time also fill the See Also field: https://bugs.mageia.org/page.cgi?id=fields.html#see_also
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=14276
Unclear why this is reported against installer. Please do review that part.
Keywords: (none) => NEEDINFO
(In reply to Dick Gevers from comment #8) > Unclear why this is reported against installer. Please do review that part. Installer is definitively wrong. I set it to "new package request"
Component: Installer => New RPM package request
Keywords: NEEDINFO => (none)CC: (none) => marja11
(In reply to Florian Hubold from comment #4) > Reassigning to bugsquad as we need an updated isdn4k-utils package first > (which is also unmaintained, so chances are pretty small this will ever get > fixed). isdn4k-utils still has the same version as in Mga1. Besides, there hasn't been a new upstream isdn4k-utils snapshot since 27-11-07, and the ffgtk link is now dead. IIUC, it is now replaced with "Roger-router". I didn't manage to find the source code or license. Anyway, closing this request for isdn4k-utils as wontfix.
Status: NEW => RESOLVEDResolution: (none) => WONTFIX