Skip to end of metadata
Go to start of metadata

What is Hipster?

Ref: 2017.10 Release notes

Hipster is a codename for rapidly moving development branch of OpenIndiana and the development branch from which major release snapshots are made. Changes go into an ISO snapshots at a slower pace and with the general assumption that they have first been tested from the Hipster IPS package repository. This is still a development branch and, at any given time, the packages from OpenIndiana's Hipster IPS repository may or may not be suitable for general use. It is simply another engineering development track, not a resource for end-users. Users who do not have the resources to perform testing should instead run their own tested ISO snapshot of Openindiana Hipster.

Those interested in tracking or contributing to the OpenIndiana's Hipster development process, especially as it relates to the next release of Openindiana Hipster, should consider following the mailing lists.

It is inevitable that there would be bugs sometimes, that were not apparent in the oi-dev team. For this reason, one should not just conduct an entire upgrade progress on an production system without reading package release notes or docs.

It is very important not to update any production servers or desktops/workstations without thoroughly testing software packages or drivers in a development or testing environment.

Releasing every ISO snapshot will be announced via mailing list and Twitter.

How to switch to the Hipster branch?

Before considering using Hipster, please read the statement below.

Unstable version

Even though, Hipster might contain some newer packages it is generally not advised for mission critical servers or fully functioning production desktop. Things might break and could cause system/service downtime. Do upgrade only if you know what you are doing. You have been warned!

To switch to the Hipster branch on an existing /dev installation, do the following:

  • Create backup. Really.
  • Uninstall all packages from publisher
  • pkg set-publisher -g -G
  • pkg unset-publisher
  • pkg refresh --full
  • pkg update --be-name oi-hipster -nv 2>&1|less - look how it is going to work
  • pkg update --be-name oi-hipster -v
  • boot new BE and check that you don't have packages with '*0.151.1.*' branch versions installed (check that pkg list |grep '0\.151\.1\.' output is empty)
  • ensure that you have userland incorporation and entire installed (pkg install userland-incorporation entire@0.5.11-2015.0.3.0 )

On switching from old /dev Openindiana to /Hipster, also see: Testing /dev to /hipster-2015 or /hipster update

  • No labels


  1. Hi,

    would be nice to present /hipster a bit better..

    For example, during latest update, i have spotted (by pure coincidence):

    Changed mediators:
      mediator automake:
               version: 1.10 (system default) -> 1.11 (system default)
      mediator mysql:
               version: 5.5 (system default) -> 5.6 (system default)
        implementation: mariadb (system default) -> percona-server (system default)

    So, there are probably other cases which maybe wasn't noted (for example OAMP components versions; OAMP=OpenIndiana Apache MySQL PHP)


    1. Mysql version is guarded by mediator. I consider default mysql is a version which is used by default while building packages. This is still Mariadb 5.5. You can still do "pkg set-mediator  -I mariadb -V 5.5 mysql". Unfortunately, IPS selects newer versions for mediators by default. If we change default version which we use while building packages, I'll add comment on OI /hipster changelog. One interesting question here is why percona-server-5.6 was installed on system update.

  2. Hi,

    just tried latest change:

    $ pfexec pkg set-publisher -p
    pkg set-publisher: http protocol error: code: 500 reason: Internal Server Error
    URL: ''

    So, reverted back...


    1. Hi,

      Thanks to Jonathan Adams, (see this was fixed with this change (I have added search first switch)

      $ pfexec pkg set-publisher -O --search-first

      I have got same error, but job was done! So there is difference between '-p' and '-O' switch