Quick links to IPS Repositories

  • Posted on: 11 January 2020
  • By: tomww

(seriously, do *not* mirror these repositories - instead help me build a release repo which is HA and can be mirrored)

If you want to install extra packages for Solaris 11, OpenIndiana or OmniOSce, then this is the place telling you how to configure the package repositories on your system. To see the available packages in your Browser go to section "Browse", to configure te IPS repository go to section "Publisher" and select the one matching your Operating System. And in any case you have questions, then please ask me on twitter @sfepacakges or by email on sfepackages at g mail dot com.


By clicking on the URL you can browse available packages for your OS:
(X86 only! Donate a SPARC build zone? Well there is something in preparation, ask for updates on this!)

Solaris 11.3 IPS Packages Repository (517)

Solaris 11.4 (was Solaris 12 internal) IPS Packages Repository (291)

OpenIndiana OI151a8 (and a9) IPS Packages Respository (333)

OmniOS IPS Packages Repository (192)

OpenIndiana Hipster (moving target) IPS Packages Repository (234)

discontinued: testing repo localhosts12nogccdeps -> please use localhosts12 now.


To configure those repos as publishers use: (pick only the publisher matching your OS)
pfexec pkg set-publisher -G '*' -g https://sfe.opencsw.org/localhosts11 localhosts11  #S11.3 x86 (sparc: upcoming spring 2020)
pfexec pkg set-publisher -G '*' -g https://sfe.opencsw.org/localhosts12 localhosts12  #S12 #S11.4 x86 (sparc: upcoming sping 2020)
pfexec pkg set-publisher -G '*' -g https://sfe.opencsw.org/localhostomnios localhostomnios  #OmniOSce x86
pfexec pkg set-publisher -G '*' -g https://sfe.opencsw.org/localhostoih localhostoih  #new OpenIndiana Hipster x86
pfexec pkg set-publisher -G '*' -g https://sfe.opencsw.org/localhostoi151a8 localhostoi151a8  #old OpenIndiana x86

These repositories are 1:1 copies from the build machines, so please expect contents to change frequently and as well, the content may have bugs. Drop me a note (in the comments, or by email) if a package works (yeah, we like that!) or breaks for you (we need to know that).
One day there will be a process which establishes a voting system. It should be used to promote packages from the development repositories to a public release repository. If you have ideas, how a test / promotion process should look like, please let me know (in the comments or by email).
If you are a programmer who can create or at least design a web workflow for the package promotion, then please get in contact very soon to discuss possibilities.
What we need as well for SFE are volunteers for testing the packages. Would you like to be one?

What is it good for

These are development repositories but good for normal use.
For production use, you can compile packages yourself, or, help us building up a "release" repository with QA and a voting website to get packages promoted to "release".

Mirroring the Repository?

Please do *not* mirror these development repositories. You can download the package and prerequisite packages with special switch "-r" to the pkgrecv command. That saves capacities on the server. I'm sure you understand that mirroring 18Gbytes for the whole repository is not the right thing to do.
Once a release repository exists, you are welcome to mirror this (though we understand that it only makes sense in very, very rare cases).
Thank you!


Please keep in mind: You can install any exact package version if you specify the *complete* FMRI listed including the timestamp.
pkg list -avf postfix
To install exaclty that version and no other, use:
pfexec pkg install -v pkg://localhosts11/sfe/service/network/smtp/postfix@3.0.3,5.11-

This way, you could install exactly an *older* or a *newer* package then the resolver would auto-select for you. This enables you to help yourself, in case we have a broken package in these build repositories. You simply install another version which is working for you.

Using https for the IPS package repositires is the default now (20200111), but you can still use the same URLs to the repos with http if you prefer.


Drop me an email at sfepackages at g mail dot com - or create a useraccount here on the blog and leave me a comment.
Need additonal packages? Put them on the package wishlist here http://sfe.opencsw.org/wishlist!

Thank you for using SFE packages and even more, for spreading the word!


Updates: 2016-11-22 -> 20170117 remove old s12nogccdeps repo, wording about volunteering for web workflow package promotion
20181115: change name from S12 (development) to S11.4, change S11 to S11.3
20200105 add intro text, add CPU-arch



Except the roadmap I have not found any info about Solaris 12, much less a beta or alpha to test/look at. Where to get details about 12?

The only source for informations about what a successor for Solaris 11 might be is the official communication from http://oracle.com itself. Only some of the open parts of the development process can be watched for example the "userland" repositories hosted on java.net

Just a quick note, I had to reclaim disk space and the only quick solution was to decommission stone old IPS repos which didn't get any updates since 2011 and 2012.
For users of those repositories like "sfe.opencsw.org/sfe/ please make a list of your installed packages and move to localhosts11 for instance. It could be the case that you need to uninstall all packages from that old publisher and start again from the new.
*Important* Please really make a backup of your system / config files first. Especially the old packages aren't really tunded for preserving config files. You could snapshot all of your old filesystems to preserve config files for later migration for the new package versions.

For now the way to go is: Use the development repos named "/localhost***"
Next step will be, become a volunteer in testing packages so we can make up a "release" repository for the masses. (This is no joke!)

Thank you for accepting the short notice for decommissioning of these old repositories!


For quite some time the RDD feed was missing for OmniOS and OpenIndiana Hipster IPS repositories.
There has been a "pkgrepo rebuild in the transferscript. That eliminated the old update history stored in the files catalog/update.YYYYMMDDTNN.C, so the rss feed had nothing to serve.

The pkgrepo rebuild is now replaced by a pkgrep refresh and this keeps the update history files.
The rss-feeds should now reappear with fresh data shortly.

If you find the rss feed helpful, then please let me know by dropping a note on sfepackages at g mail dot com,
or here on the blog as a comment.


If you have S11.3 and LibreOffice 5 installed, then you might want to upgrade to S11.4 and this will run into dependency constratints.
So you'll have to downgrade LibreOffice 5 to the little bit older version available on S11.4.
* uninstall LibreOffcie 5
* upgrade to S11.4
* install LibrOffice 5

I'm sorry for this inconvenience, but there is currently limited available time to create a more fresh LibreOffcice 5 package for S11.4
Asking for volunteering is not heling much here, except you are equipped with several weeks (!!) of spare time to fight the compile dragon LibreOffice.

Plans are (no promise!) to recompile the LibreOffice 5 version we have on S11.3 for a package installable on S11.4.