Hi Paul,

Looks like the Cloud Provider is using a couple of months old build:

[root@dev01 ~]# uname -a
SunOS dev01 5.11 joyent_20161013T025521Z i86pc i386 i86pc Solaris

Regards
--jm

On 11 March 2017 at 10:14, Paul Sture <[email protected]> wrote:

> On 11 Mar 2017, at 8:55, Jacques Marneweck wrote:
>
> Hi Guys,
>>
>> On a fresh 2016Q4 zone I did "pkgin fug":
>>
>
> Which image did you use, and for completeness, what version is the GZ
> using?
>
> (The output of 'cat /etc/motd' will provide that for the GZ version.)
>
> [root@dev01 ~]# pkgin fug
>> reading local summary...
>> processing local summary...
>> pkg_summary.xz
>>                                                                  100%
>> 2078KB
>>     4KB/s 605.7KB/s   00:04
>> calculating dependencies... done.
>>
>> 2 packages to be upgraded:
>>
>> nodejs-7.2.1 openssl-1.0.2jnb1
>>
>> 2 packages to be installed (17M to download, -59K to install):
>>
>> openssl-1.0.2k nodejs-7.5.0
>>
>> proceed ? [Y/n] y
>> downloading packages...
>> openssl-1.0.2k.tgz
>>                                                                  100%
>> 5661KB
>>     1KB/s 113.2KB/s   00:20
>> nodejs-7.5.0.tgz
>>                                                                    100%
>> 11MB
>>     3KB/s 511.1KB/s   00:36
>> removing packages to be upgraded...
>> removing nodejs-7.2.1...
>> removing openssl-1.0.2jnb1...
>> ============================================================
>> ===============
>> The following directories are no longer being used by
>> openssl-1.0.2jnb1,
>> and they can be removed if no other packages are using them:
>>
>> /opt/local/etc/openssl/certs
>>
>> ============================================================
>> ===============
>> pkg_install warnings: 0, errors: 0
>> installing packages...
>> installing openssl-1.0.2k...
>> installing nodejs-7.5.0...
>> pkg_install warnings: 0, errors: 0
>> reading local summary...
>> processing local summary...
>>
>> then I try and use pkgin again I get:
>>
>> [root@dev01 ~]# pkgin in git
>>     so.1: pkgin: fatal: libcrypto.so.1.0.0: open failed: No such file
>> or
>> directory
>> Killed
>>
>> So I try and figure out if this a borked openssl issue:
>>
>> [root@dev01 ~]# wget
>>    so.1: wget: fatal: libssl.so.1.0.0: open failed: No such file or
>> directory
>> Killed
>>
>> [root@dev01 ~]# pkg_info | grep openssl
>>     so.1: pkg_info: fatal: libssl.so.1.0.0: open failed: No such file
>> or
>> directory
>>
>> Any ideas?
>>
>> Regards
>> --jm
>>
>> --
>> Jacques Marneweck
>> http://www.powertrip.co.za/
>> http://www.powertrip.co.za/blog/
>> http://www.ataris.co.za/
>>
>>
> 
> 



-- 
Jacques Marneweck
http://www.powertrip.co.za/
http://www.powertrip.co.za/blog/
http://www.ataris.co.za/



-------------------------------------------
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

Reply via email to