https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: mail-mta/courier-1.0.14 fails tests. Discovered on: amd64 (internal ref: ci) NOTE: This machine uses GLIBC-2.32. If you think that this issue is strictly related to GLIBC please block bug 736174.
Created attachment 659703 [details] build.log build log and emerge --info
This seems to indicate there may be something wrong with the test system: ./testsuite: line 2: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) Is this some test where you try to see what happens if you don't have an utf-8 locale? I think the tests assume that you have a unicode-capable system. If you don't that's just unsupported, I'm not sure what to do about this.
There is a solution, which is to patch the offending tests. sed -i -Ee 's/^(LANG=|LC_ALL=)en_US\.(UTF-8|utf-?8)/\1C.UTF-8/' libs/rfc2045/testsuite{,mm} || die Nowadays, Gentoo's locale-gen(8) always bundles a C.UTF-8 locale into locale-archive.
I provided relevant information. The offending test hinges upon the UTF-8 character type being in effect. However, it also assumes that the en_US.UTF-8 locale is available. Non-American Gentoo users that decide to customise /etc/locale.gen are likely not to have this locale available. Clearly, this locale wasn't available at the tinderbox build host either. At least, at the time. Generating the en_US.UTF-8 locale at said host would 'fix' it there. Patching the test in the manner that I described would fix it for all Gentoo users on glibc.
I should also add that C.UTF-8 is valid for musl libc.
Re-opening because it's apparent from the question posed by Comment 2 that the nature of the problem was not understood and because my attempts to rectify that didn't spur any discussion. I'm happy to explain further if it remains unclear.
tinderbox_musl has reproduced this issue with version 1.1.8-r2 - Updating summary.
