headers
cpb | 7 Feb 2012 10:50

iputils installorder note

Hello, I just wanted to mention a small problem I had updating Owl in-place
from Owl-3.0-stable (around 2011-09-11 I think) to Owl-current. (using ROOT=/)

--- snip ---
error: Failed dependencies:
	libcrypto.so.5()(64bit) is needed by (installed) iputils-s20101006-owl1
21:15:31: Failed openssl openssl-devel openssl-perl mtree openssh openssh-clients openssh-server
d:openssh-blacklist elinks nmap ncat nping mutt openntpd readline readline-devel bc gnupg gdb lftp
21:15:31: Installing iputils traceroute (iputils-s20101006-owl1.x86_64.rpm traceroute-1.0.3-owl3.x86_64.rpm)
error: Failed dependencies:
	libcrypto.so.10()(64bit) is needed by iputils-s20101006-owl1
21:15:31: Failed iputils traceroute
--- snip ---

It seems my Owl-stable from that time had an iputils that needed the old
libcrypto.so.5, so it blocked the new one (so.10) from coming in. When I
removed iputils manually, I could run the "rpm -Uvh --force openssl..." step
OK. (I don't truly understand RPM feature dependencies...)

I believe that if the iputils package were part of the big "openssl..." step,
there would not have been any problem. The following post from last year
mentioned both the (new) dependency of iputils on libcrypto, and a consequent
change to the buildorder (iputils AFTER openssl):

http://www.openwall.com/lists/owl-dev/2011/04/06/2

That change allowed upgrade from no-crypto-deps to with-crypto-deps, but it did
not allow upgrade from with-old-crypto-deps to with-new-crypto-deps (again, if
I understand correctly).
(Continue reading)

Permalink | Reply | 1 comment |
headers
Solar Designer | 26 Feb 2012 18:53
Favicon

Re: iputils installorder note

Chris,

On Mon, Feb 06, 2012 at 11:50:32PM -1000, cpb <at> vps.log2.net wrote:
> Hello, I just wanted to mention a small problem I had updating Owl in-place
> from Owl-3.0-stable (around 2011-09-11 I think) to Owl-current. (using ROOT=/)
...
> I think the thing to do is throw iputils into that long list of packages
> that begins with openssl.

I've just reproduced the problem and made that change to Owl-current
(not yet public, but will be soon).  Thank you for reporting this!

Alexander
Permalink | Reply | 0 comments |

Gmane