Re: [OpenIndiana-discuss] Questions about /var/pkg

[aurelien . larcher]

Le Samedi 13 janvier 2024, Goetz T. Fischer a écrit :
> oh yes, that is the case for any kind of upgrades because while ips is still 
> rotating the slash, the 
> others are half-way through already. i've done rhel upgrades after 1 1/2 
> years and they were 
> significantly faster than ips upgrades after a month.
> just because they handle download and extraction of the packages differently 
> doesn't mean the total time 
> is better. what matters is how long it takes in total.

Probably a difference in hardware then.
I performed comparisons on same hardware some years ago.
Regardless of what you can expect from implementation there are actual 
complexity estimates that would disagree.
 
> On Sat, 13 Jan 2024 20:41:58 +, aurelien.larc...@gmail.com wrote:
> > Le Samedi 13 janvier 2024, Goetz T. Fischer a écrit :
> >> i don't know about plain apt but aptitude, yum or zypper are lightyears 
> >> faster than ips no matter how
> >> many updates are pending.
> > 
> > No that is the not the case for large upgrades.
> > The reason is that apt/yum and the likes unpack each tarball sequentially 
> > and process pre/post install 
> > scripts.
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Questions about /var/pkg

[aurelien . larcher]

Le Samedi 13 janvier 2024, Goetz T. Fischer a écrit :
> i don't know about plain apt but aptitude, yum or zypper are lightyears 
> faster than ips no matter how 
> many updates are pending.

No that is the not the case for large upgrades.
The reason is that apt/yum and the likes unpack each tarball sequentially and 
process pre/post install scripts.


> 
> On Sat, 13 Jan 2024 18:07:49 +, aurelien.larc...@gmail.com wrote:
> > IPS scales better w.r.t the number of packages installed and therefore is 
> > faster than apt for large 
> > upgrades.
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Questions about /var/pkg

[aurelien . larcher]

Le Samedi 13 janvier 2024, Goetz T. Fischer a écrit :
> as much as i value playful adventures, system stuff should always be c/c++. 
> the last thing one would 
> want is to add even more stuff that can't be uninstalled because of maybe 
> only one single dependency.
> 
> the first and foremost problem of ips is speed. it's so slow that i had to 
> write my own replacements for 
> certain features like "list" which are used often. or for example the time 
> "pkg update" needs before it 
> even starts actually installing things, can easily be minutes on older 
> systems. while on the same 
> machine yum or zypper get that sorted within 5 or 10 seconds.

However they do not run a SAT solver on the basis of "actions".
IPS is faster for large updates where running the SAT solver becomes negligible 
compared to the actual work performed.
IPS scales better w.r.t the number of packages installed and therefore is 
faster than apt for large upgrades. 

> the second problem is the size of the repo. as i posted here some months ago, 
> /var/pkg is significantly 
> larger compared to most other package management systems.
> 
> On Sat, 13 Jan 2024 13:50:30 +0100, Till Wegmueller wrote:
> > Glady. I made some experiments that went relatively far one being a repo
> > format implementation in Golang[0] and one being some of that work being
> > ported to rust [1].
> > 
> > -Till
> > 
> > [0] https://github.com/Toasterson/pkg6-go
> > [1] https://github.com/openflowlabs/ips
> > 
> > On 13.01.2024 13:02, Matthew R. Trower wrote:
> >> Ah okay, thanks for the clarification. There are a number of items I’d 
> >> dearly like to improve about 
> >> IPS, but none of them are something to tackle on a whim. I guess I’ll add 
> >> metadata caching behavior 
> >> to the list. Maybe once I get some more immediate matters off my plate, we 
> >> can revisit this.
> >> 
> >> 
> >> -- Matthew R. Trower
> >> 
> >>> On Jan 13, 2024, at 05:42, Till Wegmueller  wrote:
> >>> 
> >>> Hi Mathew
> >>> 
> >>> It is a special statement for /var/pkg/publisher you will get stale data 
> >>> due to how the Metadata 
> >>> download process works. This directory MUST always go forward in time 
> >>> from it's perspective. Meaning 
> >>> it MUST be inside the Boot Environment. At least as long as nobody 
> >>> rewrites that :)
> >>> 
> >>> I can give you some details on the process if needed. But the gist is 
> >>> that there are pre split JSON 
> >>> files pkg downloads and merged into the existing metadata under the 
> >>> publisher. Then it merged that 
> >>> into the global cache. Nobody has ever tested if IPS has a detection 
> >>> mechanism if there are stale 
> >>> files in this directory. This is fully undocumented territory as it was 
> >>> done in the last days of 
> >>> OpenSolaris. OmniOS IPS might have such detections now but 
> >>> somebeody(Maybe you?) would need to merge 
> >>> in that version of IPS. Solaris IPS is also open and wen could 
> >>> cherry-pick from there if we want 
> >>> [0]. I do not know which IPS Helios is using but i would assume OmniOS's 
> >>> one. In any case you can 
> >>> make a full cache refresh with `pkg refresh --full` and sometimes that is 
> >>> needed to recover from 
> >>> situations where the cache is broken.
> >>> 
> >>> As side note there was a project to merge the IPS forks but it hit my 
> >>> ENOTIME. If you want to pick 
> >>> that up and make improvements on the metadata process I am happy to help.
> >>> 
> >>> -Till
> >>> 
> >>> [0] https://github.com/oracle/solaris-ips
> >>> 
>  On 13.01.2024 01:11, Matthew R. Trower wrote:
>  Hi Till,
>  To clarify, I only wish to share /var/pkg/publisher. /var/pkg clearly 
>  contains image-specific data, 
>  and bad bad things would happen if that were shared.
>  Does your statement still apply specifically to /var/pkg/publisher?
>  -- Matthew R. Trower
> > On 1/12/24 12:25, Till Wegmueller wrote:
> > Hi,
> > 
> > From personal experience, Yes this data is kind of a cache. It is later 
> > merged into the publisher 
> > independant JSON. However you MUST NOT share this between BE's this 
> > directory is not safe to go 
> > back in time due to how partial download and merging works. Do NOT 
> > share /var/pkg between BE's
> > 
> > -Till
> > 
> > On 12.01.2024 06:16, Matthew R. Trower wrote:
> >> Hi,
> >> 
> >> Is the format of /var/pkg/publisher committed at this point? It looks 
> >> to contain cached data and 
> >> downloads from publishers, which ought not to be tied to any 
> >> particular BE. If I create a ZFS 
> >> dataset to share that among BEs, am I going to run into trouble?
> >> 
> >> What exactly are the contents of /var/pkg/lost+found? Can any files I 
> >> discover in there be safely 
> >> deleted?
> >> 
> >> 
> >> -- Matthew R. Trower
> >> 
> >> ___
> >> op

