On 5/2/20 10:18 PM, Ken Moffat via lfs-dev wrote:
I'm building with LFS as at 25th April. My previous build was in
early April, and I think this is the first time I've seen a failure
in the man-db tests. With man-db-2.9.1 :
FAIL: man-missing-locales
and src/tests/test-suite.log has:
FAIL: man-missing-locales
=========================
col: failed on line 319: Invalid or incomplete multibyte or wide character
man: command exited with status 127: LC_CTYPE=en_US.UTF-8 col -b -p -x | sed -e
'/^[[:space:]]*$/{ N; /^[[:space:]]*\n[[:space:]]*$/D; }'
FAIL: missing locales
FAIL man-missing-locales (exit status: 1)
Given that things have changed since my previous build, is anyone
else seeing this ? I suspect the error might be "mine, all mine",
so I'm reluctant to add to the noise by reporting iti upstream
unless it really is common. Looking at my glibc log I did
apparently install the en_US.UTF-8 locale.
ĸen
Hi Ken,
I got that failure on my last build too (SVN-20200501):
renodr [ /mnt/lfs/jhalfs/test-logs ]$ grep FAIL 137-man-db-2.9.1
FAIL: man-missing-locales
From what I gather, I have the same problem. My guess is that it's a
bug in the test suite, but I'm not sure on that. I do use the en_US
locale as my primary. I normally do a jhalfs build after Bruce does an
update to LFS to verify that packages such as meson don't break systemd
like they did in the past.
Looking back on it - I have this failure with man-db-2.9.0 as well, on
my build on 20200201! I didn't review the test suite logs on that one :(
- Doug
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
