On Tue, 23 Nov 2021 at 17:20, Ben Cotton wrote: > == Upgrade/compatibility impact == > The upgrade should be mostly invisible. It is possible that somebody > might be relying on some very specific `mlocate` behaviour or parsing > the `mlocate` database directly, but no such cases are currently > known. > > == How To Test == > # Install `plocate` (`sudo dnf install plocate --allowerasing`) > # Wait for `plocate-updatedb.service` to finish (`sudo systemctl start > plocate-updatedb.service`) > # Use `plocate pattern` or `plocate -r <regexp>` to search for files. > > == User Experience == > Users should not notice the difference. Installing `plocate` > automatically removes `mlocate`. The new implementation is generally > compatible with the old one in all common cases, and provides some > additional options. I have just installed plocate to try it on F34, and got: warning: /etc/updatedb.conf saved as /etc/updatedb.conf.rpmsave I reviewed the changes, and the new file is empty. Users will notice the difference. Is that expected? Is it because I'm still on F34? Also, the plocate-updatedb service was not started after installing it, so I can't use locate until the DB is created. Is that expected? Does it wait until the timer runs it? _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
