Hi Nikola Because OI hipster is using vanilla illumos-gate, illumos related bugs can be opened directly against upstream illumos project.
I am not sure what to do about OI hipster specific bugs yet. OI hipster is a fork of the /dev branch. OI project in redmine on illumos.org refers to the /dev branch itself. Maybe, at least for now, post your issues to the oi-dev mailing list? I was not able to reproduce your VirtualBox problem on my machine here. Latest VirtualBox and zoneaccess service appears to be working on fully updated system here: http://linux01.everycity.co.uk/~aszeszo/skitched-20130629-190412.png At least for now, the idea behind OI hipster is for it to remain a rolling release. Sometimes things will break. But thanks to BEs and easy contribution process things can be fixed or rolled back quickly. illumos-gate updates in OI hipster are fully automatic and there is no OI specific testing done prior to integrating the packages in the /hipster repo. Cheers, Andrzej On 29 June 2013 10:37, Nikola M. <[email protected]> wrote: > On 06/20/13 01:10 AM, Andrzej Szeszo wrote: >> Hi All >> >> I have configured Jenkins job which is continuously building and >> publishing vanilla illumos-gate packages to the /hipster repo. >> >> Jenkins is actually rebuilding this component: >> >> https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/illumos/illumos-gate >> >> The big change is that illumos-gate is being built with patched gcc >> 4.4.4. Previous packages were built using Studio. > Hi :) > Where do we post bugs about this updated illumos-gate? Or where to post > bug for Hipster itself? > Does bug reports for Hipster need to be separate from Openindiana /dev > (that a8 Hipster will be) > > I have virtualbox zoneaccess service fails to load after version > illumos-861bfc8. That is the last one that works for zoneaccess starting > in OI-Hipster with Virtualbox 4.2.14r86644 . > Does this coincide with switching to GCC or is unrelated? > > Can we have updated kernel (illumos-gate) and the rest of the system > updated separately so packages and illumos-gate could be tested > independently, or it is better to have them mall updated and live as one > big updating family? > Is there some testing procedures for illumos-gate before pushing it up > to Hipster and prior releasing it to /dev ? > N.M. _______________________________________________ oi-dev mailing list [email protected] http://openindiana.org/mailman/listinfo/oi-dev
