I've raised the severity of this bug because radiusclient-ng will hopefully not be part of jessie and therefore it will be mandatory to have asterisk linking against freeradius-client instead
Please let me know if I should go ahead and commit the fix in git myself I've already done this in reSIProcate - that means somebody can't install both asterisk and resiprocate on the same box until asterisk uses freeradius-client or until we find a way to support a concurrent install of both radius libs For reSIProcate, the following changes were necessary: - remove #include references to radiusclient-ng and replace with the equivalent #include "freeradius-client.h" - if errors about UINT4 appear, manually add the missing type: typedef uint32_t UINT4; - change the LDFLAGS to use -lfreeradius-client instead of -lradiusclient-ng - change debian/control to include Build-Depends: ..., libfreeradius-client-dev, ... Ideally upstream should make this change rather than doing it through Debian. reSIProcate upstream supports both client libs using a configure option. It may also be a good idea to split RADIUS into an asterisk-module-radius package so that people won't need any RADIUS client lib at all unless they want it -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
