Re: [OpenIndiana-discuss] Rename network interface

[Thomas Wagner]

Hi Predrag,

instance numbering is made permanent in /etc/path_to_inst

Example:
grep e1000g path_to_inst
"/pci@0,0/pci1af4,1100@3" 0 "e1000g"

So yours schould print something like "grep rge"
"/someonepath" 0 "rge"
"/someotherpath" 1 "rge"

So essentially it is a swap of the single "0" and "1".
You could delete the line with "0" and rename the "1" on
the other line to "0". 
The last step is rebuild the boot-archive to include a 
copy of the path_to_inst file and then reboot.

bootadm update-archive

Regards
Thomas



On Wed, Nov 23, 2022 at 12:40:32PM +0100, Predrag Zecevic via 
openindiana-discuss wrote:
> Hi all,
> 
> I have moved OI (rpool and other pools) from one PC to another with almost
> no problems (had to re-instate zpool cache devices, since partition
> enumeration was not done for them during zpool import operation).
> 
> Old PC has installed external (PCI) Realtek Network card and it was
> recognized as rge0.
> New PC have onboard different model Realtek Network cardand it is now
> indexed as rge1.
> 
> As rge0 card is not present anymore, how can I make OI to rename rge1 to
> rge0?
> (for example, zones are configured to use rge0, etc)
> 
> With best regards.
> 

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

Re: [OpenIndiana-discuss] Upgraded to lastest hipster release today - pkg broken

[Thomas Wagner]

Russell,

I'm maintaining the SFE packages.

could you please verify something for me, once you have the
suggested workaround applied (moving symlink /usr/gnu/lib/amd64/libstdc++.so.6 
out of the way)

The version of these packages is interesting to me: 
please run the command and paste the output lines.

   pkg info gcc-runtime osnet-incorporation | grep FMRI


And then please see if you can upgrade gcc-runtime from the SFE
publisher to the gcc 7.5.0 version with the command:

pfexec pkg update -v sfe/system/library/gcc-runtime@7.5.0

If the "pkg" command still works afterwards, that would be good.
Please paste the output of the pkg update command as well.


The "pkg fix" command from the other email might restore the
moved away symlink of /usr/gnu/lib/amd64/libstdc++.so.6, so 
I would not recommend using pkg fix this time.

Regards,
Thomas

On Sun, Apr 05, 2020 at 12:00:40AM +0100, russell wrote:
> Hi
> 
> Performed a pkg upgrade today creating a new BE, now when I use pkg I get
> the following error
> 
> # pkg refresh --full
> Traceback (most recent call last):
>   File "/usr/bin/pkg", line 87, in 
>     import pkg.actions as actions
>   File "/usr/lib/python3.5/vendor-packages/pkg/actions/__init__.py", line
> 68, in 
>     globals(), locals(), [modname])
>   File "/usr/lib/python3.5/vendor-packages/pkg/actions/signature.py", line
> 37, in 
>     from . import generic
>   File "/usr/lib/python3.5/vendor-packages/pkg/actions/generic.py", line 49,
> in 
>     import pkg.variant as variant
>   File "/usr/lib/python3.5/vendor-packages/pkg/variant.py", line 36, in
> 
>     from pkg.misc import EmptyI
>   File "/usr/lib/python3.5/vendor-packages/pkg/misc.py", line 76, in
> 
>     import pkg.json as json
>   File "/usr/lib/python3.5/vendor-packages/pkg/json.py", line 24, in
> 
>     from rapidjson import loads, load, dumps, dump, JSONDecodeError
> ImportError: ld.so.1: python3.5: fatal: relocation error: file
> /usr/lib/python3.5/vendor-packages/rapidjson.cpython-35m.so: symbol
> __gxx_personality_v0: referenced symbol not found
> 
> How can I fix this or should I just activate the previous BE and delete the
> current boot environment?
> 
> TIA
> 
> 
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss

-- 


New Work!
Service rund um UNIX(TM), Wagner Network Services, Thomas Wagner
Solaris(TM), Linux(TM)Eschenweg 21, 89174 Altheim, Germany
Windows(TM)   TEL: +49-7340-919196, FAX: +49-731-9807711
VoIP, Netzwerke,  MOBILE/CELL: +49-175-2926064
Internet-Security EMAIL: wag...@wagner-net.com

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

Re: [OpenIndiana-discuss] Ext 2 Support

[Thomas Wagner]

Hi Bob,

thanks, you got the point. 
It is using old distro packages on a new distro.

So to me, it is: 
Users should consider contribution to the projects.

OI and SFE both can only get better by occational and/or continuos 
help from the smart users.

So the question is: How to do public relations and make
OI and SFE visible to possible contributors.
That should include to make visible that this is not a
swinning pool with sharks in it, instead a community of
nice and helpful people.

Regards,
Thomas

PS: No one ever asked nor offered contribution for the ext2 packages to be in 
the currenct SFE repos...
...invest in packages users ask for looks like most sensible.

On Mon, Apr 03, 2017 at 08:23:48AM -0500, Bob Friesenhahn wrote:
>  On Mon, 3 Apr 2017, Thomas Wagner wrote:
> 
> > Hi Gordon,
> >
> > could you be more specific in terms of what breaks?
> > SFE packages should not have more limitations then using
> > either the OI stack or the SFE stack (fuse, libfuse, ext2).
> 
>  I assume that the problem with "old SFE packages" is related to 
>  incompatiblity with OI Hipster (vs -dev).  It is not an issue with the SFE 
>  packages you maintain.
> 
>  Bob

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

Re: [OpenIndiana-discuss] Avahi daemons for Solaris/Illumos?

[Thomas Wagner]

Yes, an avahi implementation is there. I'm using it on Solaris 11.

E.g. used by "mpd" / "gmpc" so the music player client can find the 
the servers on the local LAN

Regards,
Thomas

On Thu, Feb 02, 2017 at 03:51:14PM +0100, Hans J Albertsson wrote:
> Are there any working, ready to install, avahi daemons for Solaris 11.3
> and/or oi hipster?
> 
> Hans J. Albertsson
> From my Nexus 5

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

