Opened 9 years ago

Closed 9 years ago

Last modified 9 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

Description

Rev.35721 if launch Terminal you will get:

Welcome to the Haiku shell.

bash: sed: command not found
~/Desktop> 

Change History (9)

comment:1 Changed 9 years ago by mmadia

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

comment:2 Changed 9 years ago by aldeck

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 Changed 9 years ago by idefix

As a consequence of this, the installoptionalpackage script stopped working. (Tested in live-cd mode with haiku-nightly-r35752-x86gcc2hybrid-cd.zip.)

comment:4 Changed 9 years ago by scottmc

for a short term fix you can use this one: http://www.haiku-ports.de/packages/sys-apps/sed/sed-4.2.1-x86-gcc2-2010-03-09.zip

wget http://www.haiku-ports.de/packages/sys-apps/sed/sed-4.2.1-x86-gcc2-2010-03-09.zip

then extract it to /boot

comment:5 Changed 9 years ago by HaikuBot

Adding this in UserBuildConfig fix this issue:

AddOptionalHaikuImagePackages BasicCommandLineTools ;

comment:6 Changed 9 years ago by mmadia

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

comment:7 Changed 9 years ago by HaikuBot

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

comment:8 Changed 9 years ago by mmadia

Resolution: fixed
Status: newclosed

Thanks for confirming!

comment:9 Changed 9 years ago by scottmc

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.