<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Patch in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/patch/m-p/2632921#M849894</link>
    <description>Hi:&lt;BR /&gt;&lt;BR /&gt;I have a diff -c patchfile but when applying it I get the following problem :&lt;BR /&gt;&lt;BR /&gt;# patch &amp;lt; ucd-hpux-patch &lt;BR /&gt;Hmm...  Looks like a new-style context diff to me...&lt;BR /&gt;The text leading up to this was:&lt;BR /&gt;--------------------------&lt;BR /&gt;|*** acconfig.h.SAV     Sat Oct  6 03:01:41 2001&lt;BR /&gt;|--- acconfig.h Fri Oct 12 17:55:13 2001&lt;BR /&gt;--------------------------&lt;BR /&gt;Patching file acconfig.h using Plan A...&lt;BR /&gt;Hunk #1 succeeded at 304.&lt;BR /&gt;Hunk #2 succeeded at 312.&lt;BR /&gt;Hmm...  The next patch looks like a new-style context diff to me...&lt;BR /&gt;The text leading up to this was:&lt;BR /&gt;--------------------------&lt;BR /&gt;|*** s/hpux.h.SAV       Tue Jul 27 02:06:47 1999&lt;BR /&gt;|--- s/hpux.h   Fri Nov  9 17:36:18 2001&lt;BR /&gt;--------------------------&lt;BR /&gt;File to patch: &lt;BR /&gt;&lt;BR /&gt;How can I resolve this?</description>
    <pubDate>Wed, 19 Dec 2001 09:28:13 GMT</pubDate>
    <dc:creator>Phil Daws_2</dc:creator>
    <dc:date>2001-12-19T09:28:13Z</dc:date>
    <item>
      <title>Patch</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/patch/m-p/2632921#M849894</link>
      <description>Hi:&lt;BR /&gt;&lt;BR /&gt;I have a diff -c patchfile but when applying it I get the following problem :&lt;BR /&gt;&lt;BR /&gt;# patch &amp;lt; ucd-hpux-patch &lt;BR /&gt;Hmm...  Looks like a new-style context diff to me...&lt;BR /&gt;The text leading up to this was:&lt;BR /&gt;--------------------------&lt;BR /&gt;|*** acconfig.h.SAV     Sat Oct  6 03:01:41 2001&lt;BR /&gt;|--- acconfig.h Fri Oct 12 17:55:13 2001&lt;BR /&gt;--------------------------&lt;BR /&gt;Patching file acconfig.h using Plan A...&lt;BR /&gt;Hunk #1 succeeded at 304.&lt;BR /&gt;Hunk #2 succeeded at 312.&lt;BR /&gt;Hmm...  The next patch looks like a new-style context diff to me...&lt;BR /&gt;The text leading up to this was:&lt;BR /&gt;--------------------------&lt;BR /&gt;|*** s/hpux.h.SAV       Tue Jul 27 02:06:47 1999&lt;BR /&gt;|--- s/hpux.h   Fri Nov  9 17:36:18 2001&lt;BR /&gt;--------------------------&lt;BR /&gt;File to patch: &lt;BR /&gt;&lt;BR /&gt;How can I resolve this?</description>
      <pubDate>Wed, 19 Dec 2001 09:28:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/patch/m-p/2632921#M849894</guid>
      <dc:creator>Phil Daws_2</dc:creator>
      <dc:date>2001-12-19T09:28:13Z</dc:date>
    </item>
    <item>
      <title>Re: Patch</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/patch/m-p/2632922#M849895</link>
      <description>As far as I can tell, those messages are purely informative - you will get them when using a context diff file (ie diff -c) as the patch file, but the files should still be changed correctly.&lt;BR /&gt;&lt;BR /&gt;Is the patch correctly modifying the files you expect it to?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Steve</description>
      <pubDate>Wed, 19 Dec 2001 11:34:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/patch/m-p/2632922#M849895</guid>
      <dc:creator>Steven Gillard_2</dc:creator>
      <dc:date>2001-12-19T11:34:47Z</dc:date>
    </item>
    <item>
      <title>Re: Patch</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/patch/m-p/2632923#M849896</link>
      <description>As long as you didn't receive a "failed" message, then you are OK.&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry</description>
      <pubDate>Wed, 19 Dec 2001 11:50:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/patch/m-p/2632923#M849896</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2001-12-19T11:50:18Z</dc:date>
    </item>
    <item>
      <title>Re: Patch</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/patch/m-p/2632924#M849897</link>
      <description>But why does it ask me to enter a filename? If I copy and paste the filename it works fine.&lt;BR /&gt;&lt;BR /&gt;P.</description>
      <pubDate>Wed, 19 Dec 2001 12:04:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/patch/m-p/2632924#M849897</guid>
      <dc:creator>Phil Daws_2</dc:creator>
      <dc:date>2001-12-19T12:04:48Z</dc:date>
    </item>
    <item>
      <title>Re: Patch</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/patch/m-p/2632925#M849898</link>
      <description>Hmmm, according to the patch man page:&lt;BR /&gt;&lt;BR /&gt;If no original file is specified on the command line, patch will try&lt;BR /&gt;      to figure out from the leading garbage what the name of the file to&lt;BR /&gt;      edit is.  In the header of a context diff, the filename is found from&lt;BR /&gt;      lines beginning with ``***'' or ``---'', with the shortest name of an&lt;BR /&gt;      existing file winning.&lt;BR /&gt;:&lt;BR /&gt;If no filename can be intuited from&lt;BR /&gt;      the leading garbage, you will be asked for the name of the file to&lt;BR /&gt;      patch.&lt;BR /&gt;&lt;BR /&gt;So it appears for some reason that patch can't find the s/hpux.h file, which is strange.  Can you run a tusc trace on the patch command to find out where its looking for this file?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Steve</description>
      <pubDate>Wed, 19 Dec 2001 12:46:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/patch/m-p/2632925#M849898</guid>
      <dc:creator>Steven Gillard_2</dc:creator>
      <dc:date>2001-12-19T12:46:36Z</dc:date>
    </item>
  </channel>
</rss>

