Your message dated Tue, 17 Aug 2021 17:05:16 +0200 with message-id <[email protected]> and subject line Closing mlocate bugs has caused the Debian Bug report #925169, regarding mlocate: Remove prefix from DB, re-add during display to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 925169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925169 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: mlocate Version: 0.26-2 Severity: minor mlocate's feature of allowing for multiple locate databases is highly valuable in the case of shared filesystems. Problem is mlocate stores the *complete* path in the locate database. This is a problem if some systems mount the filesystem in different places than others. A fileserver might store home directories in /disk/home0, /disk/home1, etc. Whereas client systems may mount all of them in subdirectories of /home. In such case `locate some_user_file` would report /disk/home#/luser/some_user_file even on a client machine when the file would be found at /home/luser/some_user_file. Two approaches come to mind, if -o and -U are used, remove the common prefix of those files and flag in the database to add the path to the database to reportted files. ie do `updatedb -o /disk/home#/luser/.mlocate.db -U /disk/home#/luser`, have "/disk/home#/" not in the DB, but when /home/luser/.mlocate.db is examined add "/home/luser/" added. The other approach is to add an option for doing path substitution during DB creation. Perhaps "-c11,/home" to strip 11 characters and then add "/home" (-c is inspired by `cut`). I'm putting this in as "minor" since this is a crucial missing feature for many installations. This makes `locate` sort of work in large installations. -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | [email protected] PGP 87145445 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
--- End Message ---
--- Begin Message ---Hi, As of bookworm, mlocate no longer exists in Debian and is replaced by plocate. There's still an “mlocate” package, but it is only a transitional package to install plocate (and convert over the old database). Thus, I'm closing a series of bugs related to mlocate that I believe are either: 1. Already fixed in plocate, or 2. Related to implementation bugs in mlocate that are highly unlikely to reappear in plocate (which only shares configuration parsing code, no other internals). If you believe this is in error and the bug is relevant for plocate, please reopen it with a message as of why that is the case (and reassign it to plocate). Thanks! /* Steinar */ -- Homepage: http://www.sesse.net/
--- End Message ---