Re: [OpenIndiana-discuss] OpenIndiana upgrade

[Thomas Wagner]

The missing link may be the every too often removed legacy package
name in a updated IPS package.
That way even SVR4 packages know about if an (IPS) package is 
present or not.

While developing one barely notice the missing legacy package names,
but "3rd"-party addons complain later.

Thomas

On Fri, Jan 13, 2017 at 05:29:36PM +0300, Alexander Pyhalov wrote:
>  On 01/13/17 05:20 PM, Carsten Grzemba wrote:
> 
> > I solved the problem by
> > - set non-sticky the openindiana.org publisher
> > - create a fake repo and publish there incorporation packages where 
> > dependency type is changed to optional, remove the obsoleted flag in dhcp 
> > package
> > # pkgrepo list -s /repos/fake-hipster/
> > PUBLISHER NAME O VERSION
> > fake-hipster consolidation/install/install-incorporation 
> > 0.5.11,5.11-0.151.1.9:20170108T144721Z
> > fake-hipster consolidation/ips/ips-incorporation 
> > 0.5.11,5.11-0.151.1.9:20170111T153531Z
> > fake-hipster consolidation/osnet/osnet-incorporation 
> > 0.5.11,5.11-0.151.1.9:20170108T132101Z
> > fake-hipster service/network/dhcp 
> > 0.5.11,5.11-2015.0.2.15619:20170113T123056Z
> > fake-hipster service/network/dhcp 0.5.11,5.11-0.151.1.9:20170106T113837Z
> > - add the fake-hipster repository to search before openindiana.org 
> > publisher
> > - at first replace (pkg update) the old incorporations with the old fake 
> > incorporation (optional dependencies)
> > - remove the fake repository
> > - do a normal upgrade to the latest hipster
> >
> 
>  Do later SRSS versions come as IPS packages? When I installed it last time, 
>  they were still SVR4-packaged, so IPS wouldn't be aware of it...
> 
>  -- 
>  Best regards,
>  Alexander Pyhalov,
>  system administrator of Southern Federal University IT department
> 

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

Re: [OpenIndiana-discuss] How many versions of libs/apps should OI provide?

[Thomas Wagner]

> No one of us might gain fame or get right, because of OI. But one can

Oh well. I wanted to type " get rich " ... but for this I need to get it right 
first..


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

Re: [OpenIndiana-discuss] How many versions of libs/apps should OI provide?

[Thomas Wagner]

Jim, thank you for your email, otherwise I would have missed the discussion on 
IRC.


Has been also considered what the requirements of a larger scale 3rd-party 
stack are? I see this comparable to a scaled up private software stack, which
is compiled by the user. You've already mentioned user stacks.


To a degree SFE can follow a number of changes in the underlying OS-Distro.
And there is an understanding, that it is the nature of an evolving OS-Distro
so constantly change and integrate new stuff.
But this almost always means continued extra work if someone builds ontop
of such a OS-Distro. (Example: Maintaning SFE on OI means multiple times
the effort then Solaris 11).

So I see there needs to be a balance between speedy changes on the OS-Distro
side and staying compatible to a degree, so that existing work of other
parties stays usable.

Additionally I would suggest to consider to what extent should a 
in-development-OS-Distro absob every possible software that could 
be integrated. 
It could be cool to have fancy packages people might find attracting.
But ... I'm mainly looking at the only small team currently working on 
the OS-Distro...
We can't risk people burn out or loose motivation. This is very
dangerous in OpenSource projects you know.
The hammer will fall and refresh-after-refresh of packages eats up 
future mantenance capacities needed to build a potential new release
of OI.

Thanks for wise and ojective arguments. I know this is an OS and work
we love, and this can't be always talked with objective arguments :)

Remember OI has had a time where meetings led to people being exhausted
and leaving. And I would appreciate every one stay fine with the project
and its goals. And the workload is okay for them.

I didn't want to bend the talks into a different direction, but I thought
it should be kept in mind.

If the OSdistro stays small but rock-solid plus a little maketing, that
might work.

No one of us might gain fame or get right, because of OI. But one can
have fun and get an OS-Distro which has cool features and packages.
And annoys less.

Thanks!
Thomas

PS: as a non native english writer, please excuse me if I might have missed the 
point


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

Re: [OpenIndiana-discuss] Cisco IPSec VPN

[Thomas Wagner]

I'm sure the tun pseudo interface "tun" can take multiple
clients using it at the same time.
I see that "tun" interface as an interface which can send
and recive packets through an API which is convenient to
e.g. openconnect, openvpn and so on.

Actual packages leave and enter the system through the regular
interaces of the global zone. This is the same as if a shared
or an exclusive interface would be used with a NGZ. Only exception
I can see is, if you assign an exclusive interface to a NGZ;
then this interface is out of reach for the tun interface.
But this would need an investigation to be sure.
And it would not change the game, as its the already crypted
stuff going over the wire.

Regards,
Thomas


