public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: Nicolas Schier <nsc@kernel.org>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, Steve French <smfrench@gmail.com>
Subject: Re: [PATCH 0/2] kbuild: rpm-pkg: Address -debuginfo build regression with RPM < 4.20.0
Date: Fri, 13 Feb 2026 14:11:38 -0500	[thread overview]
Message-ID: <20260213191138.GA2131983@ax162> (raw)
In-Reply-To: <aY8wyR572eZYWVJY@sgarzare-redhat>

Hi Stefano,

On Fri, Feb 13, 2026 at 03:11:38PM +0100, Stefano Garzarella wrote:
> On Tue, Feb 10, 2026 at 12:04:47AM -0700, Nathan Chancellor wrote:
> > Steve reported a build issue with commit 62089b804895 ("kbuild: rpm-pkg:
> > Generate debuginfo package manually") on RHEL9, which has an older
> > version of RPM than what I tested. Turns out that RPM 4.20.0 fixed an
> > issue with specifying %files for a -debuginfo subpackage.
> > 
> > The first patch restricts the new -debuginfo package generation process
> > to CONFIG_MODULE_SIG=y and RPM >= 4.20.0 to ensure it is actually
> > necessary and working. The second patch restores the original -debuginfo
> > package generation process from commit a7c699d090a1 ("kbuild: rpm-pkg:
> > build a debuginfo RPM") when CONFIG_MODULE_SIG is disabled to keep the
> > -debuginfo package around for older versions of RPM.
> 
> Yeah, I had similar issue on Fedora 42 (RPM version 4.20.1) and this series
> fixed my issue.

Thanks for testing! I find that a little odd though since I tested
62089b804895 in Fedora 42 during my investigation of the problem and it
worked fine without these changes. Nevertheless, I will add your tags to
this series when I apply it.

Cheers,
Nathan

  parent reply	other threads:[~2026-02-13 19:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10  7:04 [PATCH 0/2] kbuild: rpm-pkg: Address -debuginfo build regression with RPM < 4.20.0 Nathan Chancellor
2026-02-10  7:04 ` [PATCH 1/2] kbuild: rpm-pkg: Restrict manual debug package creation Nathan Chancellor
2026-02-10  7:04 ` [PATCH 2/2] kernel: rpm-pkg: Restore find-debuginfo.sh approach to -debuginfo package Nathan Chancellor
2026-02-11 20:33 ` [PATCH 0/2] kbuild: rpm-pkg: Address -debuginfo build regression with RPM < 4.20.0 Nicolas Schier
2026-02-13 14:11 ` Stefano Garzarella
2026-02-13 17:34   ` Steve French
2026-02-13 19:11   ` Nathan Chancellor [this message]
2026-02-13 19:41     ` Stefano Garzarella
2026-02-15 21:29       ` Nathan Chancellor
2026-02-16  8:25         ` Stefano Garzarella
2026-02-16 11:42           ` Nathan Chancellor
2026-02-16 14:03             ` Stefano Garzarella
2026-02-18 20:49 ` Nathan Chancellor

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=20260213191138.GA2131983@ax162 \
    --to=nathan@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nsc@kernel.org \
    --cc=sgarzare@redhat.com \
    --cc=smfrench@gmail.com \
    --cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox