Thanks for the info, this is helpful :)<br><br><br><br><div><span class="gmail_quote">On 10/4/07, <b class="gmail_sendername">Faidon Liambotis</b> <<a href="mailto:paravoid@debian.org">paravoid@debian.org</a>> wrote:
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hello,<br>This is a update on the current status of Asterisk in Debian.<br>Apologies for the really long mail, it is targetted both to users and
<br>maintainers :)<br><br>I'm Ccing asterisk-users as a one-time thing; users that are interested<br>can subscribe to our list[1] for updates to prevent noise on a<br>non-Debian list. Please Cc pkg-voip-maintainer on replies.
<br><br>1: <a href="http://lists.alioth.debian.org/mailman/listinfo/pkg-voip-maintainers">http://lists.alioth.debian.org/mailman/listinfo/pkg-voip-maintainers</a><br><br>sarge/etch status<br>-----------------<br>About a month ago, I fixed all the long-standing knownn vulnerabilities
<br>in both sarge/oldstable (1.0.7) and etch/stable (1.2.12).<br>The updates are present <a href="http://security.debian.org">security.debian.org</a> a Advisory has been released<br>(DSA-1358[1]), thanks to Debian's Security Team.
<br><br>These updates are fixing CVE-2007-1306, CVE-2007-1561, CVE-2007-2294,<br>CVE-2007-2297, CVE-2007-2488, CVE-2007-3762, CVE-2007-3763 and<br>CVE-2007-3764 (...).<br><br>1: <a href="http://www.debian.org/security/2007/dsa-1358">
http://www.debian.org/security/2007/dsa-1358</a><br><br>lenny status<br>------------<br>1:1.4.11~dfsg-4 has been recently uploaded to unstable.<br>The previously mentioned block by the openh323 dependency which<br>currently fails to build in unstable (binutils bug: #440015) has been
<br>workaround-ed (by having less strict shlibs in openh323)<br><br>From our POV, it's a good candidate for lenny/testing. However:<br> - it depends on perl and net-snmp versions that are not present in<br> testing and are not in a shape to be there; we'll need new versions
<br> from the respective teams.<br> - asterisk needs to go together with yate because of a shared libpri<br> dependency. However yate is being blocked[2] by gtk+2.0.<br> - more importantly, asterisk produces an Internal Compiler Error of GCC
<br> 4.2 on hppa (#445336). Until it builds successfully there, it cannot<br> migrate to testing.<br><br>1: <a href="http://bjorn.haxx.se/debian/testing.pl?package=asterisk">http://bjorn.haxx.se/debian/testing.pl?package=asterisk
</a><br>2: <a href="http://bjorn.haxx.se/debian/testing.pl?package=yate">http://bjorn.haxx.se/debian/testing.pl?package=yate</a><br><br>1.4.12<br>------<br>Digium released 1.4.12 the day before yesterday. I have committed all
<br>the changes needed and we are now up to date.<br>Fortunately, many of our fixes that I reported upstream have been<br>merged. I have manually ported bristuff 0.4.0-test4 to 1.4.12; it needed<br>many changes compared to the previous upstream updates.
<br>I will forward my changes to kapejod so that he can hopefully release a<br>new version.<br><br>supplementary packages<br>----------------------<br>* asterisk-addons (-mp3, -mysql, -ooh323c) are finally present in Debian
<br> and should be ready to migrate to lenny after Asterisk does. Digium<br> released a new version along with 1.4.12 and I will update this ASAP.<br>* asterisk-chan-capi, asterisk-spandsp-plugins, asterisk-oh323 had<br>
recents uploads and all are in a good shape.<br>* I am going to drop rate-engine from the archive (#444712) since it has<br> no users, it wasn't released with etch, has open bugs for a really<br> long time and is unmaintained by upstream.
<br>* I tried compiling chan_misdn together with the mISDN maintainer (Simon<br> Richter) and failed because of an mISDN API mismatch.<br> Need to take another look.<br>* asterisk-gui needs to be uploaded; Tzafrir?<br>* are we going to upload ARI? If not, we should drop it from our SVN.
<br>* zaptel is in a good status and it's the only package from the suite<br> that is migrating to testing. Things TODO that come to mind are: a)<br> fixing a bug which results in /lib/modules/2.6.foo/modules.* files in
<br> amd64 and b) evaluate a switch to OSLEC as the default echo<br> cancellator. Tzafrir is doing an excellent job on maintaining this<br> package by himself :)<br>* Right now, we are shipping asterisk-sounds-main which is the "main"
<br> asterisk sounds in English in GSM format -- exactly as shipped in the<br> original tarball by Digium. Kilian, Tzafrir and me were pondering on<br> the idea of shipping separately all sounds as shipped by Digium in all
<br> formats (besides WAV), each in a separate package. This should serve<br> our users better but has an obvious problem of size. This is not<br> decided yet.<br><br>ABI issues<br>----------<br>Most -if not all- of these plugins build-depend on asterisk-dev
i.e. use<br>Asterisk's development headers. These headers are tied to the ABI and<br>this can only be expressed in dependencies manually.<br>asterisk-chan-capi was compiled with 1.2 asterisk-dev, had a >= 1.2<br>dependency but segfaults on
1.4 (#441237). There are currently no<br>similar problems that I know of.<br>However, we should expect more of these when we transition to 1.6 which<br>will most probably have a different ABI.<br><br>I'm leaning towards a solution:
<br> * Add a "Provides: asterisk-1.4" to asterisk.<br> * Replace "Depends: asterisk (>= 1.4.0)" (or similar) with "Depends:<br> asterisk-1.4" on all external modules.<br>This should help in *breaking*, dpkg-wise, the modules when a new
<br>version is uploaded which in turn will prevent a new version from<br>entering testing until all plugins are recompiled.<br><br>pushing our work upstream<br>-------------------------<br>On the 1.4.11-1.4.12 cycle, I tried pushing all of our patches to
<br>Digium's BTS (mantis). This has worked well since they're quite<br>responsive (contrary to our secondary upstream, Klaus-Peter Junghanns...).<br>I have began adding comments to all of our patches with either:<br>
* the Digium ticket number<br> * a temporary "should be forwarded upstream" tag<br> * what's wrong with a patch that makes it unsuitable for forwarding it<br>I find this a good "policy" that we should probably adopt for all
<br>pkg-voip's packages.<br><br>getting upstream's work back :)<br>-------------------------------<br>Digium is following an old-style Linux release model (odd-even<br>versions). Unfortunately, this leads to long delays between interesting
<br>features or non-trivial fixes.<br>This, combined with our long release cycles can result in *huge* delays.<br>For example, we shipped etch in April with Asterisk 1.2 and Asterisk 1.4<br>was feature-frozen for already 3 months at that point.
<br><br>We are currently shipping func_devstate (it is maintained for 1.4<br>out-of-tree by its author, Russell Bryant) and I have just commited a<br>backport of the libcap patch so that asterisk can set the ToS of IP.<br>
<br>I have also backported chan_mobile for asterisk-addons; I'm going to buy<br>a Bluetooth adapter and test it before uploading, however.<br><br>Backporting stuff from trunk may be error-prone and is not easy to draw
<br>a line of which stuff we should backport.<br>I'm open to suggestions on other modules that may have sense in backporting.<br><br>bugs<br>----<br>Our bug count is currently:<br>* Status<br> - 8 Outstanding<br> - 3 Forwarded
<br>* Severity<br> - 2 Important bugs<br> - 2 Normal bugs<br> - 7 Wishlist items<br>This is probably the lowest bug count in ages, partly because testing<br>has still 1.2.<br><br>I have begun forwarding upstream bugs to mantis. This has already been
<br>proven fruitful: #353227 is open for 1 year and 230 days; I forwarded it<br>on 2007-09-21 and got a proposed patch back on the very next day!<br><br>I'm expecting more bugs when asterisk migrates in testing; we can only
<br>cope up with them if we tag them properly and forward the upstream ones<br>quickly.<br><br>helping out<br>-----------<br>You can help by testing our packages and reporting bugs if found.<br>Besides frequent uploads to unstable, there is buildserver that has
<br>revision snapshots for etch, lenny, sid[1] and edgy, feisty and gutsy[2]<br><br>Any feedback is welcome; suggestions on how to improve the packaging,<br>bug reports, backport requests, suggested out-of-tree patches for
<br>inclusion etc.<br><br>1: <a href="http://pkg-voip.buildserver.net/debian/">http://pkg-voip.buildserver.net/debian/</a><br>2: <a href="http://pkg-voip.buildserver.net/ubuntu/">http://pkg-voip.buildserver.net/ubuntu/</a>
<br>(apt repositories)<br><br>Best regards,<br>Faidon<br><br>_______________________________________________<br>--Bandwidth and Colocation Provided by <a href="http://www.api-digital.com--">http://www.api-digital.com--</a>
<br><br>asterisk-users mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br></blockquote>
</div><br><br clear="all"><br>-- <br> With Best Regards,<br>***************************<br> Sarfaraz Chougule<br> <a href="http://www.sarfu.co.in">http://www.sarfu.co.in</a><br>***************************