[MacPorts] #73369: inetutils: Install fails with non-root installation because it can't find grcp

[MacPorts]

#73369: inetutils: Install fails with non-root installation because it can't find
grcp
--------------------------+-------------------------
  Reporter:  AgilentGCMS  |      Owner:  Schamschula
      Type:  defect       |     Status:  assigned
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.11.6
Resolution:               |   Keywords:
      Port:  inetutils    |
--------------------------+-------------------------

Comment (by AgilentGCMS):

 Replying to [comment:3 ryandesign]:
 > What ''is'' unusual is that although MacPorts seems to be configured for
 the prefix /Users/sbasu1/packages/macports/sequoia, I also see references
 to /Users/sbasu1/packages/macports/sonoma in the log. Perhaps you have
 created some symlinks between your different prefixes.

 Oh, that's strange. Since macports needs to be built anew for each major
 release, I install into a new prefix each time. It __shouldn't__ look at
 {{{sonoma}}} now, but just to be safe I removed
 {{{/Users/sbasu1/packages/macports/sonoma}}} entirely and retried building
 after doing a {{{port clean inetutils}}}. This is now the error:
 {{{
 $ port install inetutils
 --->  Computing dependencies for inetutils
 --->  Fetching distfiles for inetutils
 --->  Verifying checksums for inetutils
 --->  Extracting inetutils
 Error: reinplace: couldn't execute
 "/Users/sbasu1/packages/macports/sonoma/libexec/gnubin/sed": no such file
 or directory
 Error: Failed to patch inetutils: reinplace sed(1) failed
 }}}
 I do not understand why it's looking for sed there. A simple {{{which
 sed}}} tells me
 {{{
 $ which sed
 /Users/sbasu1/packages/macports/sequoia/libexec/gnubin/sed
 }}}
 so it's very much in the path. Why would the build process look for a
 specific {{{sed}}} as opposed to one in {{{PATH}}}?

-- 
Ticket URL: <https://trac.macports.org/ticket/73369#comment:5>
MacPorts <https://www.macports.org/>
Ports system for macOS