120180 – eselect doesn't find sed in /usr/bin/ (core.bash line 115)

Bug 120180 - eselect doesn't find sed in /usr/bin/ (core.bash line 115)

Summary: eselect doesn't find sed in /usr/bin/ (core.bash line 115)

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	New packages (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Gentoo eselect Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2006-01-24 06:21 UTC by Ingo Bormuth
Modified:	2006-05-29 22:11 UTC (History)
CC List:	3 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Ingo Bormuth 2006-01-24 06:21:52 UTC

Typing "eselect bashcomp help" gives me

   [...]
   Extra actions:
   /usr/share/eselect//libs/core.bash: line 115: /usr/bin/sed: 
   No such file or directory

Changing the given line to use /bin/sed helps.

Comment 1 Ciaran McCreesh 2006-01-24 06:34:07 UTC

How did your sed end up there?

Comment 2 Ingo Bormuth 2006-01-24 06:59:27 UTC

Ooops, apparently it got lost somehow (makes me frightened). 
It was still there two weeks ago (checked a backup).
Actually /usr/bin/sed is a symlink to /bin/sed.

So please forget you ever saw this :-/

Comment 3 Max 2006-02-10 05:36:50 UTC

There has to be done some research to this problem nevertheless. My sed just ended up without a symlink in /usr/bin and only available in /bin. I therefore had the same error as mentioned in the original report when 'eselect opengl set ati'.

I don't know when or where this happened, but I know I didn't delete the symlink myself, so it must have happened last time I updated sys-apps. Should I file over there?

Comment 4 LXj 2006-05-29 22:11:36 UTC

Got the same just now