First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 41554
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Portage Utilities Team <tools-portage@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Peter Ruskin <aoyu93@dsl.pipex.com>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 41554 depends on: Show dependency tree
Show dependency graph
Bug 41554 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2004-02-14 05:52 0000 
I run this cron job:
/usr/sbin/esync && /usr/bin/emerge world -Uuvpl
and it reports:
[32;01m * Getting old portage tree
 * Doing 'emerge sync' now

 * Doing 'eupdatedb' now

sh: line 1: eupdatedb: command not found

 * Getting new portage tree
 * Preparing databases
 * 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 From David Peter 2004-02-15 02:19:59 0000 ------- 
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 From Peter Ruskin 2004-02-15 03:31:41 0000 ------- 
Might be a good idea to allow a -nc (no colour) option too.

Otherwise it's a very useful tool.

------- Comment #3 From SpanKY 2004-03-03 02:43:43 0000 ------- 
ok, this has been fixed in 0.6 as far as i can tell

------- Comment #4 From Steven Green 2004-04-26 04:14:52 0000 ------- 
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 From David Peter 2004-04-26 11:42:23 0000 ------- 
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
First Last Prev Next    No search results available      Search page      Enter new bug