From: Kalle Valo <kvalo@kernel.org>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Masahiro Yamada <masahiroy@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: Change in kernel debian packages between -rc2 and -rc3
Date: Mon, 27 Mar 2023 10:34:47 +0300 [thread overview]
Message-ID: <87pm8utzoo.fsf@kernel.org> (raw)
In-Reply-To: <20230326121118.GB323408@mit.edu> (Theodore Ts'o's message of "Sun, 26 Mar 2023 08:11:18 -0400")
"Theodore Ts'o" <tytso@mit.edu> writes:
> On Sun, Mar 26, 2023 at 12:39:44PM +0900, Masahiro Yamada wrote:
>>
>> I am afraid you are completely misunderstanding the two versions,
>> the ABI version and the package version.
>>
>> They do not need to match. Actually, they do not match.
>>
>> See real Debian (or Ubuntu) systems.
>>
>> `uname -r` returns '5.10.0-21-amd64'.
>> This is what they call the ABI version, and
>> this is contained as a part of the package name,
>> 'linux-image-5.10.0-21-amd64'
>
> That may be a convention that Debian uses, but I'll point out that
> trying to use this as an ABI version when people are using different
> .config's is not going to end well. That's because many different
> Kernel configurations will end up making incompatible changes to the
> ABI. and only works if you are ***super*** careful about not making
> any kind of changes (e.g., the number of CPU's, adding or changing
> various cgroup controllers, all of which will make incompatible kernel
> ABI changes.)
>
> This is "Stable ABI nonsense" is well, nonsense.
>
>> It was _not_ reflected in the package version.
>> This is also correct since the package version
>> is not meant to reflect such user configuration
>> as CONFIG_LOCALVERSION.
>
> Citation, please? Does the Debian system work in that particular way?
>
> In any case, it's an incompatible regression made during rc2 and rc3,
> which I think is at the very least, unfortunate.
v6.3-rc3 also broke my deb install scripts, so definitely not cool
breaking it like this. Please keep the deb names stable.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-03-27 7:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 14:31 Change in kernel debian packages between -rc2 and -rc3 Theodore Ts'o
2023-03-26 3:39 ` Masahiro Yamada
2023-03-26 12:11 ` Theodore Ts'o
2023-03-27 7:34 ` Kalle Valo [this message]
2023-03-27 13:35 ` Masahiro Yamada
2023-03-28 4:09 ` Theodore Ts'o
2023-04-02 3:37 ` Theodore Ts'o
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=87pm8utzoo.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=tytso@mit.edu \
/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