Re: glibc: why are there no upstream-patches or patch-versions?

"\"Douglas R. Reno\"" ([email protected] via lfs-support Mailing List) <[email protected]> Wed, 1 Apr 2026 18:09:24 -0500
Newsgroups gmane.linux.lfs.support
Organization Linux From Scratch
Message-ID <[email protected]>
This is a multi-part message in MIME format...

------------=_1775084979-21900-20565
Content-Language: en-US
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 3/18/26 6:18 AM, Rainer Fiebig ([email protected] via lfs-support 
Mailing List) wrote:
> I'm wondering why there aren't upstream-patches or patch-versions for
> glibc - not even for security-issues rated as "high".  Does anybody
> know?  Thanks.
> 
> Rainer
> 
> 
> 

Hi Rainer,

I'd like to first apologize for the delayed reply here, I've been taking 
some much needed time away after the release of *LFS 13.0.

I do agree that point releases would be nice. However, the glibc 
developers to maintain backport patches in release branches! A couple of 
examples:

(for LFS 13.0's version of glibc): 
https://sourceware.org/git/?p=glibc.git;a=shortlog;h=refs/heads/release/2.43/master

(for LFS 12.4's version of glibc): 
https://sourceware.org/git/?p=glibc.git;a=shortlog;h=refs/heads/release/2.42/master

I have been maintaining a LFS 12.4 system in a VM for testing patches 
against that release to provide some basic security support for SysV 
users for now. I'll continue doing that probably until at least LFS 13.1 
or until we get a stable release of Randy's upcoming SysV branch. If 
things get too complicated though with compatibility I may end up not 
testing a given update, but I'll make sure to explicitly note that in 
the advisory.

-- 
- Doug

------------=_1775084979-21900-20565
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0

-- 
http://lists.linuxfromscratch.org/sympa/info/lfs-support
Unsubscribe: See the above information page
------------=_1775084979-21900-20565--