On Thu, Nov 24, 2016 at 11:30:06PM +0100, benta...@chez.com wrote:
> Ok, I see.
> If I follow the SFE way, could I have an issue running OpenVPN server over 
> TUN on GZ and wanting to run Openconnect client over TUN in NGZ ? Like the 
> device /dev/tun is both used in GZ and NGZ.
> 
> Best regards.
> Ben
> 
> - Mail original -
> De: "Thomas Wagner" <tom-oi-disc...@tom.bn-ulm.de>
> À: "Discussion list for OpenIndiana" <openindiana-discuss@openindiana.org>
> Envoyé: Vendredi 25 Novembre 2016 10:16:51
> Objet: Re: [OpenIndiana-discuss] Cisco IPSec VPN
> 
> For SFE we've solved this by just adding the driver modules to the NGZ
> as dead files. So there is no install contraint regarding zones-type.
> That way the IPS dependency just matches in any case.
> 
> I use a driver match rule in the NGZ to get tun passed through:
> 
> 
> Thomas
> 
> On Thu, Nov 24, 2016 at 09:15:11PM +0100, benta...@chez.com wrote:
> > By the way, is there a way to install openconnect in a zone ?
> > I can't seem to get it running because tap driver doesn't want to install :
> > 
> > vpnzone# pkg install openconnect
> > Creating Plan (Running solver): |
> > pkg install: No matching version of network/openconnect can be installed:
> >   Reject:  
> > pkg://openindiana.org/network/openconnect@7.7.20161105-2016.1.0.0:20161119T064832Z
> >   Reason:  No version matching 'require' dependency driver/network/tap can 
> > be installed
> > 
> > Reject:  
> > pkg://openindiana.org/driver/network/tap@1.3.2-2016.0.0.0:20160730T021914Z
> > Reason:  This version is excluded by installed incorporation 
> > consolidation/userland/userland-incorporation@0.5.11-2016.1.0.7919
> > Reject:  
> > pkg://openindiana.org/driver/network/tap@1.3.2-2016.1.0.1:20161124T055026Z
> >  
> > pkg://openindiana.org/driver/network/tap@1.3.2-2016.1.0.1:20161124T172113Z
> > Reason:  Package supports image variant 
> > variant.opensolaris.zone=[global] but doesn't support this image's 
> > variant.opensolaris.zone (nonglobal)
> > 
> >   Reject:  
> > pkg://openindiana.org/network/openconnect@7.7.20161105-2016.1.0.0:20161119T114634Z
> >   Reason:  No version matching 'require' dependency driver/network/tap can 
> > be installed
> > 
> > 
> > Best regards.
> > Ben
> > 
> > - Mail original -
> > De: "Jim Klimov" <jimkli...@cos.ru>
> > À: "Discussion list for OpenIndiana" 
> > <openindiana-discuss@openindiana.org>, "Andrey Sokolov" 
> > <kere...@solaris.kirov.ru>
> > Envoyé: Vendredi 25 Novembre 2016 07:07:36
> > Objet: Re: [OpenIndiana-discuss] Cisco IPSec VPN
> > 
> > 16 но�бр� 2016 г. 14:02:44 CET, Andrey Sokolov 
> > <kere...@solaris.kirov.ru> пишет:
> > >Hi!
> > >I use
> > >http://pkg.openindiana.org/sfe/info/0/system%2Fnetwork%2Fvpnc%400.5.3%2C5.11-0.151.1.5%3A20120819T093748Z
> > >
> > >2016-11-14 15:35 GMT+03:00 Jim Klimov <jimkli...@cos.ru>:
> > >
> > >> Hi all,
> > >>
> > >> I am faced with a prospect of connecting to a remote network behind
> > >Cisco
> > >> IPSec VPN (the one with user, password, group and shared keys; will
> > >be
> > >> practically trying sometime soon this week). Should I expect it to
> > >work in
> > >> OI Hipster out of the box? Are there docs/blogs on it, or would
> > >Oracle docs
> > >> I found so far (some hints about conf files and then ipadm tun
> > >commands) be
> > >> relevant here? Or should I try some other OS right away?
> > >>
> > >> TIA, Jim
> > >> --
> > >> Typos courtesy of K-9 Mai

Re: [OpenIndiana-discuss] Cisco IPSec VPN

[Thomas Wagner]

For SFE we've solved this by just adding the driver modules to the NGZ
as dead files. So there is no install contraint regarding zones-type.
That way the IPS dependency just matches in any case.

I use a driver match rule in the NGZ to get tun passed through:


Thomas

On Thu, Nov 24, 2016 at 09:15:11PM +0100, benta...@chez.com wrote:
> By the way, is there a way to install openconnect in a zone ?
> I can't seem to get it running because tap driver doesn't want to install :
> 
> vpnzone# pkg install openconnect
> Creating Plan (Running solver): |
> pkg install: No matching version of network/openconnect can be installed:
>   Reject:  
> pkg://openindiana.org/network/openconnect@7.7.20161105-2016.1.0.0:20161119T064832Z
>   Reason:  No version matching 'require' dependency driver/network/tap can be 
> installed
> 
> Reject:  
> pkg://openindiana.org/driver/network/tap@1.3.2-2016.0.0.0:20160730T021914Z
> Reason:  This version is excluded by installed incorporation 
> consolidation/userland/userland-incorporation@0.5.11-2016.1.0.7919
> Reject:  
> pkg://openindiana.org/driver/network/tap@1.3.2-2016.1.0.1:20161124T055026Z
>  
> pkg://openindiana.org/driver/network/tap@1.3.2-2016.1.0.1:20161124T172113Z
> Reason:  Package supports image variant variant.opensolaris.zone=[global] 
> but doesn't support this image's variant.opensolaris.zone (nonglobal)
> 
>   Reject:  
> pkg://openindiana.org/network/openconnect@7.7.20161105-2016.1.0.0:20161119T114634Z
>   Reason:  No version matching 'require' dependency driver/network/tap can be 
> installed
> 
> 
> Best regards.
> Ben
> 
> - Mail original -
> De: "Jim Klimov" <jimkli...@cos.ru>
> À: "Discussion list for OpenIndiana" <openindiana-discuss@openindiana.org>, 
> "Andrey Sokolov" <kere...@solaris.kirov.ru>
> Envoyé: Vendredi 25 Novembre 2016 07:07:36
> Objet: Re: [OpenIndiana-discuss] Cisco IPSec VPN
> 
> 16 ноября 2016 г. 14:02:44 CET, Andrey Sokolov 
> <kere...@solaris.kirov.ru> пишет:
> >Hi!
> >I use
> >http://pkg.openindiana.org/sfe/info/0/system%2Fnetwork%2Fvpnc%400.5.3%2C5.11-0.151.1.5%3A20120819T093748Z
> >
> >2016-11-14 15:35 GMT+03:00 Jim Klimov <jimkli...@cos.ru>:
> >
> >> Hi all,
> >>
> >> I am faced with a prospect of connecting to a remote network behind
> >Cisco
> >> IPSec VPN (the one with user, password, group and shared keys; will
> >be
> >> practically trying sometime soon this week). Should I expect it to
> >work in
> >> OI Hipster out of the box? Are there docs/blogs on it, or would
> >Oracle docs
> >> I found so far (some hints about conf files and then ipadm tun
> >commands) be
> >> relevant here? Or should I try some other OS right away?
> >>
> >> TIA, Jim
> >> --
> >> Typos courtesy of K-9 Mail on my Samsung Android
> >>
> >> ___
> >> 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
> 
> Thanks,
> 
> In the end vpnc did work for me; also I saw that openconnect could connect to 
> Juniper/Cisco SSL VPNs... so I couldn't resist and now both are packaged in 
> OI/Hipster userland ;)
> 
> Thanks,
> Jim
> --
> Typos courtesy of K-9 Mail on my Samsung Android
> 
> ___
> 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
> 

