Thanks for the heads up, my stuff auto upgrade every friday at 19.00.
I just did an upgrade of openssl only everywhere to avoid breakage!
On 2017-01-27 15:42, Jonathan Perkin wrote:
To those of you running 16.4.0 images, there is an issue introduced
with the recent OpenSSL 1.0.2k update where a 'pkgin upgrade' will
render the pkg_install tools unusable, due to removing the previous
openssl package prior to installing the update.
This is completely my fault as I forgot to merge in a patch which
ensures that pkg_install statically links against openssl.
In the short term:
- If you wish to upgrade your 16.4.0 image, perform:
$ pkg_add -U openssl
first. This will upgrade openssl in place, and then the remaining
upgrades can be handled normally via pkgin.
- If you have already broken a system with 'pkgin upgrade', things
are a little more complicated. For now probably the simplest fix,
if very ugly, is (for x86_64):
$ cp /lib/64/libsunw_crypto.so.1.0.0 libcrypto.so.1.0.0
$ cp /lib/64/libsunw_ssl.so.1.0.0 libssl.so.1.0.0
$ LD_LIBRARY_PATH=. pkg_add
http://pkgsrc.joyent.com/packages/SmartOS/2016Q4/x86_64/All/openssl-1.0.2k.tgz
$ rm -f libcrypto.so.1.0.0 libssl.so.1.0.0
If using i386/multiarch remove the '/64' path and change the URL
accordingly.
Longer term I will put out 16.4.1 images which correctly build the
pkg_install package statically linked against OpenSSL, and add QA to
our build process to ensure we can't ship broken packages again.
Sorry for the mess,
---
~ sjorge
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com
