[Hardy] dlocate depends on locate but not mlocate

Bug #225419 reported by Andrew
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dlocate (Debian)
Fix Released
Unknown
dlocate (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: dlocate

After trying to figure out why my daily cron jobs were running pretty late I noticed that locate and mlocate each have their own jobs installed. I went about seeing if I could remove locate from my computer and only use mlocate. The problem is that dlocate, a package I use quite often depends on findutils or locate.

I am not sure if dlocate depends on binaries from locate or the database so I am not sure if I can safely delete /etc/cron.daily/locate.

Either way, I should think dlocate should depend on mlocate or locate (or slocate too) since they should all provide the necessary functionality right?

Versions:
dlocate 0.94
locate 4.2.32-1ubuntu2
mlocate 0.18-2ubuntu1

Changed in dlocate:
status: Unknown → Fix Released
Revision history for this message
robepisc (robepisc) wrote :

According to the Debian mantainer (see Debian bug #453952), dlocate can't work with mlocate.

In fact, mlocate doesn't provide a way to create a file DB from a given file list (as dlocate requires); fileutils' locate, instead, allows it with its frcode tool.

Revision history for this message
Iain Lane (laney) wrote :

Closing per Debian maintainer.

Changed in dlocate:
status: New → Invalid
Matt Zimmerman (mdz)
Changed in dlocate:
status: Fix Released → Unknown
Changed in dlocate:
status: Unknown → Won't Fix
Changed in dlocate (Debian):
status: Won't Fix → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.