Bug#1043209: call updatedb.plocate explicitly
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, jessie-backports (Paul Wise)
When I read
https://sources.debian.org/src/findutils/4.9.0-5/debian/locate.cron.daily/
I understand calling "updatedb" directly when it actually is
"updatedb.findutils",
can never work: all the PRUNExx etc... variable won't be defined.
So the "--slave /usr/bin/updatedb updatedb /usr/bin/updatedb.findutils \"
stanza here
https://sources.debian.org/src/findutils/4.9.0-5/debian/locate.postinst/
is useless/botched-up.
updatedb.{mlocate|plocate} do what they are expected to do and
updatedb.findutils not.
So the 3 alternatives are unequal.
All the "locate" bugs are really old no, so I guess nobody cares:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=locate
Greetings
Le lun. 7 août 2023 à 16:10, Matus UHLAR - fantomas
a écrit :
> I have configured locate.findutils to be my "locate" due to different
> behaviour when providing multiple file arguments.
>
> I know it's slower, and I can live with that.
>
> However, cruft-ng calling "updatedb" updates incorrect database this way, it
> also produces errors.
Bug#1043209: call updatedb.plocate explicitly
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. https://sources.debian.org/src/cruft-ng/0.9.56/debian/rules/ Usage of plain old "locate" from findutils was never an option as it is so slow and would be harmful to cruft(-ng) users. I have configured locate.findutils to be my "locate" due to different behaviour when providing multiple file arguments. I know it's slower, and I can live with that. However, cruft-ng calling "updatedb" updates incorrect database this way, it also produces errors. And since cruft-ng calls explicitly "plocate", it could as well call explicitly "updatedb.plocate" -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Christian Science Programming: "Let God Debug It!".
Bug#1043209: call updatedb.plocate explicitly
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://sources.debian.org/src/cruft-ng/0.9.56/debian/rules/ Usage of plain old "locate" from findutils was never an option as it is so slow and would be harmful to cruft(-ng) users. Greetings,
Bug#1043209: call updatedb.plocate explicitly
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 -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. How does cat play with mouse? cat /dev/mouse