Re: [OpenIndiana-discuss] Device Driver Utility

[aurelien . larcher]

There was never a hcl server as the code was never released.
There is a link to submit to an email address instead. 

Le Mardi 22 mars 2022, russell a écrit :
> Hi
> 
> Is the submission option in the Device Driver Utility supposed to work 
> as when I tried to submit my config it reported that the HCL Server is 
> not active.
> 
> TIA
> 
> Russell
> 
> 
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] wiki.openindiana.org needs to be re/started and fixed

[aurelien . larcher]

Luckily there are enlightened people like you to speak the truth :)

I missed you so much Nikola :)

Le Vendredi 1 octobre 2021, Nikola M. a écrit :
> On 10/1/21 1:42 PM, Andreas Wacknitz wrote:
> >
> > Am 10/1/21 um 1:27 PM schrieb Nikola M.:
> >> Wiki.openindina.org is down and needs to be restarted or checks for
> >> functionality what actually induces and causes it not to be available
> >> occasionally.
> >>
> > The wiki has been shut down for security reasons. Most of its contents
> > has already been merged into the docs. Some pages have been exported and
> > are available for the documentation team.
> 
> I think most of Wiki it is not moved anywhere but by turning off wiki is 
> just made unavailable.
> 
> Security reasons are not quite valid reason, because new instance of 
> Wiki can be started ,license is provided as before and also it were 
> already updated before with version of Wiki.
> 
> Important functionality of the Wiki, being able to freely create and 
> enhance wiki pages is unavailable and is very valuable. (As Wikipedia as 
> an example of freely editable content proves for decades).
> 
> Process that requires strict subjection to other members approvals to 
> edit wiki-like content hinders user freedom and creativity, like 
> proposed docs pages with github , being external service, and not 
> including all the content available before but just a small subset.
> 
> Deciding on private mailing list, hidden from the wider audience is the 
> reflection of closed and exclusive projects and subjecting changes and 
> hindering wiki functionality is in line with the censorship.
> 
> I am of the opinion that no great and explosive progress and widening 
> the user base is possible on tightly restricted and secretly controlled 
> processes that hinder creativity.
> 
> Free users and contributors should not be subjected to article approvals 
> by few and affected by secret mailing lists not available to the public, 
> as OI is doing, that is not the signature of community and free software 
> projects in general.
> 
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Success! Re: Installing on Intel B460M chipset intel i5-10400F

[aurelien . larcher]

Le Dimanche 15 août 2021, Carl Brewer a écrit :
> 
> >
> > Now a lot of setup to do, but that's easy stuff. I will send in the 
> > hardware report using the DDU when it's all online.
> 
> Except that the DDU doesn't submit, I've seen another thread here 
> explaining why.
> 
> In the interests of adding to the knowledge pool, what command should I 
> use to generate a list of devices and should I just get its output and 
> email to hcl@?

Yup and please confirm to me when you do so. 
Just to check that the forward works as expected.
> 
> Thanks again!
> 
> Carl
> 
> 
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Installing on Intel B460M chipset intel i5-10400F

[aurelien . larcher]

Some commits to support recent Intel were merged post 2021.04.
Not sure if it applies to your model though. 

Le Vendredi 13 août 2021, Carl Brewer a écrit :
> I assume there's a way to make it be more verbose, so I can see where 
> it's getting stuck, any hints?
> 
> 
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] OI install on current gen desktop motherboards?

[aurelien . larcher]

Some illumos developpers seem to use recent Intel NUCs.

I run a Dell R740xd2 with two Xeon Gold 5218R bought last autumn. 

Le Mercredi 11 août 2021, Till Wegmueller a écrit :
> Hey Carl
> 
> I don't know about Intel newest gen Most developers in illumos which we 
> are based on are on AMD Ryzen now.
> 
> If you don't know if one of the illumos developers runs a modern Chipset 
> there is a good chance it's a bit too modern and will need custom build 
> again.
> 
> I know one illumos developers was recently asking for somebody to test 
> Ryzen3 Support but nobody volunteered.
> 
> -Till
> 
> On 10.08.21 18:51, Carl Brewer wrote:
> > I originally posted this to OI-userland by mistake!
> > 
> > 
> > G'day,
> > 
> > One of my aging (10 years!) OpenSolaris/OI box needs to be replaced, 
> > it's a timebomb now.
> > 
> > I'm looking at using a 10th or 11th gen Intel i5, probably a i5-10400F 
> > or 11400F, it's the sweet spot for value here. LGA1200 socket.
> > 
> > Looking at using Gigabyte desktop motherboards because I've always found 
> > them to be reliable over many years.
> > 
> > There's  H410M, B460M and B560M chipset boards that seem reasonably 
> > priced.  Any compelling reason to go with one of them in particular?
> > 
> > I had a hell of a time getting initial installs working on a 9th gen 
> > motherboard about two years ago, has that story changed?  I remember 
> > having to do all sorts of weird stuff with custom builds and BIOS changes.
> > 
> > I had a look at the OI and Illumos HCLs but nothing recent seems to be 
> > there.
> > 
> > Thank you,
> > 
> > Carl
> > 
> > 
> > ___
> > openindiana-discuss mailing list
> > openindiana-discuss@openindiana.org
> > https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] openindiana.org cert expired

