Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: trakker on December 13, 2005, 06:01:32 PM
-
a recent attept to run yum update resulted in the following:
....identical dependency loop exceeded
package openssl-perl needs openssl = 0.9.6b-36.7.legacy (not provided)
package openssl-perl needs openssl = 0.9.6b-36.7.legacy (not provided
I then checked with
rpm -qa |grep openssl
which shows
openssl-0.9.6b-36.7.legacy
openssl-perl-0.9.6b-36.7.legacy
what am I doing wrong?
-trakker-
-
anybody?
any ideas?
please help...
-
maybe run a yum clean and try again? yum clean should clear your yum cache.
-
did that thanks,
no change however....
also, when I tried to install the rpm's manually,
yum update still shows the error.....
???
-
Hmm, if you do a rpm -Uvh openssl-new-version
Does rpm give a "version already installed" ?
One option is maybe to rpm -e openssl (uninstall) or a rpm -Uvh --force new-version-of-ssl (Do a force install of the 'new' openssl version)
But I am not sure if this keeps your server in good shape.
-
very hesitant to try anything that might 'break' my server
anybody know if this'll help? or will it cause other problems?
Thanks
-
very hesitant to try anything that might 'break' my server
anybody know if this'll help? or will it cause other problems?
Thanks
Not 100% sure about this, but if you do a force, then a signal-event post-upgrade, then reboot, then your templates will be regenerated and you should be in good shape.
FWIW, the fedorylegacy project just released some updated openssl RPM's due to some security issues. You could download them and see if that corrects your youm update issue, or wait until the maintenance team pushes them to the updates-testing directory.
I have installed them on a 6.5 server, did the post-upgrade, and reboot, and didn't notice any issues on my server. But, I didn't do much other testing. The new RPMS's are named openssl-0.9.6b-39.10.legacy.i386.rpm and openssl-0.9.6b-39.10.legacy.i686.rpm respectfully.
JB
-
very hesitant to try anything that might 'break' my server
anybody know if this'll help? or will it cause other problems?
Thanks
Not 100% sure about this, but if you do a force, then a signal-event post-upgrade, then reboot, then your templates will be regenerated and you should be in good shape.
FWIW, the fedorylegacy project just released some updated openssl RPM's due to some security issues. You could download them and see if that corrects your youm update issue, or wait until the maintenance team pushes them to the updates-testing directory.
I have installed them on a 6.5 server, did the post-upgrade, and reboot, and didn't notice any issues on my server. But, I didn't do much other testing. The new RPMS's are named openssl-0.9.6b-39.10.legacy.i386.rpm and openssl-0.9.6b-39.10.legacy.i686.rpm respectfully.
JB
-
The latest Fedora Legacy openssl packages will be released by the maintenance team into updates-testing-common soon.
-
I tried the forced update on my system, but rpm reports failed dependencies:
openssl = 0.9.6m-1es1 is needed by openssl-devel-0.9.6m-1es1
openssl = 0.9.6m-1es1 is needed by openssl-perl-0.9.6m-1es1
So, it didn't ruin my system, but yum isn't happy...
-
I tried the forced update on my system, but rpm reports failed dependencies:
openssl = 0.9.6m-1es1 is needed by openssl-devel-0.9.6m-1es1
openssl = 0.9.6m-1es1 is needed by openssl-perl-0.9.6m-1es1
So, it didn't ruin my system, but yum isn't happy...
So where did the above 2 rpm's come from? On a default install openssl-devel and openssl-perl are not installed, this would have been something you installed yourself, or via someone elses script. With that said. a search on this site, shows that you have the infamous smeplus script installed. That's where the other 2 rpms' come from. This would have been good information to give in your initial post. So, it's up to you now, either you leave it like it is and continue to let yum groan, or remove the two or maybe three rpm's and possibly have to manually update openssl with the version that is in updates-testing.
JB
-
This would have been good information to give in your initial post.JB
Hi JB, I (meneer) am not the initial poster, I just happened to have run into the same problem ;)
I'll just drop the openssl stuff and report back.
-
Ran the smeplus script to get rid of smeplus. Looked fine, a few errors, but nothing special.
It didn't fix the openssl errors, though.
rpm force the new update results in the same dependencies. removing openssl seems not possible (lots of rpm dependencies reported).
-
Ran the smeplus script to get rid of smeplus. Looked fine, a few errors, but nothing special.
It didn't fix the openssl errors, though.
Obviously the smeplus script does not get rid of all of "smeplus".
Did you remove the unnecessary openssl-devel and openssl-perl rpms as recommended?
rpm force the new update results in the same dependencies.
Only use --nodeps and --force when you understand exactly why you are doing so. rpm is trying to protect your system. You should listen to what it is saying.
-
removing both rpm's fixes the problem. thanx!