[MacPorts] #70369: ruby33: fails to apply patches

[MacPorts]

#70369: ruby33: fails to apply patches
---------------------+----------------------
  Reporter:  dbl001  |      Owner:  kimuraw
      Type:  defect  |     Status:  assigned
  Priority:  Normal  |  Milestone:
 Component:  ports   |    Version:  2.9.3
Resolution:          |   Keywords:
      Port:  ruby33  |
---------------------+----------------------

Comment (by tglsfdc):

 Yeah, that patch is wrong, causing patch to complain "Reversed (or
 previously applied) patch detected!  Assume -R? [y]", and then it waits
 for a y/n response that won't be forthcoming since it's not actually
 attached to a terminal.

 BTW, not the fault of the ruby33 port I imagine, but: I lsof'd the stuck
 process before finding that error message, and noted that the process has
 a bunch of open file descriptors that patch(1) would have no use for,
 including some open https sockets.  Seems like some parent process(es) in
 the build procedure are being very sloppy about not marking their files
 F_CLOEXEC.  This could conceivably cause some real issues, for example if
 EOF on a socket isn't detected when it should be because random child
 processes are holding the file open.

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