-- 
-- 
Thomas Wagner


Service rund um UNIX(TM), Wagner Network Services, Thomas Wagner
Solaris(TM), Linux(TM)Eschenweg 21, 89174 Altheim, Germany
Windows(TM)   TEL: +49-731-9807799, FAX: +49-731-9807711
Telekommunikation, LAN,   MOBILE/CELL: +49-171-6135989
Internet-Service, Elektronik  EMAIL: wag...@wagner-net.com

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

Re: [OpenIndiana-discuss] Cisco IPSec VPN

[Thomas Wagner]

Please note, that pkg.openindiana.org/sfe doesn't get updats since years.
We just procastinate a full deprecation. So this means, if someone wants
to take that over, then get in contact.

But there is no strong need for this, as the party is now
 athttp://sfe.opencsw.org 

An automatic build system updates the packages and (usually) there are
much more uptodate versions. It contains LibreOffice4 as well.

The source for the build recipes is the same, "spec-files-extra".

About VPN, I'm using openconnect (and openvpn) on a daily basis.

If you need an updated version of vpnc, then please drop me a note.

Regards,
Thomas



On Wed, Nov 16, 2016 at 04:02:44PM +0300, Andrey Sokolov wrote:
> Hi!
> I use
> http://pkg.openindiana.org/sfe/info/0/system%2Fnetwork%2Fvpnc%400.5.3%2C5.11-0.151.1.5%3A20120819T093748Z
> 
> 2016-11-14 15:35 GMT+03:00 Jim Klimov :
> 
> > Hi all,
> >
> > I am faced with a prospect of connecting to a remote network behind Cisco
> > IPSec VPN (the one with user, password, group and shared keys; will be
> > practically trying sometime soon this week). Should I expect it to work in
> > OI Hipster out of the box? Are there docs/blogs on it, or would Oracle docs
> > I found so far (some hints about conf files and then ipadm tun commands) be
> > relevant here? Or should I try some other OS right away?

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

Re: [OpenIndiana-discuss] ntfs-3g

[Thomas Wagner]

Does this work:
ntfs-3g /dev/dsk/c4t0d0p1 /mnt

Regards,
Thomas

On Sun, Sep 25, 2016 at 06:09:23PM +, Apostolos Syropoulos via 
openindiana-discuss wrote:
> 
> 
>  Hello,
> 
> I kust wanted to check ntfs-3g and I downloaded and installed the packages 
> from
> 
> http://jp-andre.pagesperso-orange.fr/openindiana-ntfs-3g.html
> 
> However, it seems that it is not working.
> 
> 
> # rmformat -l
> Looking for devices...
> 1. Logical Node: /dev/rdsk/c2t3d0p0
> Physical Node: /pci@0,0/pci1849,4391@11/cdrom@3,0
> Connected Device: HL-DT-ST DVDRAM GH24NSD1  LG00
> Device Type: DVD Reader/Writer
> Bus: 
> Size: 
> Label: 
> Access permissions: 
> 2. Logical Node: /dev/rdsk/c4t0d0p0
> Physical Node: /pci@0,0/pci1849,4396@13,2/storage@2/disk@0,0
> Connected Device: SanDisk  Cruzer Blade 1.00
> Device Type: Removable
> Bus: USB
> Size: 30,5 GB
> Label: 
> Access permissions: Medium is not write protected.
> # ntfs /dev/rdsk/c4t0d0p0 /mtn
> NTFS signature is missing.
> Failed to mount 
> '/devices/pci@0,0/pci1849,4396@13,2/storage@2/disk@0,0:q,raw': Invalid 
> argument
> The device '/devices/pci@0,0/pci1849,4396@13,2/storage@2/disk@0,0:q,raw' 
> doesn't seem to have a valid NTFS.
> Maybe the wrong device is used? Or the whole disk instead of a
> partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
> 
> Fdisk shows the following:
> 
> Partition   StatusType  Start   End   Length%
> =   ==  =   ===   ==   ===
> 1   ActiveIFS: NTFS 1  38903890100
> 
> The USB thumb disk has been formatted using a machine running Windows 7.
> 
> A.S.
> 
> 
> 
> --
> Apostolos Syropoulos
> Xanthi, Greece

-- 

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

Re: [OpenIndiana-discuss] GCC 5.4 added to the repository

[Thomas Wagner]

Thank you Alex!

Looks good for libgcc_s.so and libstdc++.so.6
Only it makes me wonder, why the elfdump output for none of the
other (non-gcc-runtime-)libs prints "[ LAZY ]" the line right
before the lib.

Interesting is, that even 4.9 has none of the libs with "[ LAZY ]".

As having "lazy load" for libs is there to improve startup latency
for binaries/libs, I would like to ask if someone might find an 
example with actually printing "[ LAZY ]".
This can be a completely different binary/project but compiled
with enther the g++ 4.9 or the new g++ 5 version. It should print
"[ LAZY ]" for at least one library. Then I would be completely
happy.

Best Regards,
Thomas


