[bug #46815] problem when testing file size

Update of bug #46815 (project findutils): Status: Invalid => Need Info Open/Closed: Closed => Open ___ Follow-up Comment #4: Yes, both Sebasti

[bug #46846] failure due to filename encoding and locale on OSX

Update of bug #46846 (project findutils): Item Group:None => Wrong result Assigned to:None => jay ___ Follow-up Comment #1: Your workaround s

[bug #46846] failure due to filename encoding and locale on OSX

Follow-up Comment #2, bug #46846 (project findutils): Having read the bug report you pointed to, I'll be a bit more explicit: yes, I confirm that this is a bug in the updatedb script. The fix you suggest is appropriate. ___ Reply to this i

[PATCH] updatedb: run in the C locale, don't do case-folding.

* locate/updatedb.sh: Set LC_ALL to C to avoid unexpected character encodings in path names causing sort to fail (idea from Clarence Risher). Don't do case-folding, since the character set in now C, which is likely inconsistent with the user's expectations anyway. Honour $TMPDIR. Correct the error

[PATCH] updatedb: Remove support for the old pre-4.0 database format.

* locate/testsuite/Makefile.am (EXTRA_DIST_EXP): Remove locate.gnu/old_prefix.exp and locate.gnu/oldformat.exp. (EXTRA_DIST_XO): Remove locate.gnu/old_prefix.xo and locate.gnu/oldformat.xo. * doc/find.texi (Database Formats): Remove the warning about old versions of locate failing to read the LOCAT

Re: [PATCH] updatedb: run in the C locale, don't do case-folding.

On 01/09/2016 10:18 PM, James Youngman wrote: > * locate/updatedb.sh: Set LC_ALL to C to avoid unexpected character > encodings in path names causing sort to fail (idea from Clarence > Risher). Don't do case-folding, since the character set in now C, > which is likely inconsistent with the user's