[OpenIndiana-discuss] fresh hipster install important tool no workee

[Jim Klimov]

25 октября 2016 г. 20:00:57 CEST, Jonathan Adams <t12nslookup at gmail.com> пишет:
>Hi pkg needs a lot of memory, depending on the size of the repository
>that
>it is updating from ... Are you sure you gave your virtual machine
>enough
>memory?
>
>Jon
>
>On 25 Oct 2016 18:44, "Harry Putnam" <reader at newsguy.com> wrote:
>
>> Just installed hipster in vbox vm on a Solaris (openindiana) host.
>>
>> I used this iso: oi-hipster-gui-20160421.iso
>>
>> It's been disappointing.
>>
>> Seems that updating to latest image is not possible:
>>
>> A command like `pkg image-update -v'
>>
>> Just sets and never returns or shows any activity. But it is burning
>> up all resources.
>>
>> If I go to a differnt xtem and try to do anything, the host stalls
>> completely and no activity is possible at all.
>>
>> Can't run pkg publish right now to show the output here as things are
>> totally stalled, but publisher is set to:
>>    http://pkg.openindiana.org/hipster
>>
>> Had a similar bad experience trying to install the vbox guest tools.
>> At the end of the process it stalls with .. updating .. boot ..
>something?
>>
>> Am I wasting my time with the mentioned iso... is there a more recent
>> one?
>>
>> Are folks generally able to get a working system straight away from
>> the iso mentioned above?
>>
>>
>> _______________________________________________
>> openindiana-discuss mailing list
>> openindiana-discuss at openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>
>_______________________________________________
>openindiana-discuss mailing list
>openindiana-discuss at openindiana.org
>https://openindiana.org/mailman/listinfo/openindiana-discuss

What I gather from looking at IRC discussions, this situation may be due to a recent update of pkg itself, along with deprecation of python-2.6 which older pkg depended on (so binary parts were recompiled - against software not present or sufficient in the older release). Ways to fix this or at least document a workaround for upgrades are being discussed over past days, hopefully some solution will be provided before the 2016.10 snapshot (or will it be 2016.11?) which will be the next "official" ISO release.

Also there was a hiccup for some systems that had an unmodified /etc/ssh/sshd_config - adding an empty line to the file sufficed as a workaround to pass the deprecation of sunssh and migrate to openssh.

Hope this helps,
Jim
--
Typos courtesy of K-9 Mail on my Samsung Android