Child pages
  • Testing /dev to /hipster-2015 or /hipster update

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: typo



Assumption is that you install package(s) form the trusted source publisher (in IPS terminology 'repository' is called a publisher). Do not install packages form untrusted source or from third parties unless you accept the risks of installing third-party binary packages.
Prior installing and testing be advised to make a clone of your current working Boot environment (BE) using beadm command (beadm list, beadm create, beadm activate).
Prior installing and testing be advised make a snapshot of your home directories (/export/home) and other zfs datasets (filesystems) using zfs command. (zfs list, zfs snapshot, zfs rollback).
Prior installing and testing be informed that solaris zones in Openindiana hipster (OI hipster) are linked-images by default and that adding IPS publisher requires adding it in linked-image zones as well.
It is requred that you have appropirate role priviledges for installing packages,using administrative account and commands like pfexec or sudo

We are going to do do update testing, so and we do not need any additional infrastructure at the moment. We will reuse currently unchanged /hipster-2015 repository (at as the nearest to the latest positive update reports from /dev.
There is one more update target, that is OI hipster 20160421 snapshot, but there is at the moment no separate publisher infrastructure for it.

It is more important to confirm at least one positive working update target to test updating in detail, therefore even just testing update to hipster-2015 can be enough
Optional part:
The point of testing is not that you end up with running Hipster in production right now, but, but to go toward updating renewing /dev update , thank you for your testing reports!