Bug 41554 – esync can't find eupdatedb

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Peter Ruskin 2004-02-14 05:52:34 UTC]

I run this cron job:
/usr/sbin/esync && /usr/bin/emerge world -Uuvpl
and it reports:
[32;01m *[0m Getting old portage tree
[32;01m *[0m Doing 'emerge sync' now

[32;01m *[0m Doing 'eupdatedb' now

sh: line 1: eupdatedb: command not found

[32;01m *[0m Getting new portage tree
[32;01m *[0m Preparing databases
[32;01m *[0m Searching for changes

These are the packages that I would merge, in order:

Calculating world dependencies    ...done!

The problem is that /usr/sbin/esync calls eupdatedb instead of /usr/sbin/eupdatedb - this is only a problem running from cron

[Comment 1 David Peter 2004-02-15 02:19:59 UTC]

Hi,

Thanks for the bugreport (thanks to vapier for adding my to CC-List). I will fix this in the next version.

David

[Comment 2 Peter Ruskin 2004-02-15 03:31:41 UTC]

Might be a good idea to allow a -nc (no colour) option too.

Otherwise it's a very useful tool.

[Comment 3 SpanKY 2004-03-03 02:43:43 UTC]

ok, this has been fixed in 0.6 as far as i can tell

[Comment 4 Steven Green 2004-04-26 04:14:52 UTC]

I still get this problem with 0.6, also if you run:
sudo /usr/sbin/esync

Then you still get eupdatedb not found error.

Problem is that /usr/sbin (or /usr/lib/esearch) is not in the path when run like this.

[Comment 5 David Peter 2004-04-26 11:42:23 UTC]

Hi,

You're right, I have fixed this error, but I haven't released esearch-0.6.1.

I hope I can release the next version (which also fixes many other bugs) in a few days.

David