Darrick Hartman wrote: > Look at the asterisk.mk file. You'll need to put your patch file in the > packages/asterisk dir with an appropriate name. > > I can't look at the patch clearly on my bb but I will take a look at it when > I get back home. I JUST today tagged 0.6.5 and started building the release > files. Does this patch apply to 1.4.24.1? > It applies to builds from 1.4.22 onwards - which were apparently changed to make the channels more sensitive to alarms (though I have not diffed the revisions). The status of this patch is currently only "ready-for-review" but things are bad enough that I will take it as it is.
I will review the .mk file packages structure and try to fold it in. Thanks Mart > Darrick > ------Original Message------ > From: Martin Rogers > To: AstLinux Users Mailing List > ReplyTo: AstLinux Users Mailing List > Subject: [Astlinux-users] Patching Astlinux - best practice > Sent: Apr 14, 2009 5:57 PM > > Hi. > > I am running 0.6.4 in a net5501 with a TDM400p with two FXO cards. > Occaisionally one of the PSTN lines (always the same one) goes > unavailable, usually overnight. I have tried swapping FXO cards and > TDM400 daughter board slots to no avail - the same line still goes down > every now an then. The problem seems to be that ZAP/Dahdi cannot cope > with some alarm state which occaisonally occurs on one of the two lines. > > I noticed that something very very similar had been reported at digium : > > http://bugs.digium.com/view.php?id=14163 > > with a proposed patch : > wget 'http://bugs.digium.com/file_download.php?file_id=21096&type=bug' > -O - | patch -p0 > > I set up a CentOS build machine checked out and compiled up the trunk > version of Astlinux for the net5501. > I ran the above patch and it changed chan_dahdi.c as expected. > > However. If I run then 'make' it does not detect the change and > recompile the file. What is accepted best practise in this environment > for folding this change in to a local patched version of astlinux. It > would be a shame to have to 'make clean' the entire build and start from > scratch. > > Any suggestions ? > thanks > Mart > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > High Quality Requirements in a Collaborative Environment. > Download a free trial of Rational Requirements Composer Now! > http://p.sf.net/sfu/www-ibm-com > _______________________________________________ > Astlinux-users mailing list > Astlinux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pay...@krisk.org. > > > Sent from my BlackBerry® wireless device from U.S. Cellular > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > High Quality Requirements in a Collaborative Environment. > Download a free trial of Rational Requirements Composer Now! > http://p.sf.net/sfu/www-ibm-com > _______________________________________________ > Astlinux-users mailing list > Astlinux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pay...@krisk.org. > > ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