[aurelien . larcher]

You need to run the getssl script manually.
Sometimes the scheduled execution fails.

Le Dimanche 25 juillet 2021, Till Wegmueller a écrit :
> Hi Russle
> 
> Thanks for the report.
> 
> We are already looking into it with the Hoster.
> 
> -Till
> 
> On 25.07.21 16:58, russell wrote:
> > Hi
> > 
> > Tried to connect to https://openindiana.org and firefox refused, checked 
> > the cert and found the Let's Encrypt cert expired 22nd July 2021
> > 
> > Russell
> > 
> > 
> > ___
> > openindiana-discuss mailing list
> > openindiana-discuss@openindiana.org
> > https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] April May snapshot

[aurelien . larcher]

Le Samedi 24 avril 2021, Andreas Wacknitz a écrit :
> Am 16.04.21 um 14:39 schrieb bscuk2:
> >
> >
> >
> >
> >  Forwarded Message 
> > Subject: April May snapshot
> > Date: Thu, 15 Apr 2021 14:58:45 +
> > From:
> > To: openindiana-discuss@openindiana.org
> >
> >
> >
> > Hello All,
> >
> > Wallpapers to be included in next snapshot. I have done a basic
> > wallpaper for the next snapshot. I was interested if it would be
> > included in the next snapshot. Usually it would be a png image but I am
> > unable to understand what size it should be.
> >
> > Let me know what you think.
> >
> > Robert
> >
> > https://wiki.openindiana.org/oi/Image+Gallery?preview=/1474670/70156307/VISION21.PNG
> >
> >
> > ___
> > openindiana-discuss mailing list
> > openindiana-discuss@openindiana.org
> > https://openindiana.org/mailman/listinfo/openindiana-discuss
> Which one do you want to be included? It would be helpful to create a PR
> for it.
> 
> Andreas

For reference the repository is at:

https://github.com/OpenIndiana/openindiana-backgrounds


> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Filezilla 3.47.2.1 working

[aurelien . larcher]

It is probably not difficult to add Wxwidgets 3 to OI given that it has been in 
the repository for a year and a half...

3.1.4 to be exact.

Le Vendredi 2 avril 2021, russell a écrit :
> Hi
> 
> Just to let you know I have managed to build Filezilla 3.47.2.1 (depends 
> on libfilezilla 0.20.2) and it works. Unfortunately it is not the latest 
> which is Filezilla 3.53.1 but this depends on libfilezilla 0.27.0 or 
> later which generate C++ errors and this was built with the default gcc 
> 7.5.0 compiler
> 
> Environment  requirements for all builds
> 
> $ export PATH=/opt/gnu/bin:$PATH   (you must use the gnu xgettext)
> 
> 
> +++ To build Libfilezilla 0.20.2 +++
> 
> # pkg install pkg-config gnu-gettext doxygen
> 
> edit lib/string.cpp replace wcsnrtombs with std::wcsnrtombs
> 
> $ CXX=g++ CXXFLAGS="-m64 -I/usr/include/gmp -fpermissive" CPP=cpp CC=gcc 
> CFLAGS="-m64"  ./configure --prefix=/opt/gnu --disable-static 
> --enable-shared
> 
> $ gmake
> 
> # gmake install
> 
> +++ To build Libfilezilla 0.20.2 +++
> 
> 
> The standard version of wxwidgets 2.8.12 which is provided with 
> OpenIndiana is too old to be used so I downloaded and built WxWidgets 
> 3.0.5, also you can not use a later development release
> Not how difficult it would be bump the WxWidgets from 2.8.12 to 3.0.5
> 
> 
> +++ To build WxWidgets 3.0.5 +++
> 
> $ CC=gcc CFLAGS=-m64 CXX=g++ CXXFLAGS="-m64 -fpermissive" LDFLAGS="-m64 
> -L/opt/gnu/lib" 
> PKG_CONFIG_PATH="/usr/lib/pkgconfig:/opt/gnu/lib:$PKG_CONFIG_PATH" 
> ./configure --prefix=/opt/gnu --with-gtk=2 --enable-ipv6
> 
> $ gmake
> 
> # gmake install
> 
> +++ To build WxWidgets 3.0.5 +++
> 
> 
> 
> +++ To build Filezilla 3.47.2.1 +++
> 
> $ CXX=g++ CXXFLAGS="-m64 -I/usr/include/idn -I/usr/include/idn2 
> -I/usr/include/pugixml -I/opt/gnu/include 
> -I/opt/gnu/include/libfilezilla -fpermissive" CPP=cpp CC=gcc 
> CFLAGS="-m64 -I/usr/include/idn -I/usr/include/idn2 
> -I/usr/include/pugixml -I/opt/gnu/include 
> -I/opt/gnu/include/libfilezilla" 
> PKG_CONFIG_PATH="/opt/gnu/lib/64/pkgconfig:/opt/gnu/lib/pkgconfig:/usr/lib/64/pkgconfig:$PKG_CONFIG_PATH"
>  
> LDFLAGS="-m64 -L/usr/lib -L/usr/lib/pugixml -L/opt/gnu/lib/64 
> -L/opt/gnu/lib" ./configure --prefix=/opt/gnu --enable-shared 
> --disable-static --with-pugixml=builtin --disable-dependency-tracking 
> --with-wx-prefix=/opt/gnu
> 
> $ gmake
> 
> # gmake install
> 
> +++ To build Filezilla 3.47.2.1 +++
> 
> 
> In order to allow the filezilla executable you must have
> 
> $ export LD_LIBRARY_PATH=/opt/gnu/lib:$LD_LIBRARY_PATH
> 
> then you can run assuming you have /opt/gnu/bin in your PATH
> 
> $ filezilla
> 
> 
> Russell
> 
> 
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Do you ever think about adopting APT+DPKG?

