Package: slocate Version: 3.1-2.1custom1 Severity: normal
Installation of slocate moves diverts etc/cron.daily/find to /etc/cron.daily/find.notslocate but doesn't disable it, so both /etc/cron.daily/find.notslocate and /etc/cron.daily/slocate are run daily, resulting in updatedb being run twice in a row. Maybe the slocate script could check the the mtime on the database and if it is less than 12 hours old skip running updatedb? Or maybe /etc/cron.daily/find.notslocate should be disabled alltogether, as /usr/bin/updatedb.notslocate is not being run and therfore the locate database is not being updated. In fact the file name find.notslocate is misleadinng because it IS slocate, as updatedb, that is being run. *** .reportbug.sig NOTE: Due to debian.org's inadequate measures to prevent email address harvesting from bugs.debian.org, you must include "Bug#", without the quotes, in the subject of any email that you wish to send me directly. Automated messages sent by the emial list daemon already do this. Thank You. Brian McDonald -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (470, 'testing'), (460, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.8-3-686 Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1) Versions of packages slocate depends on: ii adduser 3.63 Add and remove users and groups ii dpkg 1.10.28 Package maintenance system for Deb ii libc6 2.3.2.ds1-22sarge4 GNU C Library: Shared libraries an -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
