Date: Thu, 06 Nov 2003 20:59:36 +0100 From: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) To: walt <wa1ter@myrealbox.com> Cc: freebsd-current@freebsd.org Subject: Re: sed behaving badly? Message-ID: <xzphe1he09j.fsf@dwp.des.no> In-Reply-To: <3FA7BA12.7060702@myrealbox.com> (wa1ter@myrealbox.com's message of "Tue, 04 Nov 2003 06:39:14 -0800") References: <3FA7BA12.7060702@myrealbox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
walt <wa1ter@myrealbox.com> 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/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. I introduced a bug a couple of days ago, and fixed it a few hours later. Just update and rebuild sed. DES -- Dag-Erling Smørgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzphe1he09j.fsf>