Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Apr 2012 08:15:07 -0400
From:      Jerry <jerry@seibercom.net>
To:        freebsd-ports@freebsd.org
Subject:   Re: security/openssl moved from libssl.so.7 to libssl.so.8 on 2012/04/11
Message-ID:  <20120417081507.6afbce94@scorpio>
In-Reply-To: <4F8D0493.5090600@wagsky.com>
References:  <4F8D0493.5090600@wagsky.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 16 Apr 2012 22:50:11 -0700
Jeff Kletsky articulated:

> I was pretty surprised today when I, after
> checking /usr/ports/UPDATING, updated security/openssl to find that a
> huge number of software bits no longer functioned, looking (in vain)
> for libssl.so.7
> 
> Apparently the version was bumped
> 
> --- ports/security/openssl/Makefile	2012/03/15 06:15:33
> 1.184 +++ ports/security/openssl/Makefile	2012/04/11
> 21:06:35	1.185
> 
> -OPENSSL_SHLIBVER?=	7
> +OPENSSL_SHLIBVER?=	8
> 
> but there was no notification in UPDATING that I could see.
> 
> The first hint of problems was postfix failing to start, and things
> got worse from there.
> 
> Forcibly removing openssl and reinstalling it from the RELEASE
> packages got me up and going again, but this was a bit of a surprise.
> 
> For i386 -- 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9.0-release/security/openssl-1.0.0_7.tbz
> 
> Should libssl.so.7 have been retained somehow?
> 
> I upgraded using portmaster, it that provides any clues as to why it
> was or wasn't.

This is a case where "portmanager" just worked for me.

	portmanager -u -l -y -p

It updated openssl and forced a rebuild of all ports that depended on
it. I rebooted the system and everything works fine.

HTH

-- 
Jerry ♔

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__________________________________________________________________




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120417081507.6afbce94>