Wish List for binary packages for Solaris OpenIndiana OmniOS

  • Posted on: 12 October 2017
  • By: tomww

 

New: Webform to easily submit your wanted packages: http://sfe.opencsw.org/request

 

Please don't think that there is no work done because the table below is so large. A majority of packages is already compiled and ready for install in the IPS repositories (to browse package listings, see quick links). This table blow just says, what is desired. That means, you can wait until a volunteer picks up the task and creates the packages for you.

But you can as well become a maintainer / volunteer and create the spec files and send them over to to us for integration! That is the preferred way to quickly increase the number of available packages in the binary repositories. If you just want an existing spec file be compiled and added to the repositories, then drop as a note. We might ask you to have a quick test of such a fresh package afterwards (well, why not?).

User's wish list for binary packages in the repositories:

% done Name OS PRIO status volunteers

Wishlist

- blender S11 preferred low needs update wanted
- audacity all med problem Icons all blank wanted (repair icons)
- darktable S11 preferred high needs some prereq.pkgs first (tomww)
- saltstack all med needs spec file wanted
100%smiley ansible S11 preferred med X86 version available on Solaris 11 tomww
- facter S11 preferred med want facter to make ansible better wanted
- zabbix        
90% munin all med update to 2.999.2 tomww
- lftp        
- remmina        
100% libreoffice4 4.4.7.2 OIH, S11 high

OIH works, S11, S12 done

see workaround libsmbclient for Hipster later then 2016-11-11 in workbench 2017-01

pjama, tomww
99%smileysmiley

LibreOffice5

5.2.4.2

all med

done: Solaris 11 and 12 have LO 5.2.4.2

open: OI Hipster bug #7755 gnu-libiconv (next try workaround libsmbclient)

tomww
100%(S12)
50%(OI151)
libreoffice4 S12,OI151a8/a9 med

stopper is new procfs headers, LO uses 20y old ones. OI151a8/a9 not started.

S12: Next step is program access to current procfs - [Solved!]

OI151a8/a9: Next step is to try compile run

tomww
- qt5 all med compiled with gcc/g++ wanted
- openstack all low investigate if that would work wanted

10%

100% FF45+Ffmpeg

gstreamer plugins all med

import build recipes from the packages listed in OIH

encumbered IPS, in case they are not in SFE

or update our existing SFE specs to add codes to totem/gstreamer plugin framework

Update: 2016-03-20 revealed that this is a dead end for forefox - they desintegrate gstreamer in favor of a native ffmpeg inclusion to get rid of unstable gstreamer

Solaris 11 SRU14 has FF45 and plays video by ffmpeg

OpenIndiana recent Hipster has FF45 and play video by gstreamer (maybe phased out) or ffmpeg

still wanted for totem
- kodi all low integrate kodi and prerequisites. see OI userland makefiles wanted
- webstack collection all, first OmniOS med

Webstack collection: Bundle-A apache / database / php5x
Bundle-N node - nodejs / database / common extras

Bundle-X nginx / database / php5x

 
- bind, apache (simple) OmniOS high Close the gap for OmnisOS where simple webserver and DNS works  
  vlc, mplayer OI-Hipster med add VLC and MPlayer to OI-Hipster repository.
(S11, S12, OI151a8/a9 already have it)
wanted (test compile, fix issues
with duplicate packages in OIH)
- geany editor all - geany editor needs spec file
100% postfix 3.x OI-Hipster low just compile & upload  
- mailman all med see how it can be integrated volunteers wanted, any kind of setup ideas welcome!
- clang OI-Hipster first, all med add clang. Current install model doesn't allow Hipster-GCC 4.9 and SFE GCC at the same time. Only runtime is allowed concurrently. check it it needs update to clang spec file, see implementation in OI-Userland
100% clamav OI-Hipster first low clamav is currently not packaged for OI-Hipster just add it (version bump too, if possible)
- clamsmtp all med

http://thewalter.net/stef/software/clamsmtp
can be accessed by SMTP, calls clamav antivirus

create spec file, provide tipps for configuration / create reasonable default configuration / SMF

 

