From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: updatedb broken as of findutils 4.8.0-1 due to bigram.exe no longer being provided
Date: Sun, 29 Aug 2021 13:02:47 +0200 [thread overview]
Message-ID: <3457cee1-18b5-2916-adee-afdfaf9769ea@t-online.de> (raw)
In-Reply-To: <a60ffa68-274a-5072-c90a-0dce7bc93431@harkless.org>
Am 28.08.2021 um 18:23 schrieb Dan Harkless:
> Looks like it's because in findutils 4.8.0-1, the bigram.exe program is
> no longer provided, but the /usr/bin/updatedb script (still) depends on
> it being there:
>
> [...]
> + for binary in $find $frcode $bigram $code
> + checkbinary /usr/libexec/frcode
The version of updatedb in the 4.8.0-1 package does not actually contain
those lines. Mention of both $bigram and $code has been removed from
the loop construct (and from everywhere else in the script).
That's because the old format of find databases, which is the only one
actually using bigram and code, was removed from updatedb as of
findutils version 4.7, so there really cannot be a need for the bigram
tool any more.
next prev parent reply other threads:[~2021-08-29 11:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <986736274.144968.1630167325057.ref@mail.yahoo.com>
2021-08-28 16:15 ` Dan Harkless
2021-08-28 16:23 ` Dan Harkless
2021-08-29 11:02 ` Hans-Bernhard Bröker [this message]
2021-08-29 12:06 ` Dan Harkless
2021-08-30 0:06 ` Brian Inglis
2022-02-24 16:32 ` Patches to findutils 4.9.0-1's updatedb to do locking, allow filenames with spaces & progress monitoring, exclude /dev on Cygwin, etc Dan Harkless
2022-02-27 11:54 ` Bernhard Voelker
2022-02-27 12:06 ` Dan Harkless
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3457cee1-18b5-2916-adee-afdfaf9769ea@t-online.de \
--to=hbbroeker@t-online.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).