[chirp_devel] [PATCH 0 of 4] Make ft857 survive to run_tests

[David Ranch]

I tried the FT857 patches again with today's tip of tree and I still get 
a failure:

-----------------------------------------------
1.  Had to edit all patches to remove the a/ and b/ from the file paths

-----------------------------------------------
2. common patch worked ok per email "[chirp_devel] [PATCH 1 of 4] Add 
"valid_cross_modes" to    RadioFeatures"

patch -p0 < chirp-common.patch
patching file chirp/chirp_common.py
Hunk #1 succeeded at 546 (offset -2 lines).
Hunk #2 succeeded at 646 (offset -2 lines).
Hunk #3 succeeded at 765 (offset -2 lines).
patching file chirpui/memedit.py

-----------------------------------------------
3. FT857 patch didn't work per email "[chirp_devel] [PATCH 2 of 4] Set 
valid_cross_modes as needed"
I assume we have to have the file first but it doesn't apply cleanly 
either way

# patch -p0 < ft857.patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- chirp/ft857.py     Sat Jan 21 09:59:33 2012 +0100
|+++ chirp/ft857.py     Sat Jan 21 10:00:34 2012 +0100
--------------------------
File to patch: ^C

cp chirp/ft817.py chirp/ft857.py
# patch -p0 < ft857.patch
patching file chirp/ft857.py
Hunk #1 FAILED at 109.
1 out of 1 hunk FAILED -- saving rejects to file chirp/ft857.py.rej

----------------------------------------------
4. Patching runtests ok per email "[chirp_devel] [PATCH 4 of 4] Use 
valid_cross_modes during test"
 though it doesn't talk about HUNKS

patch -p0 < run-tests.patch
patching file tests/run_tests

----------------------------------------------
5. I did NOT apply the "merge" patch via email "[chirp_devel] [PATCH 3 
of 4] merge" from the recommendation of Dan


What am I missing?

--David


David Ranch wrote:
>
> Hey Dan, Marco,
>
> Ok, I'll try out the patches tonight assuming that I can get that RT 
> Systems cable working under the FTDI driver:
>
>    Dan: Two questions:
>
>        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?
>
>        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?
>
> --David

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20120124/a9c6e153/attachment-0001.html