zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Test release: 5.8.1.2-test
Date: Mon, 11 Apr 2022 12:54:02 -0700	[thread overview]
Message-ID: <CAH+w=7ZEAHzV8JFzdLZbioHwiWRV4eH6SVzmsUpeEHxMwyxk6g@mail.gmail.com> (raw)
In-Reply-To: <20220411083035.xnb4l2qby57i5axd@sym.noone.org>

On Mon, Apr 11, 2022 at 1:31 AM Axel Beckert <abe@deuxchevaux.org> wrote:
>
> Hi,
>
> On Mon, Apr 11, 2022 at 02:32:57AM +0200, Axel Beckert wrote:
> >
> > Builds fine on Debian Unstable locally and in a local, clean chroot,
> > but seems to fail to build in Debian's Gitlab CI due to one test
> > failure: https://salsa.debian.org/debian/zsh/-/jobs/2661258

Assuming this is the same failure on the other architectures you tried ...

Can you find out which UTF-8 local the %prep section of D07 is choosing?
Any recent (a year?) changes to mbrtowc() in libraries?
Could the gitlab build be overriding environment locale settings?

That test is really pretty inconsequential, and was recently moved
from the E03posix test to D07multibyte.


  reply	other threads:[~2022-04-11 19:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-09 20:07 dana
2022-04-09 20:18 ` Bart Schaefer
2022-04-10 20:07 ` Peter Stephenson
2022-04-12  9:16   ` Peter Stephenson
2022-04-10 20:21 ` Luna Jernberg
2022-04-11  0:32 ` Axel Beckert
2022-04-11  8:30   ` Axel Beckert
2022-04-11 19:54     ` Bart Schaefer [this message]
2022-04-12  2:39       ` Jun T
2022-04-12  3:58         ` Bart Schaefer
2022-04-12  6:30           ` Jun T
2022-04-12  7:17             ` Jun T
2022-04-12  9:05             ` Axel Beckert
2022-04-12 17:55               ` [PATCH] " Axel Beckert
2022-04-12 18:40                 ` Axel Beckert
2022-04-13  1:17                   ` [PATCH] " Jun T
2022-04-13  9:34                     ` Axel Beckert
2022-04-11 10:44 ` Kamil Dudka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH+w=7ZEAHzV8JFzdLZbioHwiWRV4eH6SVzmsUpeEHxMwyxk6g@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).