Versions 1.0.1 of net-misc/asterisk, net-misc/zaptel, and net-libs/zapata were released on 30(?) September with bug fixes. Direct copy-over of 1.0.0 ebuilds and files works for me except zaptel-1.0.1-modulesd.diff, attached.
Created attachment 40956 [details, diff] zaptel-1.0.1-modulesd.diff zaptel-1.0.1-modulesd.diff
Could we please also have the issue with the pid file fixed? Gentoo # /etc/init.d/asterisk stop * Stopping asterisk PBX... No process in pidfile `/var/run/asterisk.pid' found running; none killed. Does the zaptel module use the correct 'make' option for kernel 2.6? "make linux26" in zaptel source directory instead of a simple "make"
Also, net-libs/libpri-1.0.1. I have USE=nopri, and hadn't tested it.
While this is open, I'm including a patch to zaptel from CVS that allows it to compile against kernel 2.6.9, and a zaptel-1.0.1.ebuild that includes kernel-mod changes from bug 68451.
Created attachment 42501 [details, diff] zaptel-1.0.1-skbuff.diff
Comment on attachment 42501 [details, diff] zaptel-1.0.1-skbuff.diff patch to zaptel for compilation against kernel 2.6.9
Created attachment 42502 [details] zaptel-1.0.1.ebuild ebuild for zaptel-1.0.1 which includes skbuff patch and changes from bug 68451
preparing inclusion
in cvs tree
Why doesn't portage want to update asterisk instead of just the side packages? asterisk # emerge -uDav asterisk These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild U ] sys-apps/texinfo-4.7-r1 [4.6] -build -debug +nls -static 1,385 kB [ebuild U ] sys-apps/groff-1.19.1-r1 [1.18.1-r4] -X* -debug 2,567 kB [ebuild U ] net-misc/zaptel-1.0.1 [1.0.0] -devfs26 289 kB [ebuild U ] media-sound/mpg123-0.59s-r6 [0.59s-r5] -3dnow -esd -mmx -nas -oss 6 kB [ebuild U ] net-libs/libpri-1.0.1 [1.0.0] 48 kB [ebuild U ] net-libs/zapata-1.0.1 [1.0.0] 72 kB # emerge -s asterisk * net-misc/asterisk Latest version available: 1.0.0 Latest version installed: 1.0.0
because stkn forgot to bump asterisk?
Great, thanks for adding Asterisk 1.0.1. One question, the USE flags have been changed. `nozaptel' is now zaptel. OK this is much clearer but now both useflags show up, nozaptel *and* zaptel. Guess this is not correct. Is this temporary and will it be corrected soon? Having both useflags is even more confusing I guess, I won't even try what will happen if you select both.
description for zaptel and pri has been fixed
Thanks!! Was just thinking of something else. Music On Hold in * is not working and this is because the latest version in portage of mpg123 doesn't work with * and the old version is not in portage. Ofcourse this is something that should be fixed in * but for the time being would it be an idea to put the portage version of mpg123 on 'BLOCKED' in portage and have the asterisk ebuild emerge the mpg123 version that is included in the * distro? Just my $0.02
Found 2 issues: The USE flag was changed for libpri. After removed libpri fropm the useflags I re-emerged asterisk and then removed the old libpri (I emerged asterisk 1.0.2 and removed libpri 1.0.1) asterisk didn't start. Guess this is a bug in the e-build. Then it seems that the init script of asterisk always shows OK at starting, even when asterisk doesn't start for some critical reason (like libpri missing). Wouldn't it be possible to have the init script report the actual status of asterisk?