[aurelien . larcher]

Le Mardi 2 mars 2021, Chris a écrit :
> On 2021-03-02 09:56, Judah Richardson wrote:
> > On Tue, Mar 2, 2021 at 11:43 AM Chris  wrote:
> > 
> >> On 2021-03-01 06:33, cretin1997 via openindiana-discuss wrote:
> >> > We have the tech there. Well adapted for our needs. APT+DPKG based
> >> Illumos
> >> > distro
> >> > is not unpopular. Some distros even use RPM.
> >> >
> >> > Most historic APT+DPKG based distros already dead, only DilOS is left
> >> now.
> >> > So we
> >> > could have a look at DilOS, the way they patched and utilizing APT+DPKG
> >> and
> >> > we can
> >> > even co-operate with them, if both side wanted.
> >> >
> >> > We already see too many problems of the IPS pkg. Could we switch to
> >> another
> >> > path?
> >> >
> >> > I know compatibility haunted us. But recently we broke it already. It's
> >> no
> >> > longer
> >> > the holy grail we have to keep at all cost anymore.
> >> >
> >> > Could we patch our oi-userland to generate DEB packages alongside of IPS
> >> > packages?
> >> >
> >> > The DilOS people has figured out how to build illumos-gate into DEB
> >> packages
> >> > already.
> >> >
> >> > This will not as hard as doing from scratch as we have many references.
> >> There are many possible "package managers" available. Some have already
> >> been
> >> recobbled
> >> to support Solaris derivatives. But IMHO the DEB package managers are not
> >> as
> >> efficient
> >> 
> > I'd say this is largely an academic argument. I have 3 machines that use
> > apt + deb with no associated issues. Actually, # apt dist-upgrade on Debian
> > Buster, Ubuntu 20.10, and Raspberry Pi OS Buster runs MUCH faster than #
> > pkg update -v -r on OI Hipster with approximately the same underlying
> > hardware (Intel Core 2nd Gen, 16 GB RAM) for the OI, Debian, and Ubuntu
> > machines.
> > 
> > as many of the others, it's a real "cache thrasher".
> > 
> > I don't think this is an issue if you have a decent (e.g. Samsung 860 Evo
> > or better) SSD with good endurance specs.
> Agreed. It's also not an issue with more RAM/cores && higher frequencies. ;-)
> 
> In the end, I don't really care _which_ package manager is chosen; as long
> as there is only _one_ and that it's the simplest to use for the package 
> *creators* :-)
> Ultimately; that should ensure the most packages for the users, with the 
> greatest
> package integrity. No? :-)
> 
> --Chris
> > 
> > Many of the others are
> >> more DB
> >> centric. Which tends to make them much faster and less resource abusive.

The other ones do not use a SAT solver that cross checks any action on the 
system...

Also I have repeated this a lot of times on the past but here again: 
traditional archive-based package managers are very slow for large updates.
APT in particular is awful for a large number of packages triggering 
postinstall scripts.

I think there are a lot of misconceptions about the boundaries of IPS.
If it were just solving dependencies and unpacking tarballs and triggering 
shell scripts if would be as fast as the rest...

Now if the discussion is whether the design has rough edges or whether the 
incurred penalty is worth paying for a desktop system where you do not care 
much about consistency... it is another topic. 

> >> 
> 
> -- 
> ~10yrs a FreeBSD maintainer of ~160 ports
> ~40yrs of UNIX
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Finding package that includes file

[aurelien . larcher]

Do you mean 32bit kernel or 32bit support for binaries?
32bit libraries are still shipped.

Also pkg search -r to search remote repositories, the default is local.

