All of lore.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: Mon, 16 Feb 2026 06:42:27 -0500	[thread overview]
Message-ID: <20260216114227.GA213868@ax162> (raw)
In-Reply-To: <aZLTsduMY7H-QoA2@sgarzare-redhat>

On Mon, Feb 16, 2026 at 09:25:25AM +0100, Stefano Garzarella wrote:
> Oh, yeah, I just tried the following change on top of commit cee73b1e840c
> ("Merge tag 'riscv-for-linus-7.0-mw1' of
> git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux"), so without this
> series applied:
> 
> diff --git a/scripts/package/kernel.spec b/scripts/package/kernel.spec
> index 0f1c8de1bd95..86ca327ebccf 100644
> --- a/scripts/package/kernel.spec
> +++ b/scripts/package/kernel.spec
> @@ -50,6 +50,7 @@ against the %{version} kernel package.
>  %if %{with_debuginfo}
>  %package debuginfo
>  Summary: Debug information package for the Linux kernel
> +AutoReqProv: no
>  %description debuginfo
>  This package provides debug information for the kernel image and modules from the
>  %{version} package.
> 
> And I'm able to generate RPMs too without errors!

Great, thanks for confirming! Does it still work with:

  AutoReq: 0
  AutoProv: 1

as I notice that is what the %_debuginfo_template in /usr/lib/rpm/macros
uses by default. I suspect that the automatic requires is where things
explodes and I think we do want the automatic provides because I believe
that is how the "this package provides this debug build ID" generation
happens.

Cheers,
Nathan

  reply	other threads:[~2026-02-16 11:42 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
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 [this message]
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=20260216114227.GA213868@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 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.