All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org, Rafael Aquini <aquini@redhat.com>
Subject: Re: [PATCH] kbuild: rpm-pkg: Fix C locale setup
Date: Wed, 24 Jul 2024 12:50:58 +0200	[thread overview]
Message-ID: <20240724105058.GA937292@pevik> (raw)
In-Reply-To: <CAK7LNASwTmrtgROXW_CVWX2Bjb9q=uMu7TxYkBQ6MBBTuJ_PVw@mail.gmail.com>

Hi Masahiro,

> On Wed, Jul 24, 2024 at 5:47 PM Petr Vorel <pvorel@suse.cz> wrote:

> > semicolon separation in LC_ALL is wrong. Either variable needs to be
> > exported before as a separate commit or set as part of the commit in the
> > beginning. Used second variant.

> > This fixes broken build on user's locale setup which makes 'date' binary
> > to produce invalid characters in rpm changelog (e.g. cs_CZ.UTF-8 'čec'):

> > $ make binrpm-pkg
> >   GEN     rpmbuild/SPECS/kernel.spec
> > rpmbuild -bb rpmbuild/SPECS/kernel.spec --define='_topdirlinux/rpmbuild' \
> >     --target x86_64-linux --build-in-place --noprep --define='_smp_mflags \
> >     %{nil}' $(rpm -q rpm >/dev/null 2>&1 || echo --nodeps)
> > Building target platforms: x86_64-linux
> > Building for target x86_64-linux
> > error: bad date in %changelog: St čec 24 2024 user <user@somehost>
> > make[2]: *** [scripts/Makefile.package:71: binrpm-pkg] Error 1
> > make[1]: *** [linux/Makefile:1546: binrpm-pkg] Error 2
> > make: *** [Makefile:224: __sub-make] Error 2

> > Fixes: 301c10908e42 ("kbuild: rpm-pkg: introduce a simple changelog section for kernel.spec")
> > Signed-off-by: Petr Vorel <pvorel@suse.cz>
> > ---
> >  scripts/package/mkspec | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)

> > diff --git a/scripts/package/mkspec b/scripts/package/mkspec
> > index ead54d67a024..4dc1466dfc81 100755
> > --- a/scripts/package/mkspec
> > +++ b/scripts/package/mkspec
> > @@ -50,6 +50,6 @@ fi
> >  cat << EOF

> >  %changelog
> > -* $(LC_ALL=C; date +'%a %b %d %Y') ${name} <${email}>
> > +* $(LC_ALL=C date +'%a %b %d %Y') ${name} <${email}>
> >  - Custom built Linux kernel.
> >  EOF
> > --
> > 2.43.0




> Ah, right. Thanks.



> I also noticed this mistake in Rafaels' initial submission, then
> I suggested the correct code without the semicolon:

> https://lore.kernel.org/linux-kbuild/CAK7LNAQba5CDetpwevSoaOLJ21s1tO9ZHh=7gJpPCNK0AnHfJw@mail.gmail.com/



> He tried to modify the code on his way over again,
> then I missed that he had restored the semicolon.
> I should have taken the code diff.
> :-(

Thank you for an explanation, quick review and merge!

Kind regards,
Petr

  reply	other threads:[~2024-07-24 10:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-24  8:46 [PATCH] kbuild: rpm-pkg: Fix C locale setup Petr Vorel
2024-07-24  9:11 ` Miguel Ojeda
2024-07-24 10:02 ` Masahiro Yamada
2024-07-24 10:50   ` Petr Vorel [this message]
2024-07-24 10:24 ` Masahiro Yamada
2024-07-25 12:18 ` Rafael Aquini
  -- strict thread matches above, loose matches on Subject: below --
2024-07-23 19:44 [GIT PULL] Kbuild updates for v6.11-rc1 Masahiro Yamada
2024-07-24  9:03 ` Petr Vorel
2024-07-23 21:40 ` pr-tracker-bot
2024-07-23 21:49 ` Linus Torvalds
2024-07-25 19:29   ` Masahiro Yamada
2024-07-25 19:44     ` Linus Torvalds

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=20240724105058.GA937292@pevik \
    --to=pvorel@suse.cz \
    --cc=aquini@redhat.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=masahiroy@kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.