From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050105 Galeon/1.3.20 (Debian package 1.3.20-1) Description of problem: If a user specifies databases via the LOCATE_PATH environmental variable, they will be ignored if the system slocate db is used. The problem is that the parse_decode_path() routine always overwrites the current path, rather than appending to it. For example: env LOCATE_PATH=mydb locate foo will ignore mydb. This is fixed in the latest version of this package, which now seems to be the Debian version, as the author is a Debian developer. Here's where I found it: http://packages.debian.org/unstable/source/slocate Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: % mkdir foo % cp /etc/motd foo/MyMOTD % slocate -U `pwd`/foo -o foo.db % env LOCATE_PATH=foo.db locate MyMOTD % locate -d foo.db MyMOTD /data/pelf0/dj/tmp/buggy/foo/MyMOTD Additional info:
slocate-2.7-17 in rawhide uses Debian slocate_2.7-4. Thanks for your report.