OK, so it DOESN'T work for me when using a custom configfile. Putting "export LC_ALL=C.UTF-8" into that custom config file and starting the pbuilder build results in the same "LC_ALL=C" still being set, although other LC_* env vars are now set to "C.UTF-8". So although it might be INTENDED to work by using the custom configfile, I'm still seeing LC_ALL=C regardless.
Also, the point is not that a "policy-conforming" package doesn't build, it's that in the real world various real builds fail due the incorrect locale. So in a "perfect" world then perhaps it wouldn't matter that pbuilder is using a DIFFERENT locale than all official sbuild Debian and Ubuntu builds. But in the actual real world it does matter, and therefore I still consider it a serious bug and limitation. In any case, thank you all for your feedback, and have a nice day! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947424 Title: Cannot set pbuilder build locale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pbuilder/+bug/1947424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
