Digium released a new version of asterisk. Some of the resolved issues are: - Allow users to specify a port for DUNDI peers. (Closes issue #17056. Reported, patched by klaus3000) - Decrease the module ref count in sip_hangup when SIP_DEFER_BYE_ON_TRANSFER is set. (Closes issue #16815. Reported, patched by rain) - If there is realtime configuration, it does not get re-read on reload unless the config file also changes. (Closes issue #16982. Reported, patched by dmitri) - Send AgentComplete manager event for attended transfers. (Closes issue #16819. Reported, patched by elbriga) - Correct manager variable 'EventList' case. (Closes issue #17520. Reported, patched by kobaz) - In addition, changes to res_timing_pthread that should make it more stable have also been implemented. What I've changed on the ebuild: - "${FILESDIR}/1.6.2/${P}-gsm-pic.patch" + "${FILESDIR}/1.6.2/${PN}-1.6.2.9-gsm-pic.patch" Compiles fine and smoothly.
Created attachment 240083 [details] ebuild for asterisk-1.6.2.10
Hello Oliver. Thank you for the asterisk ebuilds. By the way, are you planning to release asterisk 1.8 beta ebuilds?
(In reply to comment #2) > [...] By the way, are you planning to release asterisk 1.8 beta ebuilds? I silently hoped that somebody starts to ask ;) Well, let's think about it together: What's to do? My thoughts for the neccessary steps are (so far): Step one: base ebuild. Builds a plain (unpatched) and working asterisk.1.8b Step two: check whether our (Gentoo-)patches are nedded anymore Step three: check/review the remaining patches - how/where to apply Step four: ebuild. Builds a patched and working asterisk.1.8b [...] Last step: Stable ebuild when patching/stabilizing done and asterisk-1.8 leaves beta-status I'll give any comments and suggestions a warm welcome :)
> Step one: base ebuild. Builds a plain (unpatched) and working asterisk.1.8b Well that would be indeed the first step. :-) I don't know nothing about the patches integrated in the gentoo ebuild. So i can't comment on that. But i can take a look if you need help. cheers Thomas
(In reply to comment #2) > By the way, are you planning to release asterisk 1.8 beta ebuilds? Gentlemen, this is not your personal communications centre. Please use e-mail in the future. Asterisk 1.8 will not be in the portage tree until a point release (1.8.0; 1.8.0.0; 1.8.0.0.0; whatever they go with) is available. QA in the main Asterisk source is a point where I'm barely comfortable packaging it in the first place, let's not make it worse by packaging software that they feel is not ready for the general public.
Many thanks Oliver, this is in the tree now: +*asterisk-1.6.2.10 (26 Jul 2010) + + 26 Jul 2010; <chainsaw@gentoo.org> +asterisk-1.6.2.10.ebuild: + Bugfix release, closes bug #329771 by Oliver Jaksch. + *asterisk-1.6.2.9-r1 (19 Jul 2010)
