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:
# To enable upgrades over `pkg info osnet-incorporation | grep Branch:` # Branch: 0.151.1 #export ONNV_BUILDNUM=152 #export ONNV_BUILDNUM=151.1.100 # http://openindiana.org/pipermail/userland-team/2013-August/000261.html # http://comments.gmane.org/gmane.os.openindiana.devel/2906 export PKGVERS_BRANCH=3014.0.4.24 export BRANCHID=3014.0.4.24 Some 47 minutes later I've got an incrementally-rebuilt repository which cheerfully includes packages like SUNWcs 0.5.11-3014.0.4.24:20140424T130517Z 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. 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? ;) Thanks, //Jim ----- Исходное сообщение ----- От: Alexander Pyhalov <[email protected]> Дата: Thursday, April 24, 2014 13:39 Тема: Re: [oi-dev] Hipster and custom illumos-gate Кому (To): OpenIndiana Developer mailing list <[email protected]> Копия (Cc): Jim Klimov <[email protected]>, Discussion list for OpenIndiana <[email protected]> > > Hi, Jim. > > On 04/24/2014 02:45, Jim Klimov wrote: > > After completing a build I am suddenly stuck > trying to install > > the newer illumos-gate packages into a new BE: their versioning > > (0.151.1.100 per my arbitrarily big choice) is less than Hipster's > > (2014.*, without even a leading zero which is auto-prepended > to the > > values I provide in illumos.sh)... Should I have to somehow enforce > > larger 2014.* version numbers, or is there a way (onu?) to override > > existing packages and force installation of their "namesakes" from > > the on-nightly repository regardless of the version numbers? > I think you should set PKGVERS_BRANCH to something greater than > 2014.0.N.N (e.g. 2014.1.0.0). > > > > > Also, leaping a bit ahead: would/should KVM > work in Hipster out > > of the box, including the case when Hipster itself is virtualized > > by a hypervisor, or would I need to compile some other patches > > into my illumos-gate? Specifically, I am interested in software > > emulation for the VM anyway (ARM Linux via QEMU)?.. And also, did > > anyone try (and succeed) to set up cross-compilation of Linux ARM > > programs running the process under illumos/OI/Hipster, whether in > > native illumos zones or in lx-branded ones, or should I look forward > > to necessarily running a Linux VM as well for that task? > > > > I tested the following patch from David: > http://www.ulx.cc/assets/source/104_interdiff.diff > It worked for me, but if I understand correctly it's just a > restoration > of Sun lx/lx26 work. I think you could easily use > components/illumos/illumos-gate component from oi-userland, but > you have > to apply necessary patches by hand. I'm going to add > patching support > (I mean usual oi-userland prep mechanism) for this component in > near > future. If you are going to use illumos-gate component, you'd > better to > bump BRANCHID so that your packages would be preferred. > > -- > Best regards, > Alexander Pyhalov, > system administrator of Computer Center of Southern Federal University -- +============================================================+ | | | Климов Евгений, Jim Klimov | | технический директор CTO | | ЗАО "ЦОС и ВТ" JSC COS&HT | | | | +7-903-7705859 (cellular) mailto:[email protected] | | CC:[email protected],[email protected] | +============================================================+ | () ascii ribbon campaign - against html mail | | /\ - against microsoft attachments | +============================================================+
_______________________________________________ oi-dev mailing list [email protected] http://openindiana.org/mailman/listinfo/oi-dev
