<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 11/15/15 11:09 PM, Kirtikar Kashyap wrote:<br>
<blockquote
cite="mid:CAJ-mzLhx_wLwa2n2GLhxWjc3r88_Nr7LP7FA18J7dxnaeTGYZw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div style="font-size:12.8px">
<div>
<div>
<div>
<div>Hi Adam,<br>
<br>
</div>
Thanks for your prompt response.<br>
<br>
</div>
We installed the hipster version ( OI-hipster-gui-20151003
).<br>
<br>
</div>
However when we try to run the command "sudo pkg install
build-essential", it fails with the error:<br>
<br>
$ <b>sudo pkg install build-essential</b><br>
Creating Plan (Solver setup): \<br>
pkg install: No matching version of
metapackages/build-essential can be installed:<br>
Reject: pkg://<a moz-do-not-send="true"
href="http://openindiana.org/metapackages/build-essential@1.0-2015.0.1.1:20150727T111900Z"
target="_blank">openindiana.org/metapackages/build-essential@1.0-2015.0.1.1:20150727T111900Z</a><br>
Reason: No version matching 'require' dependency
archiver/cabextract can be installed<br>
----------------------------------------<br>
Reject: pkg://<a moz-do-not-send="true"
href="http://openindiana.org/archiver/cabextract@1.4-2014.0.1.0:20151027T055544Z"
target="_blank">openindiana.org/archiver/cabextract@1.4-2014.0.1.0:20151027T055544Z</a><br>
Reason: This version is excluded by installed
incorporation <a class="moz-txt-link-abbreviated" href="mailto:entire@0.5.11-2015.0.2.0">entire@0.5.11-2015.0.2.0</a><br>
</div>
</div>
</div>
</blockquote>
Maybe you need to update OI hipster with pkg update -v first?<br>
Current 'entire' is versioned 2015.0.2.1 so probably you need to pkg
update -v first.<br>
<br>
OI hipster ISOs are not releases per se, where packages are frozen
utill next release or are provided with updates in separate
publisher as it would be for supported release,<br>
hipster is rolling release model used for development and testing
and one can update to newest bits before installing newest packages
from publisher.<br>
<br>
Also there are development zones where one would actually install
development packages in it's own ZFS dataset. <br>
That way one can have multiple independent build environments and
clone and reinstall zones instead of reinstalling main machine and
use networking virtualization between zones and outside world for
infrastructure deployment simulations etc.
<a class="moz-txt-link-freetext" href="http://wiki.openindiana.org/oi/Building+in+zones">http://wiki.openindiana.org/oi/Building+in+zones</a><br>
<br>
</body>
</html>