Le Mercredi 25 mars 2020, Nicholas Papadonis a écrit :
> Looks like there is some dependency issues
> 
> $ pkg publisher
> PUBLISHER   TYPE STATUS P LOCATION
> openindiana.org  origin   online F 
> http://pkg.openindiana.org/hipster/ 
> 
> Search pkg.openindiana.org 
> 
> library/motif@0.5.11,5.11-2013.0.0.0:20151027T070001Z 
> 
> 
> $ sudo pkg install library/motif
> Creating Plan (Solver setup): |
> pkg install: No matching version of library/motif can be installed:
>   Reject:  
> pkg://openindiana.org/library/motif@0.5.11-2013.0.0.0:20151027T070001Z
>   Reason:  No version matching 'require' dependency 
> x11/trusted/libxtsol@0.5.11-0.151.1.8 can be installed
> 
> Reject:  
> pkg://openindiana.org/x11/trusted/libxtsol@0.5.11-2018.0.0.0:20180212T052909Z
>to
>  
> pkg://openindiana.org/x11/trusted/libxtsol@0.5.11-2020.0.0.0:20200319T111555Z
> Reason:  This version is excluded by installed incorporation 
> consolidation/userland/userland-incorporation@0.5.11-2016.0.1.7762
> 
> nick@openindiana:/home/nick/t/pop/pop$ 
> 
> Note: I need 32-bit support and that is why I’m on this old build.
> 
> 
> > On Mar 25, 2020, at 2:26 AM, Richard L. Hamilton  wrote:
> > 
> > This works for me (the locate command doesn't show the package, but it does 
> > show where it is).  This assumes the file is installed.
> > root@openindiana:~# locate libXm.so.3 # if updatedb has been run
> > /usr/dt/lib/libXm.so.3
> > /usr/lib/libXm.so.3
> > root@openindiana:~# pkg contents -o pkg.name,path -a path='*/lib/libXm.so.3'
> > PKG.NAME  PATH
> > library/motif usr/dt/lib/libXm.so.3
> > library/motif usr/lib/libXm.so.3
> > library/motif usr/lib/libXm.so.3
> > library/motif usr/lib/libXm.so.3
> > 
> > If the file is not installed, you have to know the FMRI (full or partial) 
> > of the package:
> > root@openindiana:~# pkg contents -r -o pkg.name,path -a 
> > path='*/lib/libXm.so.3' motif
> > PKG.NAME  PATH
> > library/motif usr/dt/lib/libXm.so.3
> > library/motif usr/lib/libXm.so.3
> > library/motif usr/lib/libXm.so.3
> > library/motif usr/lib/libXm.so.3
> > 
> > although you may be able to go to the repository in your browser and search 
> > there (haven't tried).
> > 
> >> On Mar 25, 2020, at 01:49, Nicholas Papadonis 
> >>  wrote:
> >> 
> >> Also, I'm running OI-hipster-text-20161030.iso because I have an app that
> >> requires 32-bit support.
> >> 
> >> Thanks
> >> 
> >> On Wed, Mar 25, 2020 at 1:47 AM Nicholas Papadonis <
> >> nick.papadonis...@gmail.com> wrote:
> >> 
> >>> I'm trying to find which package includes a file as follows:
> >>> 
> >>> $ pkg search -l -H -o pkg.name libXm.so.3
> >>> 
> >>> However no results.
> >>> 
> >>> Any guidance appreciated.
> >>> 
> >>> 
> >>> 
> >>> 
> >> ___
> >> openindiana-discuss mailing list
> >> openindiana-discuss@openindiana.org
> >> https://openindiana.org/mailman/listinfo/openindiana-discuss
> >> 
> > 
> > ___
> > openindiana-discuss mailing list
> > openindiana-discuss@openindiana.org
> > https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Greek keyboard

[Aurelien Larcher]

Le Mardi 13 mars 2018, Nikola M a écrit :
> On 03/13/18 09:40 AM, Apostolos Syropoulos via openindiana-discuss wrote:
> >> Roll back data-xkb to previous version.
> >>
> >> pkg install data-xkb@2.22
> >>
> >> I guess they broke the keymaps again...
> > I did it but still I cannot type Greek in pluma,and in LibreOffice when I 
> > type ; + vowel I see'v. So I guess they did not broke keymaps, theyactualy 
> > f%^&* them...
> > A.S.
> 
> Maybe going back to BE where it is all working and figure out on what 
> exact osnet-incorporation and userland-incorporation it were last 
> working, and on what update it started not working.

This is since March 7. It seems that the update of data-xkb has sneaky side 
effects since I got two environments with same english+swedish keyboards to 
update differently: one working, one losing the accents.
> 
> And then pkg freeze of a working package and then update the rest
> (possibly with ' pkg change-facet 
> facet.require.consolidation/userland/userland-incorporation=false '
> and/or ' pkg uninstall userland-incorporation ' ? )
> 
> So it seems it is an upstream bug, that might affect other kernel 
> distributions, too?
> Is it in line to report it on both as OI  Issue and an upstream bug ?
> Benefits of Rolling-release with spotting bugs early and fixing upstream 
> projects, I presume..
> 
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>

-- 
Envoyé depuis mon Jolla
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Greek keyboard

[Aurelien Larcher]

Le Mardi 13 mars 2018, Apostolos Syropoulos a écrit :
> >Roll back data-xkb to previous version.
> >
> >pkg install data-xkb@2.22
> >
> >I guess they broke the keymaps again...
> 
> I did it but still I cannot type Greek in pluma,and in LibreOffice when I 
> type ; + vowel I see'v. So I guess they did not broke keymaps, theyactualy 
> f%^&* them...

I checked the commit logs and nothing seems to be obviously broken.
The weird thing now is that I updated three machines: the first one used for 
testing before merging the update works as expected, the laptop as well, but my 
home desktop does not...

Could you share /var/log/Xorg.0.log?

Also I wonder if MATE's user configuration files could be the culprit...
If the previous BE does not work that could be the case.

As Nikola suggested, pkg freeze data-xkb would force keeping 2.22 until the 
root cause is found.


> A.S.
> --
> Apostolos Syropoulos
> Xanthi, Greece
>  
> 
>

-- 
Envoyé depuis mon Jolla
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Greek keyboard

[Aurelien Larcher]

Roll back data-xkb to previous version.

pkg install data-xkb@2.22

I guess they broke the keymaps again...

Le Lundi 12 mars 2018, Apostolos Syropoulos via openindiana-discuss a écrit :
> Hello,
> I few days I updated one computer with the latestbits:
> SunOS nadya 5.11 illumos-e9bacc6d1a i86pc i386 i86pc
> I have noticed that the Greek keyboard is not working. In particular, I 
> cannot enter accents ordialitika (two little dots above certain vowels).Also, 
> I cannot type Greek letter in pluma at all!
> A.S.
> 
> --
> Apostolos Syropoulos
> Xanthi, Greece
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>

-- 
Envoyé depuis mon Jolla
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Pulseaudio now delivered as 64-bit by default.

[Aurelien Larcher]

Check the current sound level with audioctl.

Le Samedi 10 mars 2018, Francis.D a écrit :
> This morning I tested in liveDVD solaris 11.3 to see the audio support on
> the Laptop. There's a big difference. The sound is clear and heavy. Yet the
> drivers are the same.
> 
> Maybe the sound management under Mate is less efficient.
> 
> I did the same test on My desktop with the asus D1 sound card and the
> fabulous audiocmi driver and I don't have sound so much under solaris 11.3.
> 
> 
> 
> 2018-03-10 13:52 GMT-05:00 Aurelien Larcher :
> 
> > Hello,
> >
> > Le Samedi 10 mars 2018, Francis.D a écrit :
> > > After updating and rebooting, I have a good sound improvement on my
> > Lenovo
> > > Laptop T400.
> > >
> > > It's not as strong as under Linux in comparaison  but there is a good
> > > improvement.
> > >
> > > big thank
> >
> > Good to hear!
> >
> > With some chipsets it seems that the sound level can be further increased
> > since pulseaudio may only use the volume set by OSS as maximum limit.
> > The default setting for OSS is 75% of the maximum provided by the
> > hardware, so setting the volume control with audioctl may improve the
> > situation.
> >
> > >
> > > 2018-03-10 10:46 GMT-05:00 Aurélien Larcher  > >:
> > >
> > > > Hi,
> > > > Pulseaudio is now delivered as 64-bits in /usr/bin.
> > > > As usual Pulseaudio may not able to cope with its own configuration
> > files
> > > > when version or bitness is changed ...
> > > > If Pulseaudio does not start after reboot, you may need to remove the
> > > > configuration files in ~/.config/pulse/ ...
> > > >
> > > > Aurelien
> > > >
> > > > --
> > > > ---
> > > > Praise the Caffeine embeddings
> > > > ___
> > > > openindiana-discuss mailing list
> > > > openindiana-discuss@openindiana.org
> > > > https://openindiana.org/mailman/listinfo/openindiana-discuss
> > > >
> > > ___
> > > openindiana-discuss mailing list
> > > openindiana-discuss@openindiana.org
> > > https://openindiana.org/mailman/listinfo/openindiana-discuss
> > >
> >
> > --
> > Envoyé depuis mon Jolla
> > ___
> > openindiana-discuss mailing list
> > openindiana-discuss@openindiana.org
> > https://openindiana.org/mailman/listinfo/openindiana-discuss
> >
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>

-- 
Envoyé depuis mon Jolla
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Pulseaudio now delivered as 64-bit by default.

[Aurelien Larcher]

Hello,

Le Samedi 10 mars 2018, Francis.D a écrit :
> After updating and rebooting, I have a good sound improvement on my Lenovo
> Laptop T400.
> 
> It's not as strong as under Linux in comparaison  but there is a good
> improvement.
> 
> big thank

Good to hear!

With some chipsets it seems that the sound level can be further increased since 
pulseaudio may only use the volume set by OSS as maximum limit.
The default setting for OSS is 75% of the maximum provided by the hardware, so 
setting the volume control with audioctl may improve the situation.

> 
> 2018-03-10 10:46 GMT-05:00 Aurélien Larcher :
> 
> > Hi,
> > Pulseaudio is now delivered as 64-bits in /usr/bin.
> > As usual Pulseaudio may not able to cope with its own configuration files
> > when version or bitness is changed ...
> > If Pulseaudio does not start after reboot, you may need to remove the
> > configuration files in ~/.config/pulse/ ...
> >
> > Aurelien
> >
> > --
> > ---
> > Praise the Caffeine embeddings
> > ___
> > openindiana-discuss mailing list
> > openindiana-discuss@openindiana.org
> > https://openindiana.org/mailman/listinfo/openindiana-discuss
> >
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>

-- 
Envoyé depuis mon Jolla
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Fwd: [oi-dev] [call for testing] KPTI images

[Aurelien Larcher]

Le Vendredi 9 mars 2018, Francis.D a écrit :
> I need these driver (cmi8788) this driver is not on hipster depot.

The audiocmihd driver is in the hipster repository, you can install it from 
there.
> 
> My sound card is asus D1 on this desktop. I have no sound on all
> installation.
> 
> Sound problem on my Laptop Lenovo t400 and Desktop 990fx with asus D1.
> On old 151a publisher seems to be available. That's what you can see on the
> wiki.
> 
> I looking for solution for my desktop.
> 
> 
> regard
> 
> 2018-03-08 11:13 GMT-05:00 Aurélien Larcher :
> 
> > On Thu, Mar 8, 2018 at 4:52 PM, Francis.D  wrote:
> >
> > > Hi,
> > >
> > > It's possible to set old publisher (151a) for install
> > > audio/driver/audiocmihd and unset publisher after ?
> > >
> >
> > Why do you need to use the old publisher?
> > What is wrong with the current driver?
> >
> >
> > >
> > >
> > >
> > > 2018-03-07 12:49 GMT-05:00 Francis.D :
> > >
> > > > Hi,
> > > >
> > > > I did the real installation on my Lenovo T400 and all works perfectly.
> > > > The only problem is the sound. I don't have any sound. Even if the
> > > drivers
> > > > are installed.
> > > >
> > > >
> > > > result ocmmande
> > > >
> > > > ls -l
> > > >
> > > > total 224920
> > > > -rw-r--r-r---1 boo staff 1644 mars 7 12:58 audiosondriverproblem
> > > >
> > > >
> > > > Reference driver
> > > >
> > > > pci17aa,20f2
> > > > Vendor: Intel Corporation
> > > > Device: 82801I (ICH9 Family) HD Audio
> > > > Controller
> > > > Sub-Vendor: Lenovo
> > > > binding name:   pciexclass,0403
> > > > devfs path: /pci@0,0/pci17aa,20f2@1b
> > > > bus addr:   1b
> > > > pci path:   0,1b,0
> > > > compatible name:(pciex8086,293e.17aa.20f2.3)(
> > > > pciex8086,293e.17aa.20f2)(pciex8086,293e.3)(pciex8086,
> > > > 293e)(pciexclass,040300)(pciexclass,0403)(pci8086,293e.
> > > > 17aa.20f2.3)(pci8086,293e.17aa.20f2)(pci17aa,20f2)(
> > > > pci8086,293e.3)(pci8086,293e)(pciclass,040300)(pciclass,0403)
> > > > driver name:audiohd
> > > > instance:   0
> > > > driver state:   Attached
> > > > fm-errcb-capable:   TRUE
> > > > fm-ereport-capable: TRUE
> > > > ddi-no-autodetach:  1
> > > > audiohd_beep:   1
> > > > sample-rate:bb80
> > > > sample-bits:10
> > > > acpi-namespace: _SB_.PCI0.HDEF
> > > > assigned-addresses: 8300d810
> > > > reg:d800
> > > > compatible: pciex8086,293e.17aa.20f2.3
> > > > model:  Mixed Mode device
> > > > power-consumption:  1
> > > > devsel-speed:   0
> > > > interrupts: 2
> > > > subsystem-vendor-id:17aa
> > > > subsystem-id:   20f2
> > > > unit-address:   1b
> > > > class-code: 40300
> > > > revision-id:3
> > > > vendor-id:  8086
> > > >
> > > > regard
> > > >
> > > > 2018-03-06 9:01 GMT-05:00 Priyadarshan via openindiana-discuss <
> > > > openindiana-discuss@openindiana.org>:
> > > >
> > > >> On 2018-03-06 14:55, Till Wegmüller wrote:
> > > >>
> > > >>> Hi and welcome in the community
> > > >>>
> > > >>>
> > > >>> On 06.03.2018 14:48, Priyadarshan via openindiana-discuss wrote:
> > > >>>
> > > 
> > > 
> > >  Thank you very much for the clarification.
> > > 
> > >  I am coming from FreeBSD (since 2002, both on servers and
> > > workstations).
> > > 
> > >  I am just getting my feet wet with openindiana.
> > > 
> > >  I am studying Pro OpenSolaris, and getting to OpenSolaris Bible
> > later,
> > >  having my first install on a ThinkPad W541. I must say, I was
> > > impressed
> > >  on how smooth and flawless the install was, in comparison to Win 10,
> > >  FreeBSD 11 or even Linux Mint.
> > > 
> > >  From the overall feel of it I know this is home.
> > > 
> > >  I would like very much to contribute some packages, when (if ever)
> > > I'll
> > >  have enough expertise.
> > > 
> > > >>>
> > > >>> If you are studying the books you will definately have enough
> > > expertise.
> > > >>> The Packaging is made with Custom makefiles based on the current
> > > >>> solaris-gate.
> > > >>>
> > > >>> You can find documentation here:
> > > >>> https://wiki.openindiana.org/oi/Building+with+oi-userland
> > > >>>
> > > >>> The Source here: https://github.com/OpenIndiana/oi-userland
> > > >>>
> > > >>>
> > > >>> As I understand, then, it would be better to contribute to
> > openindiana
> > >  repositories, as found here:https://www.openindia

Re: [OpenIndiana-discuss] Sound issue [was Fwd: [oi-dev] [call for testing] KPTI images]

[Aurelien Larcher]

Le Mercredi 7 mars 2018, Priyadarshan via openindiana-discuss a écrit :
> On 2018-03-07 18:49, Francis.D wrote:
> 
> > Hi,
> > 
> > I did the real installation on my Lenovo T400 and all works perfectly. 
> > The only problem is the sound. I don't have any sound. Even if the drivers 
> > are installed. 
> > 
> > result ocmmande
> > 
> > ls -l
> > 
> > total 224920
> > -rw-r--r-r---1 boo staff 1644 mars 7 12:58 audiosondriverproblem
> > 
> > Reference driver
> > 
> > pci17aa,20f2
> > Vendor: Intel Corporation
> > Device: 82801I (ICH9 Family) HD Audio Controller
> > Sub-Vendor: Lenovo
> > binding name:   pciexclass,0403
> > devfs path: /pci@0,0/pci17aa,20f2@1b
> > bus addr:   1b
> > pci path:   0,1b,0
> > compatible name:
> > (pciex8086,293e.17aa.20f2.3)(pciex8086,293e.17aa.20f2)(pciex8086,293e.3)(pciex8086,293e)(pciexclass,040300)(pciexclass,0403)(pci8086,293e.17aa.20f2.3)(pci8086,293e.17aa.20f2)(pci17aa,20f2)(pci8086,293e.3)(pci8086,293e)(pciclass,040300)(pciclass,0403)
> > driver name:audiohd
> > instance:   0
> > driver state:   Attached
> > fm-errcb-capable:   TRUE
> > fm-ereport-capable: TRUE
> > ddi-no-autodetach:  1
> > audiohd_beep:   1
> > sample-rate:bb80
> > sample-bits:10
> > acpi-namespace: _SB_.PCI0.HDEF
> > assigned-addresses: 8300d810
> > reg:d800
> > compatible: pciex8086,293e.17aa.20f2.3
> > model:  Mixed Mode device
> > power-consumption:  1
> > devsel-speed:   0
> > interrupts: 2
> > subsystem-vendor-id:17aa
> > subsystem-id:   20f2
> > unit-address:   1b
> > class-code: 40300
> > revision-id:3
> > vendor-id:  8086
> > 
> > regard
> 
> Hi, 
> 
> I had the same issue, I believe that is common to all OpenSOlaris
> installs.

I believe this is a limitation of the OSS Pulseaudio backend which picks the 
first detected device.


 
> 
> The instructions in the comment at the bottom of this page helped me: 
> 
> https://distrowatch.com/table.php?distribution=xstreamos 
> 
> Copy and pasting here: 
> 
>  
> 
> Also like any Solaris based systems (Solaris 11.3 or OpenIndiana) when
> installing on real hardware 
> audio defaults to wrong device (audiohd#0), to switch default to
> audiohd#1 (to have sound in Firefox) 
> remove existing links 
> # rm /dev/audio 
> # rm /dev/audioctl 
> # rm /dev/dsp 
> create new 
> # ln -s /dev/sound/1 /dev/audio 
> # ln -s /dev/sound/1ctl /dev/audioctl 
> # ln -s /dev/dsp1 /dev/dsp 
> 
> to see settings before/after change use 
> $ ls -l /dev/audio 
> $ ls -l /dev/audioctl 
> $ ls -l /dev/dsp 
> to see available options 
> $ cat /dev/sndstat 
> $ ls /dev/sound 
> 
> === 
> 
> Priyadarshan
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>

-- 
Envoyé depuis mon Jolla
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] GCC6 build zone status

[Aurelien Larcher]

Only ocaml remains :)
So aside from openjdk-8 I'll have 100% gcc-6 compiled userland repository by 
the end of the day :) 

