sed behaving badly?

Dag-ErlingSmørgrav des at
Thu Nov 6 11:59:46 PST 2003

walt <wa1ter at> writes:
> 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/
> sed: /usr/ports/lang/python/work/Python-2.3.2/Lib/ 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.

I introduced a bug a couple of days ago, and fixed it a few hours
later.  Just update and rebuild sed.

Dag-Erling Smørgrav - des at

More information about the freebsd-current mailing list