It seems highly likely that it would be in cvs by now. I would not use the file produced by this patch run without first finding out why hunk #12 succeeded. One possible cause would be that the original hunk has been reversed in cvs for some good reason. Note that I usually use this safe and sane test when working with modified sources from debian or another distro. Sometimes the package maintainers apply some patches to the upstream source but they don't always clearly document that. Anyway, I used this method to patch and build * for debian. It was not the cvs version but it did the job(see if broadvoice will work). I will probably create a debian package set from cvs next but I need to have a 1.03 machine running alongside the cvs machine in order to file truly meaningful bug reports :)

Dalon Westergreen wrote:

Hi all,

http://edvina.net/broadvoice/patch.shtml

this site claims that the patch was incorporated into the * cvs tree
as of 12/12/2004

--dalon

On Tue, 18 Jan 2005 13:15:01 -0800, David Shaw <[EMAIL PROTECTED]> wrote:


I ran a test patch like Paul said.

[EMAIL PROTECTED] test]# patch chan_sip.c broadvoicesip2.txt
patching file chan_sip.c
Hunk #1 FAILED at 231.
Hunk #2 FAILED at 323.
Hunk #3 FAILED at 494.
Hunk #4 FAILED at 502.
Hunk #5 FAILED at 3738.
Hunk #6 FAILED at 4049.
Hunk #7 FAILED at 4071.
Hunk #8 FAILED at 4091.
Hunk #9 FAILED at 4123.
Hunk #10 FAILED at 4165.
Hunk #11 FAILED at 4181.
Hunk #12 succeeded at 4309 (offset 105 lines).
Hunk #13 FAILED at 4320.
Hunk #14 FAILED at 4335.
Hunk #15 FAILED at 4450.
Hunk #16 FAILED at 6402.
Hunk #17 FAILED at 6526.
Hunk #18 FAILED at 6939.
Hunk #19 FAILED at 6974.
18 out of 19 hunks FAILED -- saving rejects to file chan_sip.c.rej
[EMAIL PROTECTED] test]#

I'm guessing I have a patched verison of Asterisk?
I tested this on a fresh CVS install.

Thanks, David

----- Original Message -----
From: "Paul" <[EMAIL PROTECTED]>
To: "Asterisk Users Mailing List - Non-Commercial Discussion"
<[email protected]>
Sent: Tuesday, January 18, 2005 10:31 AM
Subject: Re: [Asterisk-Users] Broadvoice Patch Error {Scanned}



There is a sane and safe way to do this when you are not sure if the
patches are already in:

1 - create a new "scratch" directory

2 - copy the patch and chan_sip.c to that directory

3 - patch chan_sip.c broadvoicesip2.txt

If you have the right(unpatched) version of the c source you will only
get messages about hunks suceeding.

ls -al should now yield something like this:

drwxr-xr-x 2 sysadmin sysadmin 4096 2005-01-13 00:42 .
drwxr-xr-x 16 sysadmin sysadmin 4096 2005-01-17 23:38 ..
-rw-r--r-- 1 sysadmin sysadmin 15116 2004-12-12 06:02


broadvoicesip2.txt


-rw-r--r--   1 sysadmin sysadmin 291894 2005-01-13 00:42 chan_sip.c
-rw-r--r--   1 sysadmin sysadmin 287963 2004-10-25 13:57 chan_sip.c.orig

David Shaw wrote:



Hello, I'm trying to patch Asterisk for uses wth BroadVoice. I'm
running [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>.

Here is the Error:
[EMAIL PROTECTED] asterisk]# patch < broadvoicesip2.txt
can't find file to patch at input line 8
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|Index: channels/chan_sip.c
|===================================================================
|RCS file: /usr/cvsroot/asterisk/channels/chan_sip.c,v
|retrieving revision 1.510.2.23
|diff -u -r1.510.2.23 chan_sip.c
|--- channels/chan_sip.c 26 Nov 2004 01:54:11 -0000


1.510.2.23


|+++ channels/chan_sip.c        12 Dec 2004 10:57:45 -0000
--------------------------
File to patch:
[EMAIL PROTECTED] asterisk]#

What file should I patch???

Thanks, David


-- This message has been scanned for viruses and dangerous content by *KE6UPI* <http://ke6upi.com/>, and is believed to be clean. MailScanner thanks transtec Computers <http://www.transtec.co.uk/> for their support. Plase contact Support at KE6UPI <[EMAIL PROTECTED]> if you have questions about this email.

------------------------------------------------------------------------

_______________________________________________
Asterisk-Users mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
 http://lists.digium.com/mailman/listinfo/asterisk-users



_______________________________________________
Asterisk-Users mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users

--
This message has been scanned for viruses and
dangerous content by KE6UPI, and is
believed to be clean.
KE6UPI thanks MailScanner for their support.
Please contact [EMAIL PROTECTED] if you have
questions about this email.



--
This message has been scanned for viruses and
dangerous content by KE6UPI, and is
believed to be clean.
KE6UPI thanks MailScanner for their support.
Please contact [EMAIL PROTECTED] if you have
questions about this email.

_______________________________________________
Asterisk-Users mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users



_______________________________________________
Asterisk-Users mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users



_______________________________________________ Asterisk-Users mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to