Le Samedi 2 décembre 2017, Aurelien Larcher a écrit :
> It seems that only ocaml and open-vm-tools remain since Andreas fixed 
> spidermonkey.
> Thanks :) 
> 
> Le Samedi 2 décembre 2017, Aurélien Larcher a écrit :
> > With some more help from Ken, remaining packages follow:
> > 
> > >
> > > > runtime/ocaml
> > >
> > > Needs update.
> > >
> > > > sysutils/open-vm-tools
> > >
> > > Needs update
> > >
> > > > library/ spidermonkey
> > >
> > > Needs gcc6 patches.
> > 
> > 
> > Updated page here https://wiki.openindiana.org/oi/GCC+6 and still openjdk-8
> > to be considered at some point.
> > 
> > That leaves 4 packages out of 1390.
> > 
> > Thanks
> > 
> > Aurélien
> > 
> > >
> > > >
> > > > If someone knows about Lua, there are issues with hexchat and libpeas
> > > > regarding luajit and LGI support.
> > > >
> > > > Kind regards
> > > >
> > > > Aurelien
> > > >
> > > > --
> > > > ---
> > > > Praise the Caffeine embeddings
> > > >
> > >
> > > --
> > > Envoyé depuis mon Jolla
> > 
> > 
> > 
> > 
> > -- 
> > ---
> > Praise the Caffeine embeddings
> >
> 
> -- 
> Envoyé depuis mon Joll

