Re: it works Re: About upgrading to glibc-2.40

"Pocket" ([email protected] via lfs-support Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.support
Message-ID <[email protected]>
Sent from my iPhone

> On Jan 5, 2025, at 11:57 AM, tjoen <[email protected]> wrote:
> 
> On 1/5/25 10:18 AM, tjoen ([email protected] via lfs-support Mailing List) wrote:
>> www.linuxfromscratch.org/lfs/view/stable-systemd/chapter08/glibc.html
>> Running LFS for about 15 years. With RPM.
>> Failed twice upgrading glibc with RPM
>> I came with a new idea:
>> 1. add in %pre
>>    rpm -e --justdb --nodeps glibc
>> 2. add in %install
>>    cd $RPM_BUILD_ROOT/
>>    mkdir usr/lib64/glibc
>>    mv lib64/*.so.* usr/lib64/glibc/
>> 3. add in %post
>>    install /usr/lib64/glibc/*.so.* /lib64/
>> (/lib64 is a symlink to /usr/lib64)
>> Would that work?
> 
> It works, by executing %pre and %post scripts by hand
> ~ 0$ rpm -q glibc
> glibc-2.40-1.x86_64
> 
> Many thanks for that tip: install *.so.*
> 
> Having used rpm for many years building custom gnu/linux systems you should not do what you have done.

Doing so risks breaking the system completely.  

When doing glibc upgrades using rpm you need to compile the entire tool chain including bash before you do the update.  

Are you using the latest rpm?
The later rpm version’s do a better job updating packages 

You should have tried to work with/ around rpm but what you did was to compromise rpm’s installed database.

-- 
http://lists.linuxfromscratch.org/sympa/info/lfs-support
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.