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 #969522, regarding mlocate: please consider moving the mlocate VCS to the "debian" project 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.) -- 969522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969522 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: mlocate Version: 0.13-3 Severity: minor Prior to Salsa, the mlocate source was in the "collab-maint" VCS repository. This signalled that the package was to be collaboratively maintained. The equivalent way on Salsa of signalling that a package should be collaboratively maintained is for it to be part of the "debian" project. If you are still happy for the package to be collaboratively maintained, please consider moving the VCS repository into the "debian" project on Salsa, to signal so. Either way, please configure the project's default branch to "debian", so Merge Requests are raised against that branch by default. Best wishes! -- System Information: Debian Release: 10.2 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- 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 ---