-- 
Envoyé depuis mon Jolla
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] GCC6 build zone status

[Aurelien Larcher]

It seems that only ocaml and open-vm-tools remain since Andreas fixed 
spidermonkey.
Thanks :) 

Le Samedi 2 décembre 2017, Aurélien Larcher a écrit :
> With some more help from Ken, remaining packages follow:
> 
> >
> > > runtime/ocaml
> >
> > Needs update.
> >
> > > sysutils/open-vm-tools
> >
> > Needs update
> >
> > > library/ spidermonkey
> >
> > Needs gcc6 patches.
> 
> 
> Updated page here https://wiki.openindiana.org/oi/GCC+6 and still openjdk-8
> to be considered at some point.
> 
> That leaves 4 packages out of 1390.
> 
> Thanks
> 
> Aurélien
> 
> >
> > >
> > > If someone knows about Lua, there are issues with hexchat and libpeas
> > > regarding luajit and LGI support.
> > >
> > > Kind regards
> > >
> > > Aurelien
> > >
> > > --
> > > ---
> > > Praise the Caffeine embeddings
> > >
> >
> > --
> > Envoyé depuis mon Jolla
> 
> 
> 
> 
> -- 
> ---
> Praise the Caffeine embeddings
>

-- 
Envoyé depuis mon Jolla
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] GCC6 build zone status

