On Tue, Aug 25, 2020 at 3:40 PM 'Reimundo Heluani' via sage-devel <sage-devel@googlegroups.com> wrote: > > On Aug 25, Dima Pasechnik wrote: > >On Tue, Aug 25, 2020 at 2:23 PM 'Reimundo Heluani' via sage-devel > ><sage-devel@googlegroups.com> wrote: > >> > >> Hello, now that GCC-10 has been merged I wanted to run a patchbot again. > >> The > >> issue of the non-existing C-locale C.UTF-8 prevents me from doing so since > >> there are tests that failed like so: > >> > >> File "src/sage/tests/cmdline.py", line 227, in > >> sage.tests.cmdline.test_executable > >> Failed example: > >> err # optional - build > >> Expected: > >> '' > >> Got: > >> '/home/sage-patchbot/sage/build/bin/sage-spkg: line 73: warning: > >> setlocale: LC_ALL: cannot change locale (C.UTF-8): No such file or > >> directory\n/bin/sh: warning: setlocale: LC_ALL: cannot change locale > >> (C.UTF-8)\nbash: warning: setlocale: LC_ALL: cannot change locale > >> (C.UTF-8)\nbash: warning: setlocale: LC_ALL: cannot change locale > >> (C.UTF-8)\nbash: warning: setlocale: LC_ALL: cannot change locale > >> (C.UTF-8)\nbash: warning: setlocale: LC_ALL: cannot change locale > >> (C.UTF-8)\nbash: warning: setlocale: LC_ALL: cannot change locale > >> (C.UTF-8)\nbash: warning: setlocale: LC_ALL: cannot change locale > >> (C.UTF-8)\nbash: warning: setlocale: LC_ALL: cannot change locale > >> (C.UTF-8)\nbash: warning: setlocale: LC_ALL: cannot change locale > >> (C.UTF-8)\nbash: warning: setlocale: LC_ALL: cannot change locale > >> (C.UTF-8)\n' > >> > >> > >> What can I do about this? > > > >can you install the C.UTF-8 locale? > > > That locale seems to be an invention of Debian that Ubuntu started using. This > was closed as wontfix 8 years ago on Arch. > > https://bugs.archlinux.org/task/32296 >
PS. no matter who invented it, but it's in Debian/Ubuntu and various derived from them systems, as well as in Fedora and the related systems (RedHat/CentOS/etc); and it is in OpenBSD, FreeBSD, macOS, etc, so Arch really is an outlier. > It seems to me that having these test failing and flooding the logs of a > regular build is not the way to go. Is there a trac ticket about this? I could > only find my comments on #30002 which was already closed. > > R. > > >> > >> R. > >> > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "sage-devel" group. > >> To unsubscribe from this group and stop receiving emails from it, send an > >> email to sage-devel+unsubscr...@googlegroups.com. > >> To view this discussion on the web visit > >> https://groups.google.com/d/msgid/sage-devel/20200825132311.GA580290%40vertex. > > > >-- > >You received this message because you are subscribed to the Google Groups > >"sage-devel" group. > >To unsubscribe from this group and stop receiving emails from it, send an > >email to sage-devel+unsubscr...@googlegroups.com. > >To view this discussion on the web visit > >https://groups.google.com/d/msgid/sage-devel/CAAWYfq1ZCR7N1Sg%3DdeyJ80XcygqcmxQHQpVnTbmL5nTra8D71A%40mail.gmail.com. > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/20200825143953.GA582885%40vertex. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq3W%3DTHXWNJui0Ws6FN7Wr1TkdEOf_7V5TFc6eUdGo15cA%40mail.gmail.com.
