<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="-1"><br>
I tried the FT857 patches again with today's tip of tree and I still
get a failure:<br>
<br>
-----------------------------------------------<br>
1. Had to edit all patches to remove the a/ and b/ from the file paths<br>
<br>
-----------------------------------------------<br>
2. common patch worked ok per email "[chirp_devel] [PATCH 1 of 4] Add
"valid_cross_modes" to RadioFeatures"<br>
<br>
patch -p0 < chirp-common.patch<br>
patching file chirp/chirp_common.py<br>
Hunk #1 succeeded at 546 (offset -2 lines).<br>
Hunk #2 succeeded at 646 (offset -2 lines).<br>
Hunk #3 succeeded at 765 (offset -2 lines).<br>
patching file chirpui/memedit.py<br>
<br>
-----------------------------------------------<br>
3. FT857 patch didn't work per email "[chirp_devel] [PATCH 2 of 4] Set
valid_cross_modes as needed"<br>
I assume we have to have the file first but it doesn't apply cleanly
either way<br>
<br>
# patch -p0 < ft857.patch<br>
can't find file to patch at input line 3<br>
Perhaps you used the wrong -p or --strip option?<br>
The text leading up to this was:<br>
--------------------------<br>
|--- chirp/ft857.py Sat Jan 21 09:59:33 2012 +0100<br>
|+++ chirp/ft857.py Sat Jan 21 10:00:34 2012 +0100<br>
--------------------------<br>
File to patch: ^C<br>
<br>
cp chirp/ft817.py chirp/ft857.py<br>
# patch -p0 < ft857.patch<br>
patching file chirp/ft857.py<br>
Hunk #1 FAILED at 109.<br>
1 out of 1 hunk FAILED -- saving rejects to file chirp/ft857.py.rej<br>
<br>
----------------------------------------------<br>
4. Patching runtests ok per email "[chirp_devel] [PATCH 4 of 4] Use
valid_cross_modes during test"<br>
though it doesn't talk about HUNKS<br>
<br>
patch -p0 < run-tests.patch<br>
patching file tests/run_tests<br>
<br>
</font><font size="-1">----------------------------------------------<br>
</font>5. I did NOT apply the "merge" patch via email "[chirp_devel]
[PATCH 3 of 4] merge" from the recommendation of Dan<br>
<br>
<br>
What am I missing?<br>
<br>
--David<br>
<br>
<br>
David Ranch wrote:
<blockquote cite="mid:4F1F36DC.7060304@trinnet.net" type="cite">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<br>
Hey Dan, Marco,<br>
<br>
Ok, I'll try out the patches tonight assuming that I can get that RT
Systems cable working under the FTDI driver:<br>
<br>
Dan: Two questions:<br>
<br>
1. To test the RT cable, do you know of a simple text string to
send to the 857 to see if it's properly receiving and I get a known
response back?<br>
<br>
2. I'm assuming I can download the newest nightly snapshot and
apply Marco's emailed patches (except his "merge" patch) or do I need
to use a different version of Chirp?<br>
<br>
--David<br>
</blockquote>
<br>
</body>
</html>