On Tue, Sep 06, 2016 at 05:13:10PM +0300, Alexander Pyhalov wrote:
>  On 09/ 6/16 04:57 PM, Thomas Wagner wrote:
[...]
> >
> > ...
> >   [2] somelib.so
> >   [3] [ LAZY ]  <- delayed load/binding, libc.so can bind funcs 
> > earlier then libgcc_s.so
> >   [4] libgcc_s.so
> > ...
> >   [5] someotherlib.so
> >   [6] [ LAZY ]  <- delayed load/binding, libc.so can bind funcs 
> > earlier then libstdc++.so
> >   [7] libstdc++.so
> >
> 
>  Hi.
> 
>  For g++ 5:
> 
>  Dynamic Section:  .dynamic
>   index  tagvalue
> [0]  NEEDED0x2ad   libstdc++.so.6
> [1]  NEEDED0x2ee   libm.so.2
> [2]  NEEDED0x2f8   librt.so.1
> [3]  NEEDED0x303   libgcc_s.so.1
> [4]  NEEDED0x2c8   libc.so.1
> [5]  INIT  0x8051030
> [6]  FINI  0x8051050
> [7]  RUNPATH   0x311   /usr/gcc/5/lib
> [8]  RPATH 0x311   /usr/gcc/5/lib
> [9]  HASH  0x80501c0
>[10]  STRTAB0x8050630
>[11]  STRSZ 0x520
>[12]  SYMTAB0x8050420
>[13]  SYMENT0x10
>[14]  SUNW_SYMTAB   0x80502e0
>[15]  SUNW_SYMSZ0x350
>[16]  SUNW_SORTENT  0x4
>[17]  SUNW_SYMSORT  0x8050be4
>[18]  SUNW_SYMSORTSZ0x50
>[19]  CHECKSUM  0x5bf6
>[20]  VERNEED   0x8050b50
>[21]  VERNEEDNUM0x2
>[22]  FINI_ARRAY0x8061318
>[23]  FINI_ARRAYSZ  0x8
>[24]  INIT_ARRAY0x8061320
>[25]  INIT_ARRAYSZ  0x8
>[26]  PLTRELSZ  0x40
>[27]  PLTREL0x11
>[28]  JMPREL0x8050c64
>[29]  REL   0x8050c34
>[30]  RELSZ 0x70
>[31]  RELENT0x8
>[32]  SYMINFO   0x805013c
>[33]  SYMINSZ   0x84
>[34]  SYMINENT  0x4
>[35]  DEBUG 0
>[36]  FLAGS 0   0
>[37]  FLAGS_1   0   0
>[38]  SUNW_STRPAD   0x200
>[39]  SUNW_LDMACH   0x3eEM_AMD64
>[40]  PLTGOT0x8061078
> [41-51]  NULL  0
> 
> 
>  For g++ 4.9:
>  Dynamic Section:  .dynamic
>   index  tagvalue
> [0]  NEEDED0x2c3   libstdc++.so.6
> [1]  NEEDED0x304   libm.so.2
> [2]  NEEDED0x30e   librt.so.1
> [3]  NEEDED0x319   libgcc_s.so.1
> [4]  NEEDED0x2de   libc.so.1
> [5]  INIT  0x80510c0
> [6]  FINI  0x80510f0
> [7]  HASH  0x80501c0
> [8]  STRTAB0x8050640
> [9]  STRSZ 0x527
>[10]  SYMTAB0x8050430
>[11]  SYMENT0x10
>[12]  SUNW_SYMTAB   0x80502e0
>[13]  SUNW_SYMSZ0x360
>[14]  SUNW_SORTENT  0x4
>[15]  SUNW_SYMSORT  0x8050bfc
>[16]  SUNW_SYMSORTSZ0x50
>[17]  CHECKSUM  0xaddb
>[18]  VERNEED   0x8050b68
>[19]  VERNEEDNUM0x2
>[20]  PLTRELSZ  0x40
>[21]  PLTREL0x11
>[22]  JMPREL0x8050c7c
>[23]  REL   0x8050c4c
>[24]  RELSZ 0x70
>[25]  RELENT0x8
>[26]  SYMINFO   0x805013c
>[27]  SYMINSZ   0x84
>[28]  SYMINENT  0x4
>[29]  DEBUG 0
>[30]  FLAGS 0   0

Re: [OpenIndiana-discuss] GCC 5.4 added to the repository

[Thomas Wagner]

Hi Aurelien,

it would be very cool if someone could send me / the list the output
of "elfdump -d" on a compiled binary with C++ code. If that is not
available, then regular C-code is okay too. e.g. gcc -o hello hello.c
I have no test system at hand (have only older hipster on disk).

What I would appreciated to see would be a configuration that has
"[ LAZY ]"-load removed (only) for gcc runtime libs.

Excample "good":

...
 [2] somelib.so
 [3] libgcc_s.so
...
 [5] someotherlib.so
 [6] libstdc++.so


Excample "bad":

...
 [2] somelib.so
 [3] [ LAZY ]  <- delayed load/binding, libc.so can bind funcs earlier 
then libgcc_s.so
 [4] libgcc_s.so
...
 [5] someotherlib.so
 [6] [ LAZY ]  <- delayed load/binding, libc.so can bind funcs earlier 
then libstdc++.so
 [7] libstdc++.so

This removed "LAZY"-load avoids situation where uncatched C++ exceptions
are falling through into into library /usr/lib/libc.so which normally can't
handle them, so binary core dumps.
Prominent example is "filezilla".

In SFEgcc we set "-zinterpose" to have the resulting binaries link (only) the
gcc runtime without the LAZY flag.


Thanks much!
Thomas


On Tue, Sep 06, 2016 at 03:34:21PM +0200, Aur??lien Larcher wrote:
> Hello,
> I wrote a short post about it:
> 
> https://www.openindiana.org/2016/09/06/gcc-5-4-now-available-as-testing-compiler/
> 
> Thanks go to Rich Lowe for his fixes to the linker and to Alexander
> for patches and thorough testing.
> 
> Please comment if you think about additional information which should
> be provided.
> Best regards,
> 
> Aurelien
> 
> -- 
> ---
> Praise the Caffeine embeddings
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 

-- 
-- 
Thomas Wagner


Service rund um UNIX(TM), Wagner Network Services, Thomas Wagner
Solaris(TM), Linux(TM)Eschenweg 21, 89174 Altheim, Germany
Novell(TM), Windows(TM)   TEL: +49-731-9807799, FAX: +49-731-9807711
Telekommunikation, LAN,   MOBILE/CELL: +49-171-6135989
Internet-Service, Elektronik  EMAIL: wag...@wagner-net.com

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