50% stellarium 0.12.x Qt4 all X11 med stellarium 0.12.4 works (Qt4)

try stellatrium 0.12.6 (Qt4)

waiting stellarium 0.14.x all X11 low stellarium 0.14.x (Qt5) waitin on update Qt4 to new spec Qt5, test backwards Qt4 compatibility, then make stellarium 0.14.x
100% fuse + ntfs-3g all med update to version 2016.2.22AR2 tomww (done)
 

389 Directory Server

       


Any comments? Email me at sfepackages at g mail dod com

Please register a user for this blog now (comment spam protection!), click on the confirmation email, login and write a comment!

Comments

Audacity

gstreamer plugins for Totem to play varius multimedia files

The idea would be, to import the build recipes from the OpenIndiana Hipster "encumbered" repository.

Xonotic, and Wine fixed to work with NVIDIA. By the Way Tranks for your Great work!!

predrag.zecevic's picture

Hi TomWW,

I have managed to install postfix 3.0.0 and now mail log is full of lines like:

postfix/master[16847]: [ID 947731 mail.warning] warning: smtputf8_enable is true, but EAI support is not compiled in

Also, sending mail with mutt:
sendmail.postfix: warning: smtputf8_enable is true, but EAI support is not compiled in
postdrop: warning: smtputf8_enable is true, but EAI support is not compiled in

So, is there solution (e.g. compile postfix to support EAI ?

Regards.

P.S: I would like to have dedicated chapter/page for problems reporting.

predrag.zecevic's picture

what about vlc and mplayer (was present in sfe for /dev repository)
Best regards.

Hi Predrag,

you mean the repo targeting OI-Hipster, right?

If there are no bad conflicts appearing with packages OI Hipster has on its own, then it could be possible to
get VLC and mplayer in the next few weeks, when the current day work project is on vacation.

Regards,
Thomas

predrag.zecevic's picture

Hi Thomas,

yes... for OI-Hipster.
Thanks

predrag.zecevic's picture

Hi Thomas,

I have found VLC package and tried to install it:

$ pfexec pkg install -v vlc
Creating Plan (Running solver): \
pkg install: No matching version of media/vlc can be installed:
Reject: pkg://localhostoih/media/vlc@2.1.5-0.0.151.1.8
Reason: No version matching 'require' dependency library/desktop/g++/qt@4.8.7-0.0.151.1.8 can be installed
----------------------------------------
Reject: pkg://localhostoih/library/desktop/g++/qt@4.8.7-0.0.151.1.8
Reason: All acceptable versions of 'require' dependency on database/mysql-51/library@5.1.37-2014.0.1.0 are obsolete
Reject: pkg://localhostoih/library/desktop/g++/qt@4.8.7-0.0.151.1.8
Reason: All acceptable versions of 'require' dependency on database/mysql-51@5.1.37-2014.0.1.0 are obsolete
----------------------------------------
Reject: pkg://localhostoih/media/vlc@2.1.5-0.0.151.1.8
Reason: No version matching 'require' dependency library/desktop/g++/qt@4.8.7-0.0.151.1.8 can be installed

Repositories:

$ pkg publisher -n
PUBLISHER TYPE STATUS P LOCATION
openindiana.org origin online F http://pkg.openindiana.org/hipster-2015/
localhostoih origin online F http://sfe.opencsw.org/localhostoih/
hipster-encumbered origin online F http://pkg.openindiana.org/hipster-encumbered/

Looks like qt was compiled against OLD mysql package (default database s/w in /hipster is mariadb-55):

$ pkg search -r database/mysql-51 | grep -v ^incorporate
INDEX ACTION VALUE PACKAGE
require depend database/mysql-51@5.1.37-0.133 pkg:/SUNWmysql51@5.1.37-0.133
pkg.fmri set openindiana.org/database/mysql-51 pkg:/database/mysql-51@5.1.37-2015.0.1.0
require depend database/mysql-51@5.1.37-2014.0.1.0 pkg:/library/desktop/g++/qt@4.8.7-0.0.151.1.8


$ pfexec pkg install -vn database/mysql-51@5.1.37-2014.0.1.0
pkg install: The following pattern(s) did not match any allowable packages. Try
using a different matching pattern, or refreshing publisher information:
database/mysql-51@5.1.37-2014.0.1.0

Any suggestion how to solve this situation?

Regards.

predrag.zecevic's picture

Hi,
I have found geany editor very nice (I see there is already SFEgeany.spec)
Also, no bzr is available from any repository (found SFEbzr.spec too)?

Beside spec files, I have made my own compilation try and for both it has worked fine...
Regards.

predrag.zecevic's picture

Hi Thomas,.

vlc package has appeared in http://pkg.openindiana.org/hipster-encumbered/en/catalog.shtml :

http://pkg.openindiana.org/hipster-encumbered/info/0/pkg%3A%2F%2Fhipster...

I guess you have to talk to alp

Thank you for all your efforts...
Regards.

predrag.zecevic's picture

Hi,
no postfix package is available for /hipster OI (from /localhostoih repository)?

Regards.

Hi Predrag,

I've used the chance to edit the postfix spec file to use "mediated symlinks", that should help to better integrate with the packages sendmail and eventually older postfix package from the OS-distro.

I'll update this comment once the package hits the OI-Hipster repo.

Is dovecot needed as well?

Regards,
Thomas

Hi Predrag,

postfix 3.0.3 is now available for OpenIndiana Hipster, compiled on entire@@0.5.11-2015.0.1.1.

The symboliks links to get e.g. /usr/lib/sendmail are now *mediated*, that means, they might still point to the OS-Distro "mailwrapper" or classic "sendmail".

After installing postfix by "pfexec pkg install pkg://localhostoih/service/network/smtp/postfix" you need to set the mediators to "postfix-sfe". You can check the old and new settings with e.g. "ls -l /usr/lib/sendmail" and see where the symlink points to.

old:
"pkg mediator mta"
MEDIATOR VER. SRC. VERSION IMPL. SRC. IMPLEMENTATION
mta system local mailwrapper

change:
"pfexec set-mediator -I postfix-sfe mta" (edited, now syntax is correct)

new:
"pkg mediator mta"
MEDIATOR VER. SRC. VERSION IMPL. SRC. IMPLEMENTATION
mta system local postfix-sfe

"ls -l /usr/lib/sendmail"
lrwxrwxrwx 1 root other 16 Jan 7 22:22 /usr/lib/sendmail -> sendmail.postfix

To see all available mediator alternatives, use:
pkg mediator -a

As the new mediator options are new, there might be errors in it. Please let me know, if something is not propperly linked.

Regards,
Thomas

PS: Solaris 11 uses the name "sendmail" instead of "mta" for the mediator. The postfix 3.0.3 package for Solaris11 localhosts11 will be available soon!

predrag.zecevic's picture

Hi Thomas,

many thanks for fast creation. Regarding installation/check commands executed, output was as expected/specified:

$ pfexec pkg install -v postfix
$ ls -l /usr/lib/sendmail
$ pkg mediator mta
$ pfexec set-mediator mta postfix-sfe ### <--- syntax error
.
$ pfexec pkg set-mediator -I postfix-sfe mta ### Proper one, latest /hipster-2015, illumos-c33daa8
$ pkg mediator mta
$ ls -l /usr/lib/sendmail
$ pkg mediator -a

And also works like charm! No problems found (after finishing setup).

Many thanks
Best regards/Mit freundlichen Grüßen

Hi Predrag,

thanks for testing and the syntax correction! I've edited the original comment to be correct.

It is very good to hear that the package works for you. The "mediator" feature was on the todo-list for so long. As the plain OS-Distro started to deliver postfix, it was now necessary to add it to SFE.

I still have a dream: If a user wants a new package, or a package version bump, then it would be cool to have a web form where user can select the spec file and request the build / publish process. If someone wants to help building such a web interface, I would be happy to create a small project for that. The automatic build system can easily be extended to include such "small" build requests along with the regular automatic builds.
Next would be to get a voting system, so packages in the "build repositories" like localhostoih and localhosts11 can be voted and then automatically published to a "release" repository (including dependencies).

Best Regards,
Thomas

predrag.zecevic's picture

Hi Thomas,
many thanks for sharing your dreams with us!
That is really great idea.

WBR/MfG

Hi Predrag,

clamav 0.98 is now on the OI-Hipster repository. Later tonight the automatic build process will add the 0.99 version.

In case there is some other compile option needed for clamav, then please let me know.
Interesting would be a setup guide explaining a simple setup of clamav with postfix / dovecot.
The rough steps of the setup would be enough, the publication could be done by someone else.

Regards,
Thomas

predrag.zecevic's picture

Looks like there is something to integrate it with Postfix (you might try to compile that one too):

http://thewalter.net/stef/software/clamsmtp/

Compiling is easy with gcc from /Hispter:

Build/clamsmtp-1.10$ ./configure --prefix=/my/prefix
Build/clamsmtp-1.10$ gmake

Many thanks.

P.S: There are documents on net, regarding setup:
http://thewalter.net/stef/software/clamsmtp/postfix.html
https://lelutin.ca/posts/installing_postfix_-_clamav_-_spamassassin_-_do...
https://gist.github.com/robinsmidsrod/7387679

clamsmtp is on the wishlist now

Thanks!

Could it be possible to compile/offer this great Port at sfe?

Required libraries:

zlib (provided by Oracle/solaris repo)
libjpeg (v8) (v6 by Oracle/solaris repo)
libogg
libvorbis
libvorbisfile (may be part of libvorbis)
OpenAL (OpenAL Soft required, Creative's and Apple's versions are made of fail)
SDL v1.2 or 2.0 (2.0 recommended)
libcurl (optional, required for server downloads)

Infos:
https://github.com/dhewm/dhewm3
https://github.com/dhewm/dhewm3/blob/master/README.md

Source-file:
https://www.sendspace.com/file/do0heh
or
https://github.com/dhewm/dhewm3/releases/tag/1.4.0

Regards

Verm

Hi Community, what about (if possible sparc + x64/86):

(maybe there are existing SVR4 pkg out there, or maybe they are still existing here)

avidemux
videoeditting software like: flowblade, cinelerra, auteur
xephem
octave + gui
quemu
pspice
(almost continously act. Firefox/Opera)
KDE
actual NETCDF
Blender
MONO (for use with wine under x86)
lyx
textmaker

br
ultrafire

Hi Ultrafire!

This is a challenging whislist, but at least for some of the programs I dare to say:
Challenge accepted.

It will naturally take a while to either update the existing spec files (lxy, blender, octave, cinelerra) or create new ones.

Could you please give a priority to the program names and if possible, a very rough idea what type of work you intend to do with them?
That would for sure fuel the maintainers...

Regards,
Thomas

Hi Thomas,
first thanks a lot that You are going to "take the challange" :-)
At home we switched almost completely to Solaris, just for videoediting and some gaming we have windows7 left; or for lightsribe-labeling jobs, DVD/CD Ripping (because easier.....), the rest is on solaris/Sparc or x86 - no probs anymore with maleware......

