Bug#1043209: call updatedb.plocate explicitly

2023-08-08 Thread Alexandre Detiste
I have commited to git the change you requested. This will be in Trixie but not in Bookworm. The package is fully backportable but I don't have the needed credentials. This is the only backport we ever had: >[2016-02-16] Accepted cruft-ng 0.4.4~bpo8+1 (source amd64) into >jessie-backports, jessi

Bug#1043209: call updatedb.plocate explicitly

2023-08-07 Thread Matus UHLAR - fantomas
On 07.08.23 14:38, Alexandre Detiste wrote: I would rather prefer that you explain to me first your real-life usage and need for this. My own need is to support Buster & Xenial for embedded devices at work with only mlocate. Hybriding updatedb would mean one more ugly #ifdef in the C code.

Bug#1043209: call updatedb.plocate explicitly

2023-08-07 Thread Alexandre Detiste
control: severity -1 wishlist Hi, I would rather prefer that you explain to me first your real-life usage and need for this. My own need is to support Buster & Xenial for embedded devices at work with only mlocate. Hybriding updatedb would mean one more ugly #ifdef in the C code. https://sou

Bug#1043209: call updatedb.plocate explicitly

2023-08-07 Thread Matus UHLAR - fantomas
Package: cruft-ng Version: 0.9.54 The cruft-ng package depends on and uses "plocate", but calls "updatedb" instead of "updatedb.plocate", which is more appropriate (locate/updatedb may point to different package using alternatives) please change cruft-ng to call "updatedb.plocate". thanks --