From: Stefano Garzarella <sgarzare@redhat.com>
To: Nathan Chancellor <nathan@kernel.org>
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 09:25:25 +0100 [thread overview]
Message-ID: <aZLTsduMY7H-QoA2@sgarzare-redhat> (raw)
In-Reply-To: <20260215212901.GA695045@ax162>
On Sun, Feb 15, 2026 at 04:29:01PM -0500, Nathan Chancellor wrote:
>On Fri, Feb 13, 2026 at 08:41:24PM +0100, Stefano Garzarella wrote:
>> mmm, that it's odd indeed.
>> Without this series applied, I had issues on Fedora 42 (RPM version
>> 4.20.1), but it worked on Fedora 43 (RPM version 6.0.1).
>>
>> I just retried on Fedora 42 to build commit cee73b1e840c ("Merge tag
>> 'riscv-for-linus-7.0-mw1' of
>> git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux") and I have
>> the following errors:
>>
>> RPM build errors:
>> Dependency tokens must begin with alpha-numeric, '_' or '/': #�) = 0x0d000002
>> Dependency tokens must begin with alpha-numeric, '_' or '/': �) = 0x0d000000
>> Dependency tokens must begin with alpha-numeric, '_' or '/': ) = 0x7c0e000000
>> Unknown rich dependency op 'Hat': (Red Hat 15.2.1-7)) = 0x3130363230322000
>> Unknown rich dependency op 'Hat': (Red Hat 15.2.1-7)) = 0x4728203a43434800
>> Unknown rich dependency op 'Hat': (Red Hat 15.2.1-7)) = 0x3130363230322000
>> Unknown rich dependency op 'Hat': (Red Hat 15.2.1-7)) = 0x4728203a43434800
>> Dependency tokens must begin with alpha-numeric, '_' or '/': ) = 0x47161b0700
>> Dependency tokens must begin with alpha-numeric, '_' or '/': ) = 0x339b1a000ac0
>> Dependency tokens must begin with alpha-numeric, '_' or '/': �) = 0x36000000
>> Dependency tokens must begin with alpha-numeric, '_' or '/': ) = 0x7508200000000000
>> Dependency tokens must begin with alpha-numeric, '_' or '/': ) = 0x2e76000000000400
>> Dependency tokens must begin with alpha-numeric, '_' or '/': ) = 0x803ab2b00000000
>> Dependency tokens must begin with alpha-numeric, '_' or '/': ) = 0x1a00000000005e00
>> Dependency tokens must begin with alpha-numeric, '_' or '/': ) = 0x125590000000060
>> Dependency tokens must begin with alpha-numeric, '_' or '/': = 0x03080000
>> Dependency tokens must begin with alpha-numeric, '_' or '/': ) = 0x818000000003600
>> Dependency tokens must begin with alpha-numeric, '_' or '/': �) = 0x0d000000
>> Dependency tokens must begin with alpha-numeric, '_' or '/': ) = 0x7c0e000000
>> Unknown rich dependency op 'Hat': (Red Hat 15.2.1-7)) = 0x3130363230322000
>> Unknown rich dependency op 'Hat': (Red Hat 15.2.1-7)) = 0x4728203a43434800
>> Dependency tokens must begin with alpha-numeric, '_' or '/': $) = 0x1c01040000004d00
>> Unknown rich dependency op 'Hat': (Red Hat 15.2.1-7)) = 0x3130363230322000
>> Unknown rich dependency op 'Hat': (Red Hat 15.2.1-7)) = 0x4728203a43434800
>> Dependency tokens must begin with alpha-numeric, '_' or '/': ) = 0x63c300000000000
>> Illegal char '?' (0xffffffd8) in: 3�
>> Dependency tokens must begin with alpha-numeric, '_' or '/': ) = 0x1320f691700
>> Dependency tokens must begin with alpha-numeric, '_' or '/': ) = 0x2e17101500
>> Version required: ksym(g) =
>> Unknown rich dependency op 'Hat': (Red Hat 15.2.1-7)) = 0x3130363230322000
>> Unknown rich dependency op 'Hat': (Red Hat 15.2.1-7)) = 0x4728203a43434800
>> Dependency tokens must begin with alpha-numeric, '_' or '/': p) = 0x3875480000005c
>> Dependency tokens must begin with alpha-numeric, '_' or '/': ]) = 0xfc22000000003000
>> Dependency tokens must begin with alpha-numeric, '_' or '/': 2) = 0x5d0d03cc22
>> Dependency tokens must begin with alpha-numeric, '_' or '/': ]) = 0x32042c1c
>> Unknown rich dependency op 'Hat': (Red Hat 15.2.1-7)) = 0x3130363230322000
>> Unknown rich dependency op 'Hat': (Red Hat 15.2.1-7)) = 0x4728203a43434800
>> Dependency tokens must begin with alpha-numeric, '_' or '/': ) = 0x1c11a3d1b00
>> Version required: ksym(�) =
>> Unknown rich dependency op 'Hat': (Red Hat 15.2.1-7)) = 0x3220312e322e3400
>> Unknown rich dependency op 'Hat': (Red Hat 15.2.1-7)) = 0x322e353120295400
>> Unknown rich dependency op 'Hat': (Red Hat 15.2.1-7)) = 0x2029554e47282000
>> Unknown rich dependency op 'Hat': (Red Hat 15.2.1-7)) = 0x3130363230322000
>> Illegal char ')' (0x29) in: (GNU)
>> Unknown rich dependency op 'Hat': (Red Hat 15.2.1-7)) = 0x4728203a43434800
>> Dependency tokens must begin with alpha-numeric, '_' or '/': #) = 0x031c0000
>> Dependency tokens must begin with alpha-numeric, '_' or '/': ) = 0x570d03ea11
>> Unknown rich dependency op 'Hat': (Red Hat 15.2.1-7)) = 0x3130363230322000
>> Unknown rich dependency op 'Hat': (Red Hat 15.2.1-7)) = 0x4728203a43434800
>> Dependency tokens must begin with alpha-numeric, '_' or '/': ) =
>> 0x4000000520d03c0
>> Dependency tokens must begin with alpha-numeric, '_' or '/': C) = 0x690d03cf33
>> Dependency tokens must begin with alpha-numeric, '_' or '/': �l) = 0x102000001471140
>> Dependency tokens must begin with alpha-numeric, '_' or '/': i) = 0x4a00000000011000
>> Dependency tokens must begin with alpha-numeric, '_' or '/': ) = 0x2e00000000240000
>> Dependency tokens must begin with alpha-numeric, '_' or '/': ) = 0x42111503a533
>> Dependency tokens must begin with alpha-numeric, '_' or '/': ) = 0xea1303bb33000000
>> Unknown rich dependency op 'Hat': (Red Hat 15.2.1-7)) = 0x3130363230322000
>>
>> But if I apply this series on top, everything is fine.
>
>Okay interesting! I have not seen that error yet... I wonder if adding
>'AutoReqProv: no' to the kernel-debuginfo subpackage (like the
>kernel-devel subpackage) would avoid that for rpm 4.20.0... Probably not
>that big of a deal if it is resolved with rpm 6.0.1 but it would be good
>to avoid as many corner cases as possible.
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!
Thanks,
Stefano
next prev parent reply other threads:[~2026-02-16 8:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 7:04 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 [this message]
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=aZLTsduMY7H-QoA2@sgarzare-redhat \
--to=sgarzare@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--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
all inboxes | Powered by JetHome®