(wish)Prioritylist:

1. actual NETCDF - needed for scientific work, big file handling

1.2 FUSE (inkl ntfs) for SPARC - didn´t found this working.......

1.3 smplayer frontend for SPARC

1.5 . MONO (for use with wine under x86) - missing for many win-apps under wine

1.8 avidemux, videoeditting software like: flowblade, cinelerra, auteur - one of my hobbies : Videoediting, I would like to change from win to solaris

2. octave + gui - as mathlab pedant important, there is no actual x86/SPARC Matlab version out there any more (only an old R2009b/SPARC); useful for analyzing and imagine/visualisizing scientific work, as my wife does (or others, too)

2.5 lyx - gui for latex (texlive) - my wife an me are using latex a lot for textmaking

3. KDE - one more alternative to GNOME on (oracle)solaris 11 (sparc&x86 , OI, OpenSXCE .....), prevered for me

4. quemu - for simulation other computerenvironments - hobby or job, for testing software

5. pspice - simulation electrical ciruits, usefull sometimes in my job, or for other in studying

6. Blender - hobby for me

7. textmaker just another text manipulator / editor

8. xephem

9. almost continously act. Firefox/Opera (/Thunderbird)

br
ultrafire

I am interested in an updated version of gnome-commander, which I use a lot to copy files back and forth. The current version of gnome-commander in the Oracle repository, does not support Tabs (so you can have shift between several different directories easily). This is just a minor request, gnome-commander works fine today when doing heavy file operations.

