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 #524134, regarding Compressed database files. 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.) -- 524134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524134 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: mlocate Version: 0.21.1-2 Severity: wishlist Since mlocate writes a new database file each time it updates, it would be nice if there was a compression option. I would agree that most systems won't have a large database; however I am testing the feasability on an archive filesystem with a large amount of files. For the curioush ere's an ls -l of the database files while updatedb is running: -rw-r--r-- 1 root root 1179729353 Apr 14 21:36 /archive/archive.db -rw------- 1 root root 948277248 Apr 14 22:06 /archive/archive.db.Mg7tBQ That's about 55 million files. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.27.5 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages mlocate depends on: ii adduser 3.99 Add and remove users and groups ii libc6 2.7-5 GNU C Library: Shared libraries mlocate recommends no packages. -- no debconf information
--- 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 ---
