Comment 1 for bug 189462

Just curious, why did you send this email to me?
I did not "manually" report this bug. Perhaps it was one of those
self-generating reports from one of my crashes. If that is the
case it becomes even more interesting because I received an
email this morning rejecting this bug because I didn't supply
enough information. That would be information created by the
system - not me. In any event, this isn't recent - perhaps from
Alpha-2 or 3 not Alpha-4.

On Feb 5, 2008 8:29 PM, Greg Ward <email address hidden> wrote:
> Public bug reported:
>
> Binary package hint: slocate
>
> I get this email from cron every morning:
>
> """
> From: Anacron <root@xxx>
> To: root@xxx
> Subject: Anacron job 'cron.daily' on gollum
> Date: Tue, 05 Feb 2008 07:38:56 -0500
>
> /etc/cron.daily/slocate: slocate: fatal error: load_file: Could not open file: /etc/updatedb.conf: No such file or directory
> """
>
> This is on hardy (installed from scratch a few weeks ago and kept up-to-
> date since then). Obviously I haven't bothered to create
> /etc/updatedb.conf, but is that really a fatal error? If so, shouldn't
> the slocate package ship with an empty or skeletal /etc/updatedb.conf?
>
> In fact, I can trivially workaround the problem:
>
> # touch /etc/updatedb.conf
>
> ** Affects: slocate (Ubuntu)
> Importance: Undecided
> Status: New
>
> --
> slocate cron job fails if /etc/updatedb.conf not found
> https://bugs.launchpad.net/bugs/189462
> You received this bug notification because you are a bug contact for
> slocate in ubuntu.
>