Bug#444804: asterisk package does not build, relateg to libpri

Mon Oct 1 09:35:41 UTC 2007

On Mon, 2007-10-01 at 09:05 +0200, Tzafrir Cohen wrote:
> On Mon, Oct 01, 2007 at 08:12:18AM +0200, Rafal Pietrak wrote:
> > Package: asterisk
> > Version: asterisk-1.2.13~dfsg
> > 
> > I have encountered numerous problems building asterisk in current
> > testing (lenny) environment.
> > 
> > my system is maintained (for last 3-5 years) from local debian mirror:
> > -------------------/etc/apt-/source.list----------------------
> > deb file:/usr/src/debian lenny main contrib non-free
> > deb-src file:/usr/src/debian lenny main contrib non-free
> > 
> > deb http://security.debian.org/ lenny/updates main contrib non-free
> > deb-src http://security.debian.org/ lenny/updates main contrib non-free
> > -------------------------------------------------------------------
> > 
> > During build of asterisk-bristuff, symbol BRI_NETWORK does not resolve
> > (this behaviour started occuring after one of the updated in previous
> > 2-3 months).
> > 
> > The symbol does resolve, when dependencies are changed from
> > libpri-dev(depending on libpri1.2), to libpri-dev(depending on
> > libpri1.0) - a library deliberately pooled from 'unstable' bunch.
> 
> This should be resolved with the Unstable version of libpri. Compare:
> 
>   http://packages.debian.org/lenny/libpri-dev/i386/filelist
>   http://packages.debian.org/sid/libpri-dev/i386/filelist
> 
> Note the extra "bristuffed" files.
> 
> However you will then notice that the 1.4 bristuff libpri is
> incompatible with the Asterisk 1.2 bristuffed Asterisk . 
> 
> So I guess that this issue will only be resolved once Asterisk 1.4
> migrates to Lenny .

Not really. I don't think we have to wait. I've just successfully build
asterisk-1.2.13 with libpri1.0  installed:
--------------------------------------------------------------------
rafal at zorro$ dpkg -l libpri1.0
Desired=Unknown/Install/Remove/Purge/Hold
|Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
ii  libpri1.0      1.4.1-2        Primary Rate ISDN specification
library
-----------------------------------------------------------------------------

I only needed to apply a couple of (irrelevant to the libpri) patches
(see "rp-legacy" attachement).

I was wondering what incompatibilities exactly, you are refering to? The
build produced "asterisk-bristuff*.deb" - I cannot use it (and test it),
as I don't have any such hardware, but the package was created.

> > 
> > I have also tried to build asterisk-1.4.11~dfsg, which depends on
> > libpri1.0 (which itself looks inconsistant - the newer version of
> > asterisk (1.4.11) depends on libpri1.0, which 'looks older' then
> > libpri1.2 on which depends asterisl-1.2.13). 
> 
> libpri1.0 is libpri ver. 1.4.

Yes I have seen that. I was just refering to names "libpri1.2", v.s.
"libpri1.0" - which are kind of missleading as of which one is new, and
which one is old. But that's not an issue, really. Just confusing a bit.

> For the record, the imap voicemail feature of Asterisk requires
> libc-client 2004/2006 . The plain "libc-client" in Debian (even in Sid) is
> 2002.

OK. 

And for the record: on the *very*same* system that I've build
asterisk-1.2.13; I've successfully build asterisk-1.4.11 .... after I've
removed dependencies which I couldn't resolve (on lenny/testing) - it
looks like the "./configure" (run internally by dpkg-buildpackage)
correctly excluded missing fuctionality before the actual build. The
'unimportant' dependencies were: libiksemel-dev, libradiusclient-ng-dev,
freetds-dev, libsnmp-dev, libc-client2006j2-dev.

I only had to apply a small patch to disable access to libc-client (the 
patch is attached as "rp-imap")

In short, if minimal testing (which I myself cannot perform, as I dont
have any environment to make asterisk use libpri, or libradius, etc)
show, the dependency exclusion I did, do not introduce unrelated bugs,
I'd opt for a set of dependencies which *alow* a build under lenny, in
favour of a set of dependencies which explore all the new features (like
radius, snmp, imap access).

I hope you can copy my build results.
-- 
-R
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rp-legacy.dpatch
Type: application/x-shellscript
Size: 1706 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20071001/49f60dde/attachment.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rp-imap
Type: text/x-patch
Size: 676 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20071001/49f60dde/attachment-0001.bin 