<div dir="ltr">Try doing:<div><br></div><div>pkg set-publisher --non-sticky <a href="http://openindiana.org">openindiana.org</a><br></div><div><br></div><div>to allow packages that originally came from <a href="http://openindiana.org">openindiana.org</a> repo to be upgraded with packages from a different repo.</div>
<div><br></div><div><div>Cheers,</div><div><br></div><div>Andrzej</div><div><br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 24 April 2014 16:53, Jim Klimov <span dir="ltr"><<a href="mailto:jim@cos.ru" target="_blank">jim@cos.ru</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>So... based on this suggestion, the hipster illumos-gate makefile, and some earlier list posts, I came up with this change to my illumos.sh script:<br>
<br># To enable upgrades over `pkg info osnet-incorporation | grep Branch:`<br># Branch: 0.151.1<br>#export ONNV_BUILDNUM=152<br>#export ONNV_BUILDNUM=151.1.100<br># <a href="http://openindiana.org/pipermail/userland-team/2013-August/000261.html" target="_blank">http://openindiana.org/pipermail/userland-team/2013-August/000261.html</a><br>
# <a href="http://comments.gmane.org/gmane.os.openindiana.devel/2906" target="_blank">http://comments.gmane.org/gmane.os.openindiana.devel/2906</a><br>export PKGVERS_BRANCH=3014.0.4.24<br>export BRANCHID=3014.0.4.24<br></div>
<div>Some 47 minutes later I've got an incrementally-rebuilt repository which cheerfully includes packages like</div>
<div> </div>
<div>
<table summary="A list of packages available in the repository
restricted by the specified listing criteria.">
<tbody>
<tr>
<td scope="row"><a title="Package Information Summary" href="http://jimoi:8151/on-nightly/info/0/pkg%3A%2F%2Fon-nightly%2FSUNWcs%400.5.11%2C5.11-3014.0.4.24%3A20140424T130517Z" target="_blank">SUNWcs</a> </td>
<td>0.5.11-3014.0.4.24:20140424T130517Z</td></tr></tbody></table></div>
<div> </div>
<div>However, a "pkg -R /a update" still insists on downloading new hipster patches with the 0.5.11-2014.0.1.14459:20140423T191935Z versions from the internet, rather than quickly installing the newer and higher-versioned local equivalents. This happens also if I use "-g" to specify a repo explicitly, and when I use a file-based repo instead of its http service.</div>
<div> </div>
<div>I guess nowadays IPS tries to update same-named packages using the same repo they were installed from specifically to avoid conflicts like these? How should I go about overriding that reasonable failsafe mechanism? ;)</div>
<div> </div>
<div>Thanks,</div>
<div>//Jim<br><br>----- Исходное сообщение -----<br>От: Alexander Pyhalov <<a href="mailto:alp@rsu.ru" target="_blank">alp@rsu.ru</a>><br>Дата: Thursday, April 24, 2014 13:39<br>Тема: Re: [oi-dev] Hipster and custom illumos-gate<br>
Кому (To): OpenIndiana Developer mailing list <<a href="mailto:oi-dev@openindiana.org" target="_blank">oi-dev@openindiana.org</a>><br>Копия (Cc): Jim Klimov <<a href="mailto:jim@cos.ru" target="_blank">jim@cos.ru</a>>, Discussion list for OpenIndiana <<a href="mailto:openindiana-discuss@openindiana.org" target="_blank">openindiana-discuss@openindiana.org</a>><br>
<br>> <br>> Hi, Jim.<div class=""><br>> <br>> On 04/24/2014 02:45, Jim Klimov wrote:<br>> > After completing a build I am suddenly stuck <br>> trying to install<br>> > the newer illumos-gate packages into a new BE: their versioning<br>
> > (0.151.1.100 per my arbitrarily big choice) is less than Hipster's<br>> > (2014.*, without even a leading zero which is auto-prepended <br>> to the<br>> > values I provide in illumos.sh)... Should I have to somehow enforce<br>
> > larger 2014.* version numbers, or is there a way (onu?) to override<br>> > existing packages and force installation of their "namesakes" from<br>> > the on-nightly repository regardless of the version numbers?<br>
</div>> I think you should set PKGVERS_BRANCH to something greater than <br>> 2014.0.N.N (e.g. 2014.1.0.0).<div class=""><br>> <br>> ><br>> > Also, leaping a bit ahead: would/should KVM <br>> work in Hipster out<br>
> > of the box, including the case when Hipster itself is virtualized<br>> > by a hypervisor, or would I need to compile some other patches<br>> > into my illumos-gate? Specifically, I am interested in software<br>
> > emulation for the VM anyway (ARM Linux via QEMU)?.. And also, did<br>> > anyone try (and succeed) to set up cross-compilation of Linux ARM<br>> > programs running the process under illumos/OI/Hipster, whether in<br>
> > native illumos zones or in lx-branded ones, or should I look forward<br>> > to necessarily running a Linux VM as well for that task?<br>> ><br>> <br></div>> I tested the following patch from David: <br>
> <a href="http://www.ulx.cc/assets/source/104_interdiff.diff" target="_blank">http://www.ulx.cc/assets/source/104_interdiff.diff</a><br>> It worked for me, but if I understand correctly it's just a <br>> restoration <br>
> of Sun lx/lx26 work. I think you could easily use <br>> components/illumos/illumos-gate component from oi-userland, but <br>> you have <br>> to apply necessary patches by hand. I'm going to add <br>> patching support <br>
> (I mean usual oi-userland prep mechanism) for this component in <br>> near <br>> future. If you are going to use illumos-gate component, you'd <br>> better to <br>> bump BRANCHID so that your packages would be preferred.<br>
> <br>> -- <br>> Best regards,<br>> Alexander Pyhalov,<br>> system administrator of Computer Center of Southern Federal University</div>
<div> </div>
<div> </div>
<div align="left">-- <br><br>+============================================================+ <br>| | <br>| Климов Евгений, Jim Klimov | <br>
| технический директор CTO | <br>| ЗАО "ЦОС и ВТ" JSC COS&HT | <br>| | <br>| <a href="tel:%2B7-903-7705859" value="+79037705859" target="_blank">+7-903-7705859</a> (cellular) mailto:<a href="mailto:jimklimov@cos.ru" target="_blank">jimklimov@cos.ru</a> | <br>
| <a href="mailto:CC%3Aadmin@cos.ru" target="_blank">CC:admin@cos.ru</a>,<a href="mailto:jimklimov@gmail.com" target="_blank">jimklimov@gmail.com</a> | <br>+============================================================+ <br>
| () ascii ribbon campaign - against html mail | <br>| /\ - against microsoft attachments | <br>+============================================================+ <br><br></div>
<div><br><br></div>
<br>_______________________________________________<br>
oi-dev mailing list<br>
<a href="mailto:oi-dev@openindiana.org">oi-dev@openindiana.org</a><br>
<a href="http://openindiana.org/mailman/listinfo/oi-dev" target="_blank">http://openindiana.org/mailman/listinfo/oi-dev</a><br></blockquote></div><br></div>