From: Jari Ruusu <jariruusu@protonmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Salvatore Bonaccorso <carnil@debian.org>,
Sasha Levin <sashal@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Jiri Slaby <jirislaby@kernel.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: glibc VETO for kernel version SUBLEVEL >= 255
Date: Sun, 26 Sep 2021 10:58:59 +0000 [thread overview]
Message-ID: <xxvm9EznCQoQ_-YYhxhEknGTxHEnVW584ypJShT__L09eV-JOfFtr-K4M33xRa3VTL5tNgOGvJSUqWthW-El4IwTi6Vt4B_XZA-xMB6vOEY=@protonmail.com> (raw)
In-Reply-To: <YVA9l9svFyDgLPJy@kroah.com>
On Sunday, September 26th, 2021 at 12:29, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> On Sun, Sep 26, 2021 at 10:10:53AM +0200, Salvatore Bonaccorso wrote:
> > Recently prompted due to https://bugs.debian.org/987266 the check was
> > removed in the postinst script of libc in Debian:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987266 .
>
> Wonderful, thanks for pointing this out!
> Jari, try asking whatever distro you are getting these rebuilt packages
> from to update their scripts and all should be good.
It is/was mostly self-inflicted pain, using Rasbian distro userland and
self-compiled kernel.org kernel.
Since that problem seems to be fixed in upstream glibc, that problem is not
going to persist forever.
--
Jari Ruusu 4096R/8132F189 12D6 4C3A DCDA 0AA4 27BD ACDF F073 3C80 8132 F189
next prev parent reply other threads:[~2021-09-26 10:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 7:23 glibc VETO for kernel version SUBLEVEL >= 255 Jari Ruusu
2021-09-26 7:28 ` Greg Kroah-Hartman
2021-09-26 8:10 ` Salvatore Bonaccorso
2021-09-26 9:29 ` Greg Kroah-Hartman
2021-09-26 10:58 ` Jari Ruusu [this message]
2021-09-26 11:24 ` Greg Kroah-Hartman
2021-09-26 11:31 ` Jari Ruusu
2021-09-26 11:39 ` Greg Kroah-Hartman
2021-09-26 15:03 ` Willy Tarreau
2021-09-26 16:18 ` Jari Ruusu
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='xxvm9EznCQoQ_-YYhxhEknGTxHEnVW584ypJShT__L09eV-JOfFtr-K4M33xRa3VTL5tNgOGvJSUqWthW-El4IwTi6Vt4B_XZA-xMB6vOEY=@protonmail.com' \
--to=jariruusu@protonmail.com \
--cc=aurelien@aurel32.net \
--cc=carnil@debian.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).