Yes, I have tried it. It fails because libcrypto.so.0.9.7 isn't in the RPM database, even though it exists. It appears that rebuilding this RPM (and any others like it) from source will be my best option. Chris St. Pierre Unix Systems Administrator Nebraska Wesleyan University On Thu, 29 Jun 2006, McDougall, Marshall (FSH) wrote: >Why do you say your rpm install would fail? It should find the library >and carry on accordingly. Have you tried it? > >-----Original Message----- >From: redhat-list-bounces@xxxxxxxxxx >[mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Chris St. Pierre >Sent: Thursday, June 29, 2006 1:54 PM >To: General Red Hat Linux discussion list >Subject: RE: libcrypto names > >While that would functionally work, my RPM install would still fail -- >unless I use --force, I suppose. That's ugly, though, as we don't >have --force written into any of our scripts, crontabs, Cfengine >rules, etc., and don't want to. I'm looking for a way to do this >"politely," I guess. > >Chris St. Pierre >Unix Systems Administrator >Nebraska Wesleyan University > >On Thu, 29 Jun 2006, McDougall, Marshall (FSH) wrote: > >>If they are indeed the same package, just create a soft link to your >>currently installed lib but name it with the other naming standard ala: >> >> cd /lib >> ln -s ./libcrypto.so.0.9.7 ./libcrypto.so.4 >> >>Regards, Marshall >> >>-----Original Message----- >>From: redhat-list-bounces@xxxxxxxxxx >>[mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Chris St. Pierre >>Sent: Thursday, June 29, 2006 1:04 PM >>To: redhat-list@xxxxxxxxxx >>Subject: libcrypto names >> >>I've got an RPM that requires libcrypto.so.0.9.7. The problem is that >>RHEL's OpenSSL package provides libcrypto.so.4. Some googling >>suggests that these are, in fact, the same library, just named >>differently: the .4 is an RHEL thing, while the .0.9.7 is the OpenSSL >>version. (The RPM is packaged without a specific distro in mind.) >>How can I solve this dependency, preferably without installing a >>non-RHEL OpenSSL package? >> >>The only thing I can think of is to create an RPM package that just >>installs a symlink to libcrypto.so.4 under libcrypto.so.0.9.7, and >>reports to the RPM database that this package provides >>libcrypto.so.0.9.7. This seems like overkill, and I'm also a total >>noob when it comes to making my own RPMs. Other ideas? >> >>Chris St. Pierre >>Unix Systems Administrator >>Nebraska Wesleyan University >> >>-- >>redhat-list mailing list >>unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe >>https://www.redhat.com/mailman/listinfo/redhat-list >> >>-- >>redhat-list mailing list >>unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe >>https://www.redhat.com/mailman/listinfo/redhat-list >> > >-- >redhat-list mailing list >unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe >https://www.redhat.com/mailman/listinfo/redhat-list > >-- >redhat-list mailing list >unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe >https://www.redhat.com/mailman/listinfo/redhat-list > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
