First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 1128
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Chad Huneycutt <chadh@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Chad Huneycutt <chadh@gentoo.org>
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 1128 depends on: Show dependency tree
Bug 1128 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

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


Not eligible to see or edit group visibility for this bug.






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

Description:   Opened: 2002-03-13 15:36 0000 
I inadvertently emerged a masked version of slocate (stupid portage_pre24), and
updatedb apparently takes new commandline options, so your slocate.conf needs to
be updated.

Just a heads-up.

------- Comment #1 From Daniel Robbins (RETIRED) 2002-03-15 01:47:18 0000 ------- 
:)

------- Comment #2 From Chad Huneycutt 2002-03-18 21:24:12 0000 ------- 
Okay.  This is misreported.  The problem is not a masked version of slocate. 
the problem is that slocate and findutils both install versions of locate and
updatedb.  If findutils gets installed after slocate, then the cron script that
comes with slocate won't work (since updgradedb).

------- Comment #3 From Chad Huneycutt 2002-03-18 21:41:00 0000 ------- 
Hmmm... I am not sure what to do with this.  There are 2 possibilities: the
first  is to do nothing, which is what I am doing for now.  The other is to
remove findutils' locate and updatedb.  Then there is no conflict :-)

------- Comment #4 From Thilo Bangert 2003-04-12 08:38:52 0000 ------- 
this is taken care of in bug #18729 as well as bug #8227
First Last Prev Next    No search results available      Search page      Enter new bug