Re: [OpenIndiana-discuss] ????????: Looking back at the past 8 months...

[Thomas Wagner]

On Sat, Aug 20, 2016 at 03:53:31PM +0200, Aur??lien Larcher wrote:
> > There is no 64bit binary!
> 
> Most likely you installed from SFE's repository.

Possible, what does 
pkg info sfe/library/libglew 
print?

Regards,
Thomas

-- 

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

Re: [OpenIndiana-discuss] Dovecot error on OpenIndiana

[Thomas Wagner]

Hi,

you might want to explore two spec files building postfix and dovecot
together. I used them so make up a SMTP-AUTH and IMAP mailserver.
(SFE / spec-files-extra project)

Here are the spec files to build the packages:
   
https://sourceforge.net/p/pkgbuild/code/HEAD/tree/spec-files-extra/trunk/SFEdovecot.spec
   
https://sourceforge.net/p/pkgbuild/code/HEAD/tree/spec-files-extra/trunk/SFEpostfix.spec

and here are the prebuilt packages:

   http://sfe.opencsw.org/quickrepolinks 
(these are not csw packages, only kind hosting)

Regards,
Thomas

On Sun, Aug 14, 2016 at 08:56:25AM -0500, Bob Friesenhahn wrote:
>  On Sun, 14 Aug 2016, Sakuma, Koshiro wrote:
> 
> > Hi, Bod,
> >
> > Sorry again.  I would like to know about option of postfix installation.
> > Please see below.  Is this correct option for TLS and BerkeleyDB for new
> > OpenIndiana?
> >
> > make makefiles CCARGS='-DUSE_SASL_AUTH -DDEF_SASL_SERVER=\"dovecot\" \
> > -DUSE_TLS -I/usr/include/openssl \
> > -DHAS_DB -I/usr/include' \
> > AUXLIBS="-R/usr/include/openssl -L/usr/lib -lssl -lcrypto \
> > -R/usr/lib -L/usr/lib -ldb
> 
>  I am unable to answer this question since I am still using sendmail (and 
>  would like to configure to use TLS with sasl and cyrus-sasl, which I think 
>  is included in OmniOS sendmail).  I am experiencing this under OmniOS which 
>  is much more spartan and "do it yourself" than OpenIndiana.
> 
>  It is interesting that dovecot is a SASL option.
> 
>  Bob

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

Re: [OpenIndiana-discuss] Plumbing tun0 in a non-global zone

[Thomas Wagner]

you have entries for tun and tap in /etc/name_to_major?

and the modules actually do load?

example:
modinfo  | egrep "  tun|  tap"
277 f8ba   2de8 227   1  tun (TUN/TAP driver 1.1.0 12/23/2013)
288 f8bfd000   3528 290   1  tap (TUN/TAP driver 1.1.0 12/23/2013)

In my openvpn setup I have no extra plumbing, openvpn does it for me IIRC.

in the config file:
dev tun
tun-mtu 1400   (because running over a mtu 1492 ADSL line)

Regards,
Thomas

On Thu, Mar 10, 2016 at 03:45:43PM +, Jonathan Adams wrote:
> I know I've done this before, I just can't find it anywhere.
> 
> I have a zone with OpenVPN in it, that needs to plumb tun0.
> 
> I've added the "match" for the tun device to the global zone, I've
> installed tuntap in the zone and the global zone ...
> 
> I have a suspicion that I need to set something in "limitpriv" to allow the
> ability to plumb/unplumb interfaces in the zone, but I can't for the life
> of me remember the specifics.
> 
> Does anyone do this, can they remind me how to do it?
> 
> Thanks
> 
> Jon
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
> 


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

Re: [OpenIndiana-discuss] Ganglia?

[Thomas Wagner]

Hi Richard,

in "SFE" we have a old SFEganglia.spec. If you want to share the
way you've built ganglia and prerequisites, then this could be a
chance to work on it.

Regards,
Thomas

On Fri, Feb 19, 2016 at 10:26:57AM -0800, Richard Feltstykket wrote:
> Hi list,  
> 
>   
> 
> I've been attempting to get a stable install of ganglia to monitor my 
> 
> growing stable of openindiana fileservers.
> 
>   
> 
> I was able to compile the latest ganglia-monitor source with a few
> 
> patches and get it to run at least, but a lot of the metrics appear   
> 
> broken.   
> 
>   
> 
> I also tried the OpenCSW packages, and found they had generally   
> 
> the same issues.  
> 
>   
> 
> By any chance has anyone else done any work on this?  I just don't
> 
> want to reinvent the wheel :-)
> 
>   
> 
> Thanks!   
> 
> Richard
> work on it.

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

Re: [OpenIndiana-discuss] Updated OpenIndiana FAQ (2nd draft)

[Thomas Wagner]

On Sun, Feb 07, 2016 at 03:56:50PM -0500, Michael Kruger wrote:
>  Hi All,
> 
>  Based on feedback, I've reworked the FAQ a bit more.
>  Several sections have been reworded and re-ordered.
> 
>  http://hub.openindiana.ninja/?q=content/faq
> 
>  Feel free to comment
>  Michael

Yes, thanks. I would mention that the OS brings a basic set of
packages with it. This is important, as people should not walk
away just because their currently most important packages
aren't present today.

Then 3rd party packaging projects come into play, each with a
bit different goals but add a lot more packages if interest.
I would add a link to the overview page for those repos.

For contribution section, it would be nice to mention that
people can help the 3rd-party packages as well and share the
work, if they don't see themselves contributing to the OS itself. 

Regards,
Thomas

-- 

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

Re: [OpenIndiana-discuss] 32-bit support in OpenIndiana Hipster

[Thomas Wagner]

> > The next OI Hipster snapshot will no pretend to support 32bit CPUS.
The question is here, booting the 32-bit Kernel. That might be abandoned.
32-bit programs can continue to run as well as 64-bit programs

