Description of problem:
Several applications -- such as cupsd, httpd, and sendmail -- are linked against
both version 2 /and/ version 3 of libcom_err.so. Only libcom_err.so.2 comes in
Fedora test2 (0.94), in the e2fsprogs package.
Version-Release number of selected component (if applicable):
Always (as far as I can tell)
Steps to Reproduce:
1. I upgraded from stock RH9 to Fedora Core test 2 (0.94)
2. Reboot into fedora system
httpd, cupsd, and sendmail did not start (missing shared library).
They should have started.
Doing an `ldd <APP>`, where <APP> is either cupsd, httpd, or sendmail shows that
all three daemons are linked against both libcom_err.so.2 and libcom_err.so.3.
I only see one version of libcom_err being pulled in on my box with that version
of sendmail and cups. It appears your upgrade didn't upgrade something correctly?
What library is bringing in the wrong libcomm_err dep?
Which version of libcom_err is on your box? Also, keep in mind that I upgraded
directly from RH9 to Fedora test2. Most of the binaries in /usr/sbin are linked
against both v2 and v3 of libcom_err. I'm not seeing any packages that depend
on libcom_err v3, but several that depend on v2.
I'd be more specific, but I don't have the laptop in front of me right now. I'm
at work and I left it at home this morning.
I only have .2 on my install here.
openssl-0.9.7a-20 depends on libcom_err.so.3, but anaconda/rpm/whatever didn't
install any package that provides libcom_err.so.3. Now that I'm actually
learning to read directions, I check my /root/upgrade.log and found lines like
Upgrade Dependency: Needs (('openssl', '0.9.7a', '20'), ('libcom_err.so.3',
None), 0, None, 0), automatically added.
There's another line like that for pine 4.44-19.90.0
This problem occurs when upgrading a RH9.0 system that has an updated version of
openssl from the RH9.0 errate is 0.9.7a-20 (and depends on libcom_err.so.3) is
not upgraded with the version from Fedora core 0.9.7a-17 (linked against the
correct version of the library).
You can fix a broken system by upgrading with --oldpackage using the version of
OpenSSH supplied with Fedora. THIS WILL EFFECTIVELY REMOVE A SECURITY PATCH.
The pine issue is a bit of a red herring - pine has been removed from Fedora so
its breakage is not supprising.
I did the update with --oldpackage and it worked.
Current openssl for Cambridge is 0.9.7a-23.
*** Bug 106842 has been marked as a duplicate of this bug. ***