Plocate: plocate-build.service and plocate-updatedb.timer

[eosbtw]

Some time ago I replaced mlocate with plocate:

Summary

[2021-12-20T18:03:15+0530] [PACMAN] Running 'pacman -Syu plocate'
[2021-12-20T18:03:15+0530] [PACMAN] synchronizing package lists
[2021-12-20T18:03:22+0530] [PACMAN] starting full system upgrade
[2021-12-20T18:03:50+0530] [ALPM] transaction started
[2021-12-20T18:03:53+0530] [ALPM] removed mlocate (0.26.git.20170220-7)
[2021-12-20T18:03:53+0530] [ALPM] installed liburing (2.1-1)
[2021-12-20T18:03:53+0530] [ALPM] installed plocate (1.1.13-1)
[2021-12-20T18:03:53+0530] [ALPM-SCRIPTLET] plocate now provides its own "updatedb". plocate-build.service is deprecated
[2021-12-20T18:03:53+0530] [ALPM-SCRIPTLET] and should be removed. Enable plocate-updatedb.timer.
[2021-12-20T18:03:53+0530] [ALPM] transaction completed

plocate seems to work just fine but each time there’s an update to plocate I’m reminded to remove plocate-build.service and enable plocate-updatedb.timer:

( 8/13) upgrading plocate                                                     [--------------------------------------------] 100%
plocate now provides its own "updatedb". plocate-build.service is deprecated
and should be removed. Enable plocate-updatedb.timer.

I couldn’t find guidance in the man page or in the wiki for locate. So please help!

Edit:
systemctl list-units | grep locate gives me

systemctl list-units | grep locate
plocate-updatedb.timer    loaded active waiting   Update the plocate database daily

[dalto]

That message is a hardcoded warning in the package itself.

It doesn’t indicate that you have a problem. It looks like you are already using plocate-updatedb.timer

[eosbtw]

Thanks for explaining!

[xircon]

Slight derailment - how much better than mlocate is it? (At work, so can’t play )

[eosbtw]

I read about it here: https://www.linuxuprising.com/2021/09/plocate-is-much-faster-locate-drop-in.html

[xircon]

Will read later - thanks for the pointer.