If the question is about changing the directory layout, I would vote
for *don't* change it.

If the directory layout is kept as it is, then you can for instance
deliver a 64-bit-only program /usr/bin/ and its libs into /usr/lib/%arch64/

I would not start delivering 64-bit-libs into /usr/lib/ as this leads to all
sorts of confusions during the transition phase.

Perl and python are special cases, as they usually have their own directory
space for modules and binary objects. Making perl 64-bit would mean *all*
consumers of perl which add extra binary objects need to recompile everything
at one point in time. SFE binary repo would such an example, and all users
who maintain reihr own perl modules.

If Perl changes version numbers in a way that a new /usr/perl/m.n directory
is created, then this would be a suitable point in time where it can change
from 32- to 64-bit. Then only users with private perl modules will be "hit".

So, I would say: Don't break with your own old binaries, then fine.

Thomas

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

[OpenIndiana-discuss] LibreOffice4 updated 4.4.7.2

[Thomas Wagner]

Hi all,

LibreOffice4 is updated to 4.4.7.2  (prev: 4.4.5.2)

I'm looking for testers, so please install and try a
few things in LO. 

In any case I would like to hear from you if you had
success or errors.

Repo/Install instructions here: http://sfe.opencsw.org/libreoffice-4.4.7.2

If you feel the package is running fine, then don't hesitate
to spread the word! 

If you tweet about it, please include a screenshot and use the
hashtag: #SFE and your OS, e.g. #OpenIndiana or #Solaris

Backtracks are welcome as well!

Regards,
Thomas


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

[OpenIndiana-discuss] LibreOffice4 updated 4.4.7.2

[Thomas Wagner]

Hi all,

LibreOffice4 is updated to 4.4.7.2  (prev: 4.4.5.2)

I'm looking for testers, so please install and try a
few things in LO. 

In any case I would like to hear from you if you had
success or errors.

Repo/Install instructions here: http://sfe.opencsw.org/libreoffice-4.4.7.2

If you feel the package is running fine, then don't hesitate
to spread the word! 

If you tweet about it, please include a screenshot and use the
hashtag: #SFE and your OS, e.g. #OpenIndiana or #Solaris

Backtracks are welcome as well!

Regards,
Thomas



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

Re: [OpenIndiana-discuss] /hipster-2015 and /localhostoih gcc mess up (second time)

[Thomas Wagner]

Soden am Taunus, Germany
>  Company registration: Amtsgericht Königstein (Germany), HRB 7303
>  Managing director:Phil Douglas
> 
>  http://www.2e-systems.com/ - Making your business fly!
> 
>  ___
>  openindiana-discuss mailing list
>  openindiana-discuss@openindiana.org
>  http://openindiana.org/mailman/listinfo/openindiana-discuss
> 

-- 
-- 
Thomas Wagner


Service rund um UNIX(TM), Wagner Network Services, Thomas Wagner
Solaris(TM), Linux(TM)Eschenweg 21, 89174 Altheim, Germany
Novell(TM), Windows(TM)   TEL: +49-731-9807799, FAX: +49-731-9807711
Telekommunikation, LAN,   MOBILE/CELL: +49-171-6135989
Internet-Service, Elektronik  EMAIL: wag...@wagner-net.com

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

Re: [OpenIndiana-discuss] Hipster upgrade problem

[Thomas Wagner]

in the meantime, you can start immediatly setting 
up an SFE environment, if you can read Japanese.

https://pt.osdn.jp/projects/jposug/wiki/howtouse



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

Re: [OpenIndiana-discuss] Hipster upgrade problem

[Thomas Wagner]

On Sun, Nov 15, 2015 at 11:16:00PM +, Stefan M??ller-Wilken wrote:
> 
> Full 'thumbs up' to all you've said. I admit that I've treated SFE as part of 
> the core.  My bad, I'll fix that following your suggestions and report.
 
thanks :)

> Regarding maintaining and supporting OI, I know what you mean: I'm always 
> happy to see someone coming back to my NWAM wiki topic. :-)
> 
> And I agree there is a lot of room for PR - just alone from looking at the 
> website. :-)
> 
> As for contributing packages, I think it would help to have a full tutorial 
> starting wirh preparing a packaging zone, downloading a tgz package from a 
> source repository (e. g. latest tomcat) over creating IPS metadata to 
> packaging and lastly delivering to the maintainers placed on the wiki. There 
> was one for SFE I remember being fairly complex - but we'd need this for dev 
> with the minimum number of steps just to upgrade an existing package... or is 
> this already available somewhere on the net?

Yes, for the SFE part, it has been sitting on the mediawiki of pkgbuild. The 
Wiki Source
files are still in a safe place (my ZFS disk :) but I got mad of waiting on the 
sourceforge
hosted  mediawiki install getting hacked after a day.

So if someone has an idea on converting mediawiki pages to a modern wiki, please
let me know very soon, that would help a lot.


Getting a SFE build environment is either by a running a single script called 
bootstrap-sfe*,
or, the already mentioned longer step guide from the wiki. But that guide is 
currently locked
in the offline mediawiki pages.

If at least two people raise hands, I'll put up a draft page somewhere which 
describes the usage
of the boostrap-sfe-* script. Then the build-recipes form the SFE repository 
can be built
locally. Those recipes usually run on OpenIndiana OI151a[89], Hipster, Solaris 
11 (12), OmniOS.
And the LibreOffice for Hipster and Solaris 11 is built from this stack.

Regards,
Thomas


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

Re: [OpenIndiana-discuss] Hipster upgrade problem

[Thomas Wagner]

Some comments on upgrades. Some comments on maintaining projects.

_if_ you change the OS-distribution, it is indeed recommended
to *uninstall* the 3rd-party packages before upgrade attempt.
IPS is pedantic for a good reason.

That means, you can't expect 3rd-party packages to fit
into a different, new OS-distribution.

For packages from http://sfe.opencsw.org, you will see that every major
OS distrobution has it's own IPS repository matching the OS.


