<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">http://openindiana.org/pipermail/userland-team/2013-August/000261.html</A><BR># <A href="http://comments.gmane.org/gmane.os.openindiana.devel/2906">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">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 <alp@rsu.ru><BR>Дата: Thursday, April 24, 2014 13:39<BR>Тема: Re: [oi-dev] Hipster and custom illumos-gate<BR>Кому (To): OpenIndiana Developer mailing list <oi-dev@openindiana.org><BR>Копия (Cc): Jim Klimov <jim@cos.ru>, Discussion list for OpenIndiana <openindiana-discuss@openindiana.org><BR><BR>> <BR>> Hi, Jim.<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>> I think you should set PKGVERS_BRANCH to something greater than <BR>> 2014.0.N.N (e.g. 2014.1.0.0).<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>> I tested the following patch from David: <BR>> http://www.ulx.cc/assets/source/104_interdiff.diff<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>| +7-903-7705859 (cellular) mailto:jimklimov@cos.ru | <BR>| CC:admin@cos.ru,jimklimov@gmail.com | <BR>+============================================================+ <BR>| () ascii ribbon campaign - against html mail | <BR>| /\ - against microsoft attachments | <BR>+============================================================+ <BR><BR></DIV>
<DIV><BR><BR></DIV>