I can't reproduce this bug, but it would be a 'serious' bug to depend on the existace of a configuration file., which may be removed, and this removal must be preserved by package updates. If slocate depends on the "data" which it presently assumes is available as /etc/cron.daily.find.notslocate must be provided by slocate or by some package it depends on, for example, as /usr/share/slocate/cron.daily.find.
-- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
