From: Nathan Chancellor <nathan@kernel.org>
To: Steve French <smfrench@gmail.com>
Cc: Nicolas Schier <nsc@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Holger Kiehl <Holger.Kiehl@dwd.de>
Subject: Re: Regression with patch "kbuild: rpm-pkg: Generate debuginfo package manually"
Date: Tue, 10 Feb 2026 10:34:46 -0700 [thread overview]
Message-ID: <20260210173446.GA4037050@ax162> (raw)
In-Reply-To: <20260209222550.GA1844976@ax162>
On Mon, Feb 09, 2026 at 03:25:54PM -0700, Nathan Chancellor wrote:
> On Thu, Feb 05, 2026 at 05:24:16PM -0700, Nathan Chancellor wrote:
> > On Thu, Feb 05, 2026 at 05:56:20PM -0600, Steve French wrote:
> > > I noticed with the recent patch below:
> > >
> > > commit 62089b804895e845f82e132ea9d46a1fc53ed5a7
> > > Author: Nathan Chancellor <nathan@kernel.org>
> > > Date: Wed Jan 21 15:29:15 2026 -0700
> > >
> > > kbuild: rpm-pkg: Generate debuginfo package manually
> > >
> > > that all of our test builds were failing to build kernel RPMs for
> > > 6.19-rc8 and later (see e.g.
> > > http://osmb311-linux-testing.southcentralus.cloudapp.azure.com/#/builders/1/builds/99/steps/9/logs/stdio).
> >
> > Sorry for the breakage :(
> >
> > Can you provide me with the .config? I want to see if I can reproduce
> > this locally.
> ...
> > I wonder if we are relying on something in a newer rpm version that is
> > not available on an older version that is present in RHEL.
>
> Ooookay, after much gnashing of teeth investigating different
> environments and such, it looks like my change implicitly relies on some
> improvements to debuginfo package generation that are in rpm 4.20 or
> newer (Fedora 41 or newer), which is why I have not seen any issues up
> until this point. I am not entirely sure why yet though but I wanted to
> provide a small update that I am still looking into this. I plan to send
> the main 7.0 Kbuild pull request then I should be able to focus more
> intently on this.
Just to close the loop for future travelers:
https://lore.kernel.org/20260210-kbuild-fix-debuginfo-rpm-v1-0-0730b92b14bc@kernel.org/
Cheers,
Nathan
prev parent reply other threads:[~2026-02-10 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 23:56 Regression with patch "kbuild: rpm-pkg: Generate debuginfo package manually" Steve French
2026-02-06 0:24 ` Nathan Chancellor
2026-02-09 22:25 ` Nathan Chancellor
2026-02-10 17:34 ` Nathan Chancellor [this message]
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=20260210173446.GA4037050@ax162 \
--to=nathan@kernel.org \
--cc=Holger.Kiehl@dwd.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nsc@kernel.org \
--cc=smfrench@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox