sed behaving badly?

From: walt <wa1ter_at_myrealbox.com>
Date: Tue, 04 Nov 2003 06:39:14 -0800
I got this nonsensical error from sed while trying to update python:

/usr/bin/sed -i.bak -e  's,/usr/doc/python-docs-,/usr/local/share/doc/python,g'  /usr/ports/lang/python/work/Python-2.3.2/Lib/pydoc.py
sed: /usr/ports/lang/python/work/Python-2.3.2/Lib/pydoc.py: No such file or directory

But the file DOES exist, and furthermore the same port compiles just fine on
-CURRENT from November 1.  I think the recent changes to sed may have broken
something, but I don't know how, exactly.

Anyone else seeing this problem?
Received on Tue Nov 04 2003 - 10:42:33 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:27 UTC