[Aurelien Larcher]

Thanks to Ken pylint and hal-cups-utils are fixed.
I have fixed and/or republished trousers, clamav, and nut.

Remaining packages follow: 
 
> desktop/hexchat

Issue in LUAjit: lj_vm.o is not compiled as PIC so linking fails. As it is 
generated from assembly code I do not know how to deal with it. 

> library/libpeas

Configuration error: Lua has no LGI support.
  
> runtime/clisp

Automake issue? No rule to make mbrtowc.o in gllib to produce libgnu.a
 
> runtime/ocaml

Needs update. 
 
> sysutils/open-vm-tools

Needs update 

> library/ spidermonkey

Needs gcc6 patches.
 
Update page here https://wiki.openindiana.org/oi/GCC+6

Another oustanding package on the list will be openjdk-8.

Thanks

Aurélien 

> 
> If someone knows about Lua, there are issues with hexchat and libpeas
> regarding luajit and LGI support.
> 
> Kind regards
> 
> Aurelien
> 
> -- 
> ---
> Praise the Caffeine embeddings
>

-- 
Envoyé depuis mon Jolla
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] No changes for over a month

[Aurelien Larcher]

Le Samedi 18 novembre 2017, Gary Mills a écrit :
> The web page:
> 
> https://wiki.openindiana.org/oi/Recent+Wiki+Changes
> 
> has not changed since 14 October.  Is something wrong again?

Always the same and unless we update it this will likely happen again.

> 
> 
> -- 
> -Gary Mills-  -refurb--Winnipeg, Manitoba, Canada-
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>

-- 
Envoyé depuis mon Jolla
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss