On Wed, Dec 01, 2021 at 02:10:33PM +0000, Jonathan Wakely wrote: > 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? I think rpm is saving the file because if was declared as %config(noreplace) by mlocate. So when you install plocate, mlocate gets uninstalled, and rpm moves the file out of the way. plocate just declares %ghost %{_sysconfdir}/updatedb.conf, because there is no need for the file. If I understand correctly, rpm created an empty file for you. I don't know why it would do that. Anyway, if the the %ghost is not appropriate, or it should be some more complex incantation, suggests are welcome. > 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? Do you have fedora-release-common-34-39 installed? The service should run once immediately after the installation. Zbyszek _______________________________________________ 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