Probably you did nothing wrong. It just means that the particular "hunk" in the patch is already in the source code. Perhaps Red Hat applied pieces of it, but not all of it. Perhaps pieces of it got accepted by Marcello, etc., etc. If it goes on (and you do _not_ revert those hunks), I would say you're ready to try to rebuild it.
Mark Post -----Original Message----- From: Scully, William P [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 06, 2004 12:51 PM To: [EMAIL PROTECTED] Subject: Patch Fails on RH 3.0 I'm trying to apply the timer-patch on top of Red Hat Enterprise Linux 3.0 AS. I find the patch command is not applying the patches "perfectly". For example: # cd /usr/src # ln -s linux-2.4 linux-2.4.21 # patch -p0 --dry-run < linux-2.4.21-s390-june2003.diff patching file linux-2.4.21/Documentation/Configure.help Hunk #1 succeeded at 6057 with fuzz 2 (offset 398 lines). Hunk #2 succeeded at 7310 with fuzz 2 (offset 77 lines). Hunk #3 succeeded at 24904 (offset 1049 lines). Hunk #4 succeeded at 23962 with fuzz 2 (offset 86 lines). Hunk #5 succeeded at 27712 with fuzz 2 (offset 1170 lines). patching file linux-2.4.21/Documentation/devices.txt Reversed (or previously applied) patch detected! Assume -R? [n] If I respond "no", this process continues with various hunks applied successfully and many "reversed" patches detected. I find it hard to believe that IBM reversed the patches. So what did I do wrong here? William P. Scully Senior Systems Programmer Computer Associates International, Inc 2291 Wood Oak Drive Unit 5-29C Herndon, Virginia 20171 Work: +1 703 708 3976 [EMAIL PROTECTED]