However, I would be interested in an "how to" for building an IPS package. Say that I try compiling gnome-commander myself from the latest sources, and I succeed in doing that. How would I help you providing an IPS package for that? What are the steps? If there would be a good guide out there, then maybe several people would help you providing IPS packages/build instructions. The problem is not that people are lazy, the problem is lack of knowledge. There are lot of Solaris users out there, but not many knows how to provide an IPS package. So, I wish an easy how-to for providing an IPS package. Ideally, exemplified with a very small program, from say, git. And then a detailed how-to, for building an IPS package so we can submit that to you.

PS. The layout of this page could be better. ;) Have a look at this page from a new version of firefox. Quite difficult to read, as the text runs into each other. Anyway, thanx for your efforts! :)

Hi!
User Rene on this blog is currently looking into the old Wiki pages for the pkgbuild project. They are currently offline but the content is accessible. That way we could make the old setup instructions available on how to install a build environment.

A note about re-building the same package then the OS already provides: This is often a bit difficult, as you need to deal with the package itself being a duplicate and the prerequisite libraries as well. They need live in a place, where they don't interfere with the older OS provided libs. But usually that can be somehow managed to work fine.

About providing packages. The concept for SFE is in any case, to have a maintainer only provide the build instructions in form of a spec file and patches. Both are commited to the SVN repository of spec-files-extra. That way we can ensure, that every one can follow what is done to build the packages and maintain quality. Other maintainers will comment on each others code.
Binary packages for the public users are only built on a build machine which is also maintained by other persons, so the real package is built by a different person and then uploaded to the IPS repositories.

About setting up a build environment. We currently have no ready guide online, but in the meantime, you might want to look for the setup instructions you can find when googling for "bootstrap-sfe-latest" (http://bit.ly/bootstrap-sfe-latest). This script does the pre-install of a number of packages from the OS and then create the Build-Environment. For Solaris 11 you should install before the Solaris Studio compiler runnging the scriptes. A tarball install of Studio is good enough and should be stored in /opt/solarisstudio*numbers* with the "cc" command sitting in e.g. /opt/solarisstudio12.4/bin/cc
The bootstrap script then finds the compiler and configures the init-script accordingly.

I see my role in focusing on building the packages with a automated script-work on several OS platforms (Solaris 11, OpenIndiana, OmniOS) and therefore I need support from the community to do other important supporting tasks. One of the important tasks to do is writing an easy to understand documentation and put it online. If someone wants to write down the initial steps he/she learned while doing the initall install, that would be perfect. I've given that several times, but unfortunately, once the build environment worked, they have been too much busy developing spec files and building packages.
I can give a little bit support on the IRC channel #pkgbuild in irc.freenode.org if someone wants to setup the build environment live. I can provide setup help and doing reviews of docs, but I don't want to write again a doc which the community could easily write for us.

Thanks for asking!

Regards,
Thomas

PS: You might have noticed, that I'd tweak the website a bit to get the theme a bit more clean. There has been an unfortunate config setting for the menus, a remaining from the very beginning. Work on the blog is not complete as of now. But again, I want to focus on the packages and build process, not on documentation and website. If someone wants to maintain this blog from the drupal or content side, then I would be more then happy to arrange that (currently running drupal 7, but that is not a roadblocker to write articles, right?).

Great information. I would actually be interested in helping out, but I am a bit busy. So I dont really know if I will find time. Time will be easier to find, if there is less of a uphill of course, for instance, by easy to read instructions. If I had some documentation, I might take a casual look. But dont expect too much from me, please. But if there are easy to read instructions, the barrier to help is lowered. A lot.

So, to recap, these are the steps, right?
1) Setup a Build-Environment. This needs documentation and there are no such documentation, but you have thought of writing it.
2) Figure out how to compile a certain source code for Solaris, and document the changes in an spec-file. This is done by me.
3) Share the spec-file to you, who will build an IPS package and add it to your IPS repository.

