jukoff@imram.net.com (Steve Jukoff) (04/27/91)
I un-sharred the kits and applied the patches immediately. Several files were consistently flagged as: File to patch: No file found--skip this patch? [n] (...I RESPONDED 'y'...) AS IN: Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |Index: perl_man.4 |Prereq: 3.0.1.12 |*** perl_man.4.old Sat Nov 10 02:33:50 1990 |--- perl_man.4 Sat Nov 10 02:34:09 1990 -------------------------- File to patch: No file found--skip this patch? [n] y Skipping patch... Hunk #1 ignored at 1. Hunk #2 ignored at 63. Hunk #3 ignored at 226. Hunk #4 ignored at 777. Hunk #5 ignored at 832. Hunk #6 ignored at 1093. 6 out of 6 hunks ignored--saving rejects to perl_man.4.rej The (repeatedly) "un-patchable" files were: config_h.SH perl_man.{1,2,3,4} t/op.s (...ONE TIME ONLY FOR THIS FILE...) What could I have done to have prevented this? What can I do to fix it? Why did it happen? The sequence of commands used to cause these errors were: foreach file ( perl.kit* ) sh $file end foreach pp ( perl-patch3.* ) patch -p -N < $pp end Any help appreciated. +----------------------------------------------------------+ | Steven Jukoff DDN: jukoff@net.com | | Phone: 415-780-5819 uucp: ames!unet!jukoff | +----------------------------------------------------------+