svn commit: r217562 - in stable/7/secure/lib: libcrypto libssl
John Baldwin
jhb at freebsd.org
Wed Jan 19 15:26:05 UTC 2011
On Wednesday, January 19, 2011 8:30:16 am Erwin Lansing wrote:
> On Wed, Jan 19, 2011 at 08:07:46AM -0500, John Baldwin wrote:
> > On Tuesday, January 18, 2011 5:19:55 pm Simon L. Nielsen wrote:
> > > Author: simon
> > > Date: Tue Jan 18 22:19:55 2011
> > > New Revision: 217562
> > > URL: http://svn.freebsd.org/changeset/base/217562
> > >
> > > Log:
> > > Decrease the libcrypto and libssl shared object version numbers from 6
> > > to 5. They were accidentally bumped in r215997 (on 2010-11-28) with the
> > > merge of OpenSSL 0.9.8p, but unfortunately this was not caught until
> > > now.
> > >
> > > Also add compat links for libcrypto.so.6 / libssl.so.6 (pointing to
> > > their .5 counterparts) in case any users have compiled any third party
> > > during the time stable/7 (and releng/7.4) were broken.
> > >
> > > This is deemed the last poor of bad options. Had the number bump not
> > > been reverted binary packages for stable/7 would not have worked on the
> > > still supported 7.3 and 7.1 releases.
> >
> > Erm, shouldn't the packages for 7-stable be built against the 7.0 ABI instead
> > (and I thought this change was already made)? We've only supported backwards
> > compat, not forwards compat.
> >
> Oldest supported by the security officer, currently 7.1-RELEASE-p16 to
> be exact, but yes. Those are built against libcrypto.so.5, which of
> course won't work on 7.4 with libcrypto.so.6, hence the above rollback
> with an added symlink for those people that already built binaries
> themselves against libcrypto.so.6.
Ah, as there is no so.5 on a clean 7.4 system. Nevermind me then. The
symlinks are certainly fine regardless, my only question was about the
base the packages were being built against.
--
John Baldwin
More information about the svn-src-stable-7
mailing list