BTW, here are build instructions for Kodi (a.k.a XBMC) a very popular media player:
http://forum.kodi.tv/showthread.php?tid=44315&pid=2210368#pid2210368

The old wiki pages are back online, if you want, please visit the link Rene gave in the other comment.

It would be perfect if you could come to the IRC channel #pkgbuild on irc.freenode.org and we can do the setup and the very first steps together.

Regards,
Thomas

Hi MichaelJackson123,

I hope there has been a chance to look at the old wiki pages https://sfedocs.oxys.dk/w/index.php/Main_Page and get an idea how the build environment setup can be done.

This is the exact point where I would be happy to see the SFE community step in and write a new setup page based on the text on the old wiki. The new guid can for instance live on this blog here, but can be hosted anywhere. It just needs to be written :)

If you have any questions then please drop me a note. And the online help on the IRC chat channel is best to reach me (irc.freenode.org channel pkgbuild)

Regards,
Thomas

Well, about 1) .. There is already documentation, I personally don't want to write a new one :). You could ask Rene if he could send an extract of the old pages from the wiki backup he was able to restore.

2) and 3) somthing like this. Look at a spec file and you'll see this is the complete information needed to fetch sources, apply patches, compile, install and create IPS package for the software.

About Kodi, there is an attempt to integrate it into OpenIndiana, but I can't tell if there is any progress.
We already have mediatomb providing at least a subset of features and I think we'll add Kodi some day as well (low to med priority).

Hi there,

I have put up the old mediawiki site here for reference only:
https://sfedocs.oxys.dk/w/index.php/Main_Page

Note that absolutely everything about this site may change (URL, hosting, looks, accessibility, whathaveyou) :-)
It is also in readonly mode.

But at least you should be able to pull some information for now.

/Rene

Hi Rene,

thank you very much! It was fun reading that old pages.

I believe there will be someone speaking up and take page after page out and find a new home for them.

Regards,
Thomas

I have browsed the build instructions, but need to devote more time to it. Most realististically, I wont be able to contribute now.

I have question though, how come the complete list of software is not shown in the IPS package maneger? For instance, the game Breakout is not listed in the IPS manager GUI, but it can still be installed via browsing this, and using the manifest:
http://sfe.opencsw.org/localhosts11/en/catalog.shtml

The Package Manager GUI relies on the information like e.g. "name=info.classification value=org.rpm:Amusements/Games" in the package. This is one source for displaying a package in the GUI. Packages missing this information will not automatically displayed in the GUI. E.g. this makes sense for a hidden package that for instance helps upgrading.

The package games/lbreakout can be displayed in my case when I select "all publishers" and then in the list, "all categories".

As written in the other article on the blog, if you tried the package during the last 24hours, there has been unplanned (unintended :) ) maintenance on the repositories. That way the meta-info for the packages was available but catalog and index has been missing. This is now back online, so if you re-try, I believe with the above selection "all publishers" "all categories" the packages should be displayed.

In SFE we still have some (diligent) work to do: Add correct and useful categories to every package. If a package misses such a category, it can barely found in the GUI package manager.

For setting up a build environment, you should reserve say 2hours (excluding Solaris Studio compiler tarball and required IPS packages from the distro).
But, as you can imaging, the real time sink comes after setting up the build environment :). But I think it's worth putting some effort into building/updating package anyways. And sharing that effort makes it possible that Solaris, OpenIndiana and OmniOS can be a very good Desktop or a mixture from Desktop and Server or a pure Internet Server with your database, web- and emailserver on it. If you want, you can setup a Non-Global-Zone for the builds and install packages there for testing, then install the same package on your global zone once proven okay.

So my offer is still valid, reserve 2h and we can setup the build environment together. We only need IRC or any other chat platform for it to stay connects. No access to your system needed from my side.

Regards,
Thomas