Re: dnf messages when installing recent fc44 kernels

[email protected]
Newsgroups gmane.linux.redhat.fedora.general
Message-ID <[email protected]>
On 30/5/26 17:03, Samuel Sieb wrote:
> On 5/29/26 10:19 PM, [email protected] wrote:
>> I upgraded fc42->fc44 a few days ago.
>>
>> This shows up at the end of each kernel update:
>>
>>>>> Running %posttrans scriptlet: kernel-core-0:7.0.9-205.fc44.x86_64
>>>>> Finished %posttrans scriptlet: kernel-core-0:7.0.9-205.fc44.x86_64
>>>>> Scriptlet output:
>>>>> dracut-install: ERROR: could not locate dependency libcrypto.so.10 requested by '/lib64/libssl.so.1.0.2o'
>>>>> dracut-install: ERROR: installing '/lib64/libssl.so.1.0.2o'
>>>>> dracut-install: ERROR: could not locate dependency libcrypto.so.10 requested by '/usr/lib64/libssl.so.1.0.2o'
>>>>> dracut-install: ERROR: installing '/usr/lib64/libssl.so.1.0.2o'
>>>>> dracut-install: ERROR: could not locate dependency libcrypto.so.10 requested by '/usr/lib64/libssl.so.1.0.2o'
>>>>> dracut-install: ERROR: installing '/usr/lib64/libssl.so.10'
>>>>> dracut[E]: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/ dracut.dmOI579/initramfs -a -l -f /lib64/libssl.so /lib64/ libssl.so.1.0.2o /lib64/libssl.so.1.1 /lib64/libssl.so.1.1.1q / lib64/libssl.so.10 /lib64/libssl.so.3 /lib64/libssl.so.3.5.5 /usr/ lib64/libssl.so /usr/lib64/libssl.so.1.0.2o /usr/lib64/ libssl.so.1.1 /usr/lib64/libssl.so.1.1.1q /usr/lib64/libssl.so.10 / usr/lib64/libssl.so.3 /usr/lib64/libssl.so.3.5.5 /lib/libssl.so / lib/libssl.so.1.0.2o /lib/libssl.so.1.1 /lib/libssl.so.1.1.1q /lib/ libssl.so.10 /lib/libssl.so.3 /lib/libssl.so.3.5.5 /usr/lib/ libssl.so /usr/lib/libssl.so.1.0.2o /usr/lib/libssl.so.1.1 /usr/lib/ libssl.so.1.1.1q /usr/lib/libssl.so.10 /usr/lib/libssl.so.3 /usr/ lib/libssl.so.3.5.5
>>
>> The system boots OK, however I would like to resolve the issue.
>>
>> I think that it is due to some old cruft still installed on this server.
>> The source of the requesting libs seems to be
>>      compat-openssl10-1:1.0.2o-9.fc32.x86_64
>> which is ... old ...
>>
>> Maybe this is some old ssl packages that are not needed and can be removed?
>>
>> $ sudo dnf remove compat-openssl10 openssl1.1
>> Package                          Arch Version                          Repository            Size
>> Removing:
>>   compat-openssl10                i686 1:1.0.2o-9.fc32                  fedora             2.6 MiB
>>   compat-openssl10                x86_64 1:1.0.2o-9.fc32                  fedora             2.9 MiB
>>   openssl1.1                      i686 1:1.1.1q-4.fc38                  fedora             3.5 MiB
>>   openssl1.1                      x86_64 1:1.1.1q-4.fc38                  fedora             3.7 MiB
>> Removing dependent packages:
>>   bind-export-libs                x86_64 32:9.11.14-2.fc30                updates            3.3 MiB
>>   libc-client                     x86_64 0:2007f-25.fc32                  fedora             1.5 MiB
>>   virtuoso-opensource             x86_64 2:6.1.6-7.fc22                   <unknown>         13.0 MiB
>> Removing unused dependencies:
>>   openldap-compat                 x86_64 0:2.6.13-1.fc44                  fedora            42.3 KiB
>>
>> Is it safe to remove these? I hope so.
> 
> They're all really old packages except the one compat package that nothing else is using.

Thanks. Of course, but my question was more specific: Is it safe to remove these?
In other words, will the system be OK without these?
I expect that if I later NEED to reinstall these, the packages my very well not be available.

-- 
Eyal at Home ([email protected])
-- 
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
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.