>  As I see, you has sfe packages installed. First of all, I'd create new BE to 
>  experiment with,
>  uninstalled all SFE packages, updated it to Hipster and added 
>  http://sfe.opencsw.org/localhostoih/en/index.shtml
>  repository for SFE packages.
> 
>  Perl 5.10 was removed, but packages from old SFE repository still depend on 
>  it, so you can't update.

Agreed.
It is recommended to...
 * beadm create a backup-bootenvironment  (your insurance)
 * save list of all installed 3rd-party packageds
   pkg list | egrep "sfe|localhost" > USERHOME/my-old-sfe-packages

 * make an extra backup of the 3rd-party packages config files (really!)
   (e.g. /etc/ or where else config is stored)

 * uninstall all 3rd-party-packages before the OS upgrade.
 * remove the old SFE publisher

Do the major OS distribution upgrade

After the upgrade:
 * re-add the *new* SFE publisher for the *new* OS distribution
 * install those 3rd party packages you still want to run
 * restore the configuration for the 3rd party packages


In an optimal world with lots of paid supporters, the OS distribution
and 3rd party Package repositories would be synchronized. They would
contain a complete set of automatic "renamed-to" and "obsolete" 
meta-packages which allow seamless upgrades.

But you know, not a single one of all the maintainers are paid for the
OpenIndiana and SFE projects.

I believe all the maintainers are still paid, but in a non-monetary
currency. They see you are using their work and have fun or profit of it.

And the biggest success for maintainers might be, seeing users turn
into mainainers and help getting the project forward. This includes
programmers/hackers as well as users writing documentaion or do community
or public relations! (blogging, presentatations, usergroups)

Regards,
@tomww







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

Re: [OpenIndiana-discuss] New packaged LibreOffice4

[Thomas Wagner]

Hi Nikola,

thank you for the error output, that helps a lot.

Answer and to-do inline...

On Sun, Nov 08, 2015 at 09:39:08PM +0100, Nikola M wrote:
>  It is saying this when trying to save ODT file:
> 
>  $ /usr/lib/libreoffice/program/soffice
> 
>  (soffice:3815): GLib-CRITICAL **: g_hash_table_foreach_remove_or_steal: 
>  assertion 'version == hash_table->version' failed
>  ld.so.1: soffice.bin: fatal: libraptor2-lo.so.0: open failed: No such file 
>  or directory
>  ld.so.1: soffice.bin: fatal: relocation error: file 
>  /usr/lib/libreoffice/program/librdf-lo.so.0: symbol 
>  raptor_xmlschema_datatypes_namespace_uri: referenced symbol not found
>  ld.so.1: soffice.bin: fatal: relocation error: file 
>  /usr/lib/libreoffice/program/../program/libunordflo.so: symbol 
>  librdf_new_world: referenced symbol not found

I did a check on the build machine which has the latest packages installed
including the prerequisite libs. It propperly finds file libraptor2-lo.so.0.
So we should have a closer look on your specific set of packages.

I can see two places where to dig deeper:
a) parallel installed openoffice (right?) and loffice stumbling over wrong libs
b) verify that *old* revisions of the prerequisite libs are uninstalled and do 
a 
   "pkg fix" for loffice and see if files delivered are complete.

about a)
 I would say this is possible but not looked at in the first attempt.

about b)
 I have the plan to inject "renamed-to" meta-packages into the repo, so
 a normal user gets with an update just the old packages deleted and have only
 the new ones remain installed.

In the meantime you could see for duplicate package names from the
localhostoih publisher and remove all the older packages of the same
name, e.g. remove /gnu/something and leave /g++/something on the system.

 pkg list -v | grep localhostoih


If you send me the output of the above command as a pastebin or priv email,
then I can help finding the outdated packages. That would as well help me to
verify/identify those older packages which need a automatic uninstall 
(renamed-to),
because they have been renamed from /gnu/ to /g++/ or similar.
As the repo localhostoih is a development repo, from time to time it happens
that we need to manually clean up.

Regards,
Thomas


-- 

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

Re: [OpenIndiana-discuss] New packaged LibreOffice4

[Thomas Wagner]

Nikola,

could you please be a bit more specific about "save problems"
with the libreoffice from SFE? 
It works for Libreoffice on other installations.

As both issued SFE package versions for libreoffice can save 
odt files on my systems, I'm wondering what is going. 
I test basic functionality like open / save / print preview
before pushing the packages to the public repo.

If you please could provide debug output from libreoffice, e.g.
if you start from a terminal, is something printed on the xterm
at the time the save fails? Or is a core dump written which
could be inspected closer.

Regards,
Thomas



On Sat, Oct 24, 2015 at 11:53:27AM +0200, Nikola M wrote:
>  That package should not be put in public repo because as zou discovered it 
>  doesn't install well regular way, but with issuing exact full package name 
>  it installs, but only for testing before release.
> 
>  Butw when installed it has same problem as OpenOffice in O:, doesn't save 
>  .odt files but LibreO dies and OpenOffice does not die.
> 
>  SFE is separate project from OI / OI hipster but somplementary SFE OI 
>  hipster repo is welcomed and I am happy to have it.
> 

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

Re: [OpenIndiana-discuss] New packaged LibreOffice4

[Thomas Wagner]

Alex,

On Fri, Oct 23, 2015 at 09:04:55PM +0300, Alexander Pyhalov wrote:
>  Or we can just don't incorporate */g++/* packages, so that one can always 
>  install packages from SFE. Having them is still useful for old OI Hipster 
>  installations,
>  which can have pre-renamed versions installed.
>  Something like 
>  
> https://github.com/OpenIndiana/oi-userland/compare/OpenIndiana:oi/hipster...pyhalov:sfe-conflicts
>  

yes, it should be a good solution to just remove the (old) package names
from the consolidation (we already talked in more detail on IRC).

About libreoffice and dependencies, at the moment it is just a little 
bit easier to depend on the SFE g++/icu g++/boost. 
We try porting the spec file to OIH (works), OI151a9 (works), and S11 (S12), 
therefore we want to keep the differences small. We hote to learn quicker,
if problems appear only on one platform or on all and which component 
might be involved. 

Thanks much for the update!

Regards,
Thomas

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