Hi, On 2023-10-29 12:51, Mike Gabriel wrote: > Hi, > > On So 29 Okt 2023 11:17:21 CET, Mike Gabriel wrote: > > > Investigating deeper... > > underlying cause that introduced this FTBFS in geonames is this patch [1] in > glibc (added with glibc 2.37-8): > > [1] > https://salsa.debian.org/glibc-team/glibc/-/blob/sid/debian/patches/any/git-c-utf-8-language.diff > > I just rebuilt 2.37-12 (glibc version currently in unstable) with that patch > disabled in d/p/series and geonames builds fine again. > > Cc:ing Aurelien Jarno who cherry-picked that patch from upstream into the > glibc Debian package. > > @Aurelien: Any idea, what my cause the observed FTBFS in geonames (#1052859).
The backported commit changed the behaviour of the C.UTF-8 locale wrt LANG and LANGUAGE to match the one of the C locale. The goal being that C.UTF-8 locale can completely replace the C locale. It appears that geonames was already affected by this issue and used the C.UTF-8 in debian/rules as a workaround (and also to ensure a UTF-8 locale for valid string comparison). With the glibc change, this workaround does not work. I have seen that in the meantime you have done a new upload with the en_US.UTF-8 locale, that's a perfectly valid workaround. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
signature.asc
Description: PGP signature
