Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#5517 closed bug (fixed)

bash: sed: command not found

Reported by: HaikuBot Owned by: nobody
Priority: normal Milestone: R1/alpha2
Component: - General Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All


Rev.35721 if launch Terminal you will get:

Welcome to the Haiku shell.

bash: sed: command not found

Change History (9)

comment:1 by mmadia, 10 years ago

What type of image is this: default, self-built, @alpha-*, @nightly-*, ... ?

comment:2 by aldeck, 10 years ago

Pretty much anyone with a custom build profile will experience the problem since hrev35705 (cf. my comment in the commit list). We should either remove the dependency on sed or make sed not optional.

comment:3 by idefix, 10 years ago

As a consequence of this, the installoptionalpackage script stopped working. (Tested in live-cd mode with

comment:4 by scottmc, 10 years ago

for a short term fix you can use this one:


then extract it to /boot

comment:5 by HaikuBot, 10 years ago

Adding this in UserBuildConfig fix this issue:

AddOptionalHaikuImagePackages BasicCommandLineTools ;

comment:6 by mmadia, 10 years ago

Can you retest with hrev35829? The optional package sed is now included in default images.

comment:7 by HaikuBot, 10 years ago

hrev35860 All fine. So you can close ticket. Thanks.

comment:8 by mmadia, 10 years ago

Resolution: fixed
Status: newclosed

Thanks for confirming!

comment:9 by scottmc, 10 years ago

I'm not so sure this is actually fixed yet. On a new install libtoolize is still complaining that it can't find /bin/sed I either have to symlink it, or install the package which has sed in /boot/system in order to get libtoolize to work correctly.

Note: See TracTickets for help on using tickets.