Re: [oi-dev] Missing headerfiles for illumos-build in oi-userland

[Alexander Jung]

Thanx,

from your hints i figured out what the problem was, i forget to change 
perlversion to 5.36, it was still 5.22 and so it failed creation of the 
headerfiles.


Best regards,

Alex

On 5/19/23 20:07, Peter Tribble wrote:

Alexander,

That header is created by the build itself (if you look at the Makefile in
usr/src/lib/libbsm you'll see it's created by running perl against the xml
file that actually contains the definitions). So I would look at the 
nightly

log file to work out why that perl invocation failed.


On Fri, May 19, 2023 at 8:38 AM Alexander Jung  wrote:

Hi,

i can not build illumos-gate anymore in oi-userland, it fails
because of missing headerfiles like adt_event.h.
On

https://github.com/illumos/illumos-gate/tree/master/usr/src/lib/libbsm/common
there are alo not includet but on

https://hipster.openindiana.org/jenkins/job/illumos-gate/ws/components/openindiana/illumos-gate/illumos-gate/usr/src/lib/libbsm/common/
there are still there.

Can someone help me out.


Best regards,
Alex

-- 
*s c i ls e t*

Alexander Jung
Sohlberg 5
77883 Ottenhöfen

*MOBIL:* (0 17 6) 47 16 6195
*E-MAIL:* a.j...@scilset.de <mailto:a.j...@scilset.de>
*INTERNET:* www.scilset.de <http://www.scilset.de/>
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev



--
-Peter Tribble
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/

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

--
*s c i ls e t*
Alexander Jung
Sohlberg 5
77883 Ottenhöfen

*MOBIL:* (0 17 6) 47 16 6195
*E-MAIL:* a.j...@scilset.de <mailto:a.j...@scilset.de>
*INTERNET:* www.scilset.de <http://www.scilset.de/>___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] Missing headerfiles for illumos-build in oi-userland

[Alexander Jung]

Hi,

i can not build illumos-gate anymore in oi-userland, it fails because of 
missing headerfiles like adt_event.h.
On 
https://github.com/illumos/illumos-gate/tree/master/usr/src/lib/libbsm/common 
there are alo not includet but on 
https://hipster.openindiana.org/jenkins/job/illumos-gate/ws/components/openindiana/illumos-gate/illumos-gate/usr/src/lib/libbsm/common/ 
there are still there.


Can someone help me out.


Best regards,
Alex

--
*s c i ls e t*
Alexander Jung
Sohlberg 5
77883 Ottenhöfen

*MOBIL:* (0 17 6) 47 16 6195
*E-MAIL:* a.j...@scilset.de <mailto:a.j...@scilset.de>
*INTERNET:* www.scilset.de <http://www.scilset.de/>___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] webkitgtk2 problem

[Alexander Jung]

Hello,

I have a problem with a program what i compiled and used a long time but 
now it don't work anymore.


The program uses gtk and webkitgtk2 and it don't render any html.

I tested several things and now i tried to build a small sample app with 
gtk and webkit and the app also don't render the htmltext, so i am 
assume that the problem is with webkit.


Now i see that yelp, which uses webktigtk also do not render html text.


Best regards,
Alex

--
*s c i ls e t*
Alexander Jung
Sohlberg 5
77883 Ottenhöfen

*MOBIL:* (0 17 6) 47 16 6195
*E-MAIL:* a.j...@scilset.de <mailto:a.j...@scilset.de>
*INTERNET:* www.scilset.de <http://www.scilset.de/>___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] pkg install

[Alexander Jung]

Hello,

it's me again :)

I have a problem with a program what i compiled and used a long time but 
now it don't work anymore.


The program uses gtk and webkitgtk2 and it don't shows any text, only 
the menu an so on.


I tested several things and now i tried to build a small sample app with 
gtk and webkit and the app also don't render the htmltext, so i am 
assume that the problem is with webkit.


I am not an expert, can someone help me out.


Best regards,
Alex

--
*s c i ls e t*
Alexander Jung
Sohlberg 5
77883 Ottenhöfen

*MOBIL:* (0 17 6) 47 16 6195
*E-MAIL:* a.j...@scilset.de <mailto:a.j...@scilset.de>
*INTERNET:* www.scilset.de <http://www.scilset.de/>___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] pkg install

[Alexander Jung]

Hello,

i want install some pkg's from pkg.openindiana.org/hipster but i get 
this message.


1: Invalid contentpath 
/var/pkg/cache/incoming-2300/update.20221006T06Z.C: CatalogPart failed 
validation: The signature data for the 
'/var/pkg/cache/incoming-2300/update.20221006T06Z.C' catalog file is not 
valid.. (happened 4 times)
2: Invalid contentpath 
/var/pkg/cache/incoming-2300/update.20221006T07Z.C: CatalogPart failed 
validation: The signature data for the 
'/var/pkg/cache/incoming-2300/update.20221006T07Z.C' catalog file is not 
valid.. (happened 4 times)


Is ist possible to fix this?

In the last days i have also a problems with update/installs because it 
is very very slow even with a good internet connection.



Best regards,
Alex

--
*s c i ls e t*
Alexander Jung
Sohlberg 5
77883 Ottenhöfen

*MOBIL:* (0 17 6) 47 16 6195
*E-MAIL:* a.j...@scilset.de <mailto:a.j...@scilset.de>
*INTERNET:* www.scilset.de <http://www.scilset.de/>___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] libstdc++.so version

[Alexander Jung]

Hello,

what version of libstdc++.so should be in current OI under /usr/lib/amd64 ?

Best regards,
Alex

--
*s c i ls e t*
Alexander Jung
Sohlberg 5
77883 Ottenhöfen

*MOBIL:* (0 17 6) 47 16 6195
*E-MAIL:* a.j...@scilset.de <mailto:a.j...@scilset.de>
*INTERNET:* www.scilset.de <http://www.scilset.de/>___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] system falls in maintenance mode

[Alexander Jung]

Hi,

in last time, if i rebuild oi-userland with illumos-gate, illumos-gate 
builds without problems, but if i update the system falls in maintenance 
mode, almost all services fail to start.


Has someone else experienced this problem?

Best regards,
Alex


--
*s c i ls e t*
Alexander Jung
Sohlberg 5
77883 Ottenhöfen

*MOBIL:* (0 17 6) 47 16 6195
*E-MAIL:* a.j...@scilset.de <mailto:a.j...@scilset.de>
*INTERNET:* www.scilset.de <http://www.scilset.de/>___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] Some packages did not build anymore in userland

[Alexander Jung]

Hello,

i build the whole oi-userland from time to time, but in the last time 
there are many packages they did not build anymore. I tried a fresh 
install and fresh sync of oi-userland but it is the same.



For example glib stops with this message ...

Option buildtype is: plain [default: debugoptimized]
Found ninja-1.10.2 at /usr/bin/ninja
/usr/bin/touch 
/code/workspace/oi-userland/components/library/glib/build/i86/.configured
(/usr/bin/env LD_OPTIONS="-M /usr/lib/ld/map.noexstk -M 
/usr/lib/ld/map.noexdata -M /usr/lib/ld/map.pagealign -Bdirect -z 
ignore" LD_EXEC_OPTIONS="-z aslr=disable" 
PKG_CONFIG_PATH="/usr/openssl/1.0/lib/32/pkgconfig:/usr/lib/pkgconfig" 
DFLAGS= /usr/bin/ninja -C 
/code/workspace/oi-userland/components/library/glib/build/i86 -j2 )
ninja: Entering directory 
`/code/workspace/oi-userland/components/library/glib/build/i86'

[395/1081] Compiling C object gio/gresource.p/gresource-tool.c.o
FAILED: gio/gresource.p/gresource-tool.c.o
/usr/gcc/9/bin/gcc -Igio/gresource.p -Igio -I../../glib-2.66.8/gio 
-Igmodule -I../../glib-2.66.8/gmodule -I. -I../../glib-2.66.8 -Iglib 
-I../../glib-2.66.8/glib -Igobject -I../../glib-2.66.8/gobject 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch 
-std=gnu99 -O3 -D_GNU_SOURCE -fno-strict-aliasing 
-DG_DISABLE_CAST_CHECKS -Wduplicated-branches -Wimplicit-fallthrough 
-Wmisleading-indentation -Wstrict-prototypes -Wunused 
-Wno-unused-parameter -Wno-bad-function-cast -Wno-cast-function-type 
-Wno-pedantic -Wno-format-zero-length 
-Werror=declaration-after-statement -Werror=format=2 
-Werror=implicit-function-declaration -Werror=init-self 
-Werror=missing-include-dirs -Werror=missing-prototypes 
-Werror=pointer-arith -m32 -O3 -Wno-error=format-nonliteral 
-D_XOPEN_SOURCE=600 -D__EXTENSIONS__=1 -D_XPG6 -MD -MQ 
gio/gresource.p/gresource-tool.c.o -MF 
gio/gresource.p/gresource-tool.c.o.d -o 
gio/gresource.p/gresource-tool.c.o -c 
../../glib-2.66.8/gio/gresource-tool.c

In file included from ../../glib-2.66.8/gio/gresource-tool.c:32:
/usr/include/libelf.h:43:2: error: #error "large files are not supported 
by libelf"

   43 | #error "large files are not supported by libelf"
  |  ^
[396/1081] Compiling C object gio/gio-querymodules.p/giomodule-priv.c.o
ninja: build stopped: subcommand failed.

Or another problem is that GCC-7 did not build the gobjc stuff.


Do i have messed something up?


Greetings an always thanx for that nice OS,
Alex



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

Re: [oi-dev] Status of OpenIndiana Wiki (Atlassian Confluence)

[Alexander Pyhalov]

Hi.
Separate issue - wanted to work on docs conversion (ipf section), but found 
that mdl is broken.
For now it seems I fixed it. Will try to work on this section later if I have a 
bit of free time.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: James Madgwick 
Отправлено: 13 сентября 2021 г. 0:43
Кому: oi-dev@openindiana.org
Тема: Re: [oi-dev] Status of OpenIndiana Wiki (Atlassian Confluence)

On Sat, 11 Sep 2021 18:59:04 -0300
Till Wegmueller  wrote:

> In my opinion I would put the HTML under wiki.openindiana.org or
> another space.
>
> Docs should only be the migrated docs.
>

To give an idea of what the Confluence HTML exported wiki looks like,
I've created this: https://oi-wiki-test.madgwick.xyz/

The HTML pages don't look great, but are usable as an archived version.
Happy to put the zip of HTML files and images (125MB - too big for gist)
somewhere - new OI repo?

James


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

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

Re: [oi-dev] I'm taking a break

[Alexander Pyhalov via oi-dev]

Aurelien and Michal.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Andreas Wacknitz 
Отправлено: 8 сентября 2020 г. 20:35
Кому: Alexander Pyhalov via oi-dev
Тема: Re: [oi-dev] I'm taking a break

Am 08.09.20 um 17:36 schrieb Alexander Pyhalov via oi-dev:
> Hi, guys.
>
> I wasn't sure if this should be a public message, but when I understood that 
> CC list reached > 5 persons, decided to send it here.
>
> Briefly, I'm taking a break.
> This doesn't mean that I'll not be able to answer your questions or that I 
> will not commit anything to OI repos - I don't know. But for now I'm changing 
> my job and likely will relocate to Moscow in near future. Given that's new 
> position is a new area for me, I'll just have  no time for such 
> time-consuming hobby as OI.
>
> I'm still excited about OI and illumos. It was a wonderful experience, but 
> for now our ways parted.
> Good luck. You can always reach me via my gmail account.
>
> Best regards,
> Alexander Pyhalov,
> (still) system administrator of Southern Federal University IT department
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
Hi Alexander,

sad to hear that, but understandable. Good luck for the next time,
especially for your new job.

Who is left with access to the build system? I "only" have commit rights
but nothing else...

Regards,
Andreas

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

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

[oi-dev] I'm taking a break

[Alexander Pyhalov via oi-dev]

Hi, guys.

I wasn't sure if this should be a public message, but when I understood that CC 
list reached > 5 persons, decided to send it here.

Briefly, I'm taking a break.
This doesn't mean that I'll not be able to answer your questions or that I will 
not commit anything to OI repos - I don't know. But for now I'm changing my job 
and likely will relocate to Moscow in near future. Given that's new position is 
a new area for me, I'll just have  no time for such time-consuming hobby as OI. 

I'm still excited about OI and illumos. It was a wonderful experience, but for 
now our ways parted.
Good luck. You can always reach me via my gmail account.

Best regards, 
Alexander Pyhalov, 
(still) system administrator of Southern Federal University IT department

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

Re: [oi-dev] couchdb-21 seems to need be rebuild, removed or upgraded

[Alexander Pyhalov via oi-dev]

Hi.
The issue is with netaddr-27 module, have to check why it depends on ipython.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Andreas Wacknitz 
Отправлено: 12 августа 2020 г. 20:45
Кому: OpenIndiana Developer mailing list
Тема: [oi-dev] couchdb-21 seems to need be rebuild, removed or upgraded

Hi,

my build systems are stuck in the past because there seems to be a
problem with couchdb-21, eg. on my desktop machine:
╰─➤  pfexec pkg install -nv pkg://openindiana.org/database/couchdb-21 1 ↵
Creating Plan (Running solver): -
pkg install: No matching version of database/couchdb-21 can be installed:
   Reject:
pkg://openindiana.org/database/couchdb-21@2.1.1-2020.0.1.1:20200601T200510Z
   Reason:  No version matching 'require' dependency
library/python/netaddr-27 can be installed
 
 Reject:
pkg://openindiana.org/library/python/netaddr-27@0.7.10-2020.0.1.0:20200330T154852Z
 Reason:  All acceptable versions of 'require' dependency on
library/python/ipython-27@5.0.0-2020.0.1.2 are obsolete
 

Am I right?

Regards,
Andreas

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

[oi-dev] Gobject-introspection works only for 64-bit

[Alexander Pyhalov via oi-dev]

Hi.
We have an interesting issue. Our Pythons 3 are 64-bit only. And 
gobject-introspection requires Python 3.
So, anything using 32-bit python 2.7 (the default python2.7 interpreter) can't 
longer use gobject-introspection and gobject module.
Affected components include:

some ansible modules - should switch ansible to Python 3
dbus-python - likely just have to drop Python 2.7 module (just 32-bit version 
or both?) 
gnomedesktop.py salt module - not really important, but likely should switch 
salt to py3
parts of ipython2.7 - should deliver 64-bit only ipython2.7
ldtp - should drop 2.7 version?
pygobject-3 - should drop 2.7 version (just 32-bit version or both?) 
pygobject  - should drop 2.7 version (just 32-bit version or both?) 
parts of twisted 
terminator - should update to py3 version

So far I don't think that dropping python 2.7 completely is an option, as there 
are still applications, requiring it at least for build.
We can consider delivering only 64-bit python 2.7 version, but this will break 
a lot of consumers, and I don't think that this worth the effort.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ


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

Re: [oi-dev] One package still uses python3.4

[Alexander Pyhalov via oi-dev]

Hi.
The only method I see is to drop 32-bit gobject-introspection.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Andreas Wacknitz 
Отправлено: 18 июля 2020 г. 14:44
Кому: OpenIndiana Developer mailing list
Тема: [oi-dev] One package still uses python3.4

Hi,

g-ir-scanner, g-ir-annotation-tool, and g-ir-doc-tool from the
gobject-introspection package still use #!/usr/bin/python3.4 as their
interpreters.
I have tried to set the PYTHON_VERSION for gobject-introspection from
3.4 to 3.5 but then configure doesn't find its Python.h file (located at
usr/include/python3.5m/).
Does anybody know how to fix this?

Regards,
Andreas

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

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

Re: [oi-dev] Integration of PR #5893 broke several packages

[Alexander Pyhalov via oi-dev]

Hi.
At least for components/python/decorator, you removed TPNO from Makefile, but 
not from manifests. Now gmake print-package-names can't parse them.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Andreas Wacknitz 
Отправлено: 14 июля 2020 г. 0:10
Кому: OpenIndiana Developer mailing list
Тема: [oi-dev] Integration of PR #5893 broke several packages

Hi,

jenkins build failed after integration of PR #5893 because some packages
have problems like this
...
NEW PACKAGE CONTENTS ARE LOCALLY VALIDATED AND READY TO GO
/usr/bin/touch
/oibuild/oi-userland/components/python/jsonrpclib/build/.pre-published-i386
Generating component metadata...
Traceback (most recent call last):
   File "/oibuild/oi-userland/tools/bass-o-matic", line 262, in 
 main()
   File "/oibuild/oi-userland/tools/bass-o-matic", line 207, in main
 BassComponent(FindComponentPaths(path=workspace, debug=debug,
subdir=os.path.join(subdir, component_path))[0])
   File "/oibuild/oi-userland/tools/bass/component.py", line 68, in __init__
 raise ValueError('Empty list of supplied FMRIs\npath = ' + self.path)
ValueError: Empty list of supplied FMRIs
path = /oibuild/oi-userland/components/python/jsonrpclib
gmake: *** [/oibuild/oi-userland/make-rules/depend.mk:24:
update-metadata] Error 1

Sorry for this, I only checked the changes until the pre-publish step
and didn't expect the last step to fail.
I don't know what the reason for the empty list of FMRIs is and how to
fix these issues.
Any ideas?

Regards,
Andreas

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

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

Re: [oi-dev] Jenkins build of squeak5 failed

[Alexander Pyhalov via oi-dev]

Hi.

Likely,
opensmalltalk-vm-sun-v5.0.8/platforms/unix/config/Makefile.install needs fixing:

install-doc : squeak.1
$(MKINSTALLDIRS) $(ROOT)$(docdir)
@list='$(DOCFILES)'; for f in $$list; do \
  echo $(INSTALL_DATA) $(topdir)/platforms/unix/doc/$$f 
$(ROOT)$(docdir); \
  $(INSTALL_DATA) $(topdir)/platforms/unix/doc/$$f $(ROOT)$(docdir); \
done
gzip -f9 $(ROOT)$(docdir)/*
$(MKINSTALLDIRS) $(ROOT)$(mandir)/man1
$(INSTALL_DATA) squeak.1 $(ROOT)$(mandir)/man1
rm -f $(ROOT)$(mandir)/man1/inisqueak.1 
$(ROOT)$(mandir)/man1/inisqueak.1.gz
if test -f $(ROOT)$(mandir)/man1/squeak.1; then $(LN) 
$(ROOT)$(mandir)/man1/squeak.1 $(ROOT)$(mandir)/man1/inisqueak.1; fi
if test -f $(ROOT)$(mandir)/man1/squeak.1.gz; then $(LN) 
$(ROOT)$(mandir)/man1/squeak.1.gz $(ROOT)$(mandir)/man1/inisqueak.1.gz; fi

it creates build/prototype/i386/usr/doc/squeak/COPYING.gz.gz if file 
build/prototype/i386/usr/doc/squeak/COPYING.gz already exists.

Cleaned build area.


С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Andreas Wacknitz 
Отправлено: 8 июля 2020 г. 20:01
Кому: OpenIndiana Developer mailing list
Тема: [oi-dev] Jenkins build of squeak5 failed

Hi,

squeak5 failed to build because it needs a clean environment. Can
somebody with access to the build machine please clean its folder?

Regards
Andreas

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

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

Re: [oi-dev] Jenkins fails

[Alexander Pyhalov via oi-dev]

Hi. Cleared old BEs.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Andreas Wacknitz 
Отправлено: 7 июля 2020 г. 11:54
Кому: OpenIndiana Developer mailing list
Тема: [oi-dev] Jenkins fails

Hi all,

illumos-gate build failed tonight as oi-userland build failed this
morning. I guess the build machine's disk is full.
Can some admin fix this, please?

Regards,
Andreas

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

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

Re: [oi-dev] pkglint fails during publish

[Alexander Pyhalov via oi-dev]

Likely by default it passed -Es to the python interpreter, so doesn't load 
modules from non-standart path.



С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Gary Mills 
Отправлено: 9 мая 2020 г. 1:31
Кому: OpenIndiana Developer mailing list 
Копия: Alexander Pyhalov 
Тема: Re: [oi-dev] pkglint fails during publish

On Fri, May 08, 2020 at 07:49:21AM -0500, Gary Mills wrote:
> On Fri, May 08, 2020 at 07:01:36AM +0000, Alexander Pyhalov wrote:
> > Sorry, I meant
> > https://github.com/OpenIndiana/oi-userland/commit/fb10babbcfd65ff74cf439bc77a2186fd79ee2a7
>
> I have some of those changes in the 2019 source clone, but not all of
> them.

I made another change shown in your PR: I replaced userland.py in
tools/python/pkglint with the one in my 2020 source clone.  With that,
I got the same error during a publish, twice:

pkglint: Error parsing config value for pkglint.ext.content: No module 
named 'pkglint'

The file tools/pkglintrc contains:

pkglint.ext.content = pkglint.userland

suggesting that the pkglint command could not find the pkglint module.
I'm wondering if PYTHONPATH is set correctly in the environment.

In any case, I made the changes in make-rules, which consists only of
altering the definition of PKGLINT by adding /usr/bin/python3.5 in
front of /usr/bin/pkglint .  With those changes, I got a successful
publish.  I did not expect that result.

I don't understand why it worked.  /usr/bin/pkglint is already a
python3.5 script.  Can you explain it?  Can anybody explain it?


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

[oi-dev] libzmq update

[Alexander Pyhalov via oi-dev]

Hi.
We have to update libzeromq and pyzmq to try updating salt.
The issue is that 
a) new libzmq 4.3.x is not abi-compatible to currently shipped 3.2.5.
b) our current packaging allows us to deliver second (abi-incompatible copy), 
but is overcomplicated.
So, the question is if we want to ship new version in the same over-complicated 
way or just bump it and rebuild several consumers which we have in OI (czmq and 
pyzmq)?  

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ


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

Re: [oi-dev] pkglint fails during publish

[Alexander Pyhalov]

Sorry, I meant
https://github.com/OpenIndiana/oi-userland/commit/fb10babbcfd65ff74cf439bc77a2186fd79ee2a7

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Alexander Pyhalov 
Отправлено: 8 мая 2020 г. 10:00
Кому: oi-dev@openindiana.org
Копия: Carsten Grzemba
Тема: RE: [oi-dev] pkglint fails during publish

Hi.
Do you have 
https://github.com/OpenIndiana/oi-userland/commiti/fb10babbcfd65ff74cf439bc77a2186fd79ee2a7#diff-4a931512ce65bdc9ca6808adf92d8783
 ?

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Carsten Grzemba via oi-dev 
Отправлено: 8 мая 2020 г. 8:34
Кому: OpenIndiana Developer mailing list; oi-dev@openindiana.org
Копия: Carsten Grzemba
Тема: Re: [oi-dev] pkglint fails during publish



Am 08.05.20 04:06 schrieb Gary Mills :
When I'm attempting a publish, I get this error:

/usr/bin/pkglint  \
-f
 /dpool/export/home/mills/Downloads/code/oi-userland-jan/tools/pkglintrc
 
/dpool/export/home/mills/Downloads/code/oi-userland/components/x11/xorg-server-1.20.8/build/manifest-i386-trusted-xorg.depend.res
...
 
/dpool/export/home/mills/Downloads/code/oi-userland/components/x11/xorg-server-1.20.8/build/manifest-i386-xdmx.depend.res

Lint engine setup...
pkglint: Error parsing config value for pkglint.ext.content: No module 
named 'pkglint'
Error: Error parsing config value for pkglint.ext.content: No module named 
'pkglint'
gmake: *** 
[/dpool/export/home/mills/Downloads/code/oi-userland-jan/make-rules/ips.mk:463: 
/dpool/export/home/mills/Downloads/code/oi-userland/components/x11/xorg-server-1.20.8/build/.linted-i386]
 Error 2

I'm building part of a source clone from January 2019, but the BE is
from March 2020.  I'm assuming the error is a result of the change
from python2.7 to python3.5 that happened during that interval.  The
file /usr/bin/pkglint is a python3.5 script.  The statement:

pkglint.ext.content = pkglint.userland

occurs in the tools/pkglintrc file.  This seems to be the source
of the error.

Am I missing a package, or has something else gone wrong?
So check, that userland-tools start pkglint with Python3



--
-Gary Mills- -refurb- -Winnipeg, Manitoba, Canada-

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

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

Re: [oi-dev] pkglint fails during publish

[Alexander Pyhalov via oi-dev]

Hi.
Do you have 
https://github.com/OpenIndiana/oi-userland/commiti/fb10babbcfd65ff74cf439bc77a2186fd79ee2a7#diff-4a931512ce65bdc9ca6808adf92d8783
 ?

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Carsten Grzemba via oi-dev 
Отправлено: 8 мая 2020 г. 8:34
Кому: OpenIndiana Developer mailing list; oi-dev@openindiana.org
Копия: Carsten Grzemba
Тема: Re: [oi-dev] pkglint fails during publish



Am 08.05.20 04:06 schrieb Gary Mills :
When I'm attempting a publish, I get this error:

/usr/bin/pkglint  \
-f
 /dpool/export/home/mills/Downloads/code/oi-userland-jan/tools/pkglintrc
 
/dpool/export/home/mills/Downloads/code/oi-userland/components/x11/xorg-server-1.20.8/build/manifest-i386-trusted-xorg.depend.res
...
 
/dpool/export/home/mills/Downloads/code/oi-userland/components/x11/xorg-server-1.20.8/build/manifest-i386-xdmx.depend.res

Lint engine setup...
pkglint: Error parsing config value for pkglint.ext.content: No module 
named 'pkglint'
Error: Error parsing config value for pkglint.ext.content: No module named 
'pkglint'
gmake: *** 
[/dpool/export/home/mills/Downloads/code/oi-userland-jan/make-rules/ips.mk:463: 
/dpool/export/home/mills/Downloads/code/oi-userland/components/x11/xorg-server-1.20.8/build/.linted-i386]
 Error 2

I'm building part of a source clone from January 2019, but the BE is
from March 2020.  I'm assuming the error is a result of the change
from python2.7 to python3.5 that happened during that interval.  The
file /usr/bin/pkglint is a python3.5 script.  The statement:

pkglint.ext.content = pkglint.userland

occurs in the tools/pkglintrc file.  This seems to be the source
of the error.

Am I missing a package, or has something else gone wrong?
So check, that userland-tools start pkglint with Python3



--
-Gary Mills- -refurb- -Winnipeg, Manitoba, Canada-

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

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

Re: [oi-dev] Build server repeatedly failed on bhyve-fw

[Alexander Pyhalov via oi-dev]

It failed with

gmake[4]: Leaving directory 
'/jenkins/jobs/oi-userland/workspace/components/openindiana/bhyve-fw/build/DEBUG/BaseTools/Tests'
gmake[3]: Leaving directory 
'/jenkins/jobs/oi-userland/workspace/components/openindiana/bhyve-fw/build/DEBUG/BaseTools'
BaseTools not found in your tree, and EDK_TOOLS_PATH is not set.
Please check that WORKSPACE is not set incorrectly in your
shell, or point EDK_TOOLS_PATH at the directory that contains
the EDK2 BuildEnv script.
Restoring files...
gmake[2]: *** [/jenkins/jobs/oi-userland/workspace/make-rules/justmake.mk:62: 
/jenkins/jobs/oi-userland/workspace/components/openindiana/bhyve-fw/build/DEBUG/.built]
 Error 1

It publishes when run manually.

Can it be due to WORKSPACE jenkins variable ?

Strange,
С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Andreas Wacknitz 
Отправлено: 6 мая 2020 г. 23:20
Кому: OpenIndiana Developer mailing list
Тема: [oi-dev] Build server repeatedly failed on bhyve-fw

Hi all,

for an unknown reason the jenkins build repeatedly failed on the new
bhyve-fw package. This is probably because of a local problem pn the
server as the package gets successfully published on other systems. Is
there anybody left with access rights to fix this?

Regards
Andreas


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

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

Re: [oi-dev] OpenIndiana Hipster 2020.04

[Alexander Pyhalov via oi-dev]

Just install desktop/office/libreoffice

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ




От: Gerard Arthus 
Отправлено: 6 мая 2020 г. 4:26
Кому: OpenIndiana Developer mailing list
Тема: Re: [oi-dev] OpenIndiana Hipster 2020.04

How to instal the new version of libreoffice on the latest Hipster?

Thank you.

Gerry

Gerard Arthus
409 Lowell Avenue East
Mishawaka, Indiana
United States
46545
Cell - 574-302-7731
Home - 574-520-1337

Instructor ITT-Tech - Mathematics, Electrical Engineering, and Computer 
Engineering.

garthus...@gmail.com<mailto:garthus...@gmail.com>
Notary The State of Indiana #685426
http://www.OpenEducation.org
http://openeducation.org/moodle/  (For Course Portal) Log In as Guest
http://www.linkedin.com/profile/edit?trk=tab_pro
http://www.facebook.com/gerard.arthus
https://archive.org/details/arthusgerardphilosophicalwritings (Philosophical 
Discussions)
https://archive.org/details/arthusgerardpoems (Poems)
https://archive.org/details/arthusgerardzoe?sort=titleSorter (Zoe Book)
https://archive.org/details/@garthus1=collections (Gerard Arthus 
Collections Page)
https://archive.org/details/arthusgerardhack<https://archive.org/search.php?query=hacking%20the%20world%20garthus>
 (Hacking The World)
https://archive.org/details/arthusgerardmedical=about
(Medical Records)
https://archive.org/details/arthusgerardrec=collection
(Musical Recordings)

https://archive.org/details/arthusgerardpackagingandinstructionmanuals 
(Packaging Collection)
https://archive.org/details/@garthus1=uploads  (All Items Uploaded to Date)
https://archive.org/details/What_Have_We_Wrought_ (Selected Poem)
https://archive.org/details/A_World_Where_We_Consume_Our_Hearts_ (Selected Poem)
https://archive.org/details/Here_There_Is_No_Lesson_To_Be_Learned_ (Selected 
Poem)
https://archive.org/details/Deception_And_The_Self_Created_Terrorist_Threat_American_Complicity_In_World_W
 (Selected Poem)
https://archive.org/details/Solitary_Horsemen_Reflections_On_Life_In_Cyberspace 
(Selected Poem)


On Tue, May 5, 2020 at 6:13 AM Alexander Pyhalov 
mailto:a...@sfedu.ru>> wrote:
OpenIndiana Hipster 2020.04 snapshot is ready.

Images:

http://dlc.openindiana.org/isos/hipster/20200504/OI-hipster-gui-20200504.iso
http://dlc.openindiana.org/isos/hipster/20200504/OI-hipster-gui-20200504.usb

http://dlc.openindiana.org/isos/hipster/20200504/OI-hipster-text-20200504.iso
http://dlc.openindiana.org/isos/hipster/20200504/OI-hipster-text-20200504.usb

http://dlc.openindiana.org/isos/hipster/20200504/OI-hipster-minimal-20200504.iso
http://dlc.openindiana.org/isos/hipster/20200504/OI-hipster-minimal-20200504.usb


SHA 256 checksums are available at ${link}.sha256sum
Signed SHA 256 checksums are available at ${link}.sha256sum.asc
The OpenIndiana Release Engineering key has key id 0x3a021afadbe31887
Note - I've had to update key today,  pks key servers still refer to outdated 
key. ).

Release notes: http://docs.openindiana.org/release-notes/2020.04-release-notes/

Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department
___
oi-dev mailing list
oi-dev@openindiana.org<mailto:oi-dev@openindiana.org>
https://openindiana.org/mailman/listinfo/oi-dev

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

[oi-dev] OpenIndiana Hipster 2020.04

[Alexander Pyhalov]

OpenIndiana Hipster 2020.04 snapshot is ready.

Images:

http://dlc.openindiana.org/isos/hipster/20200504/OI-hipster-gui-20200504.iso
http://dlc.openindiana.org/isos/hipster/20200504/OI-hipster-gui-20200504.usb

http://dlc.openindiana.org/isos/hipster/20200504/OI-hipster-text-20200504.iso
http://dlc.openindiana.org/isos/hipster/20200504/OI-hipster-text-20200504.usb

http://dlc.openindiana.org/isos/hipster/20200504/OI-hipster-minimal-20200504.iso
http://dlc.openindiana.org/isos/hipster/20200504/OI-hipster-minimal-20200504.usb


SHA 256 checksums are available at ${link}.sha256sum
Signed SHA 256 checksums are available at ${link}.sha256sum.asc
The OpenIndiana Release Engineering key has key id 0x3a021afadbe31887
Note - I've had to update key today,  pks key servers still refer to outdated 
key. ).

Release notes: http://docs.openindiana.org/release-notes/2020.04-release-notes/

Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Incorporation version constraints

[Alexander Pyhalov via oi-dev]

Hi.
I see
depend facet.version-lock.system/library/g++-7-runtime=true 
fmri=system/library/g++-7-runtime@7.5.0-2020.0.1.2 type=incorporate
on build server.
Does pkg update fail to fetch latest userland-incorporation for you?
What if you explicitly say
pkg update -vv 
pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2020.0.1.12901:20200503T163621Z
 ?

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Till Wegmüller 
Отправлено: 4 мая 2020 г. 0:24
Кому: OpenIndiana Developer mailing list
Тема: [oi-dev] Incorporation version constraints

Good evening folks

I was trying to install a current revision of library/gmp with "pkg
install pkg:/library/gmp@6.1.2-2020.0.1.2" and got the following error

Reason:  This version is excluded by installed incorporation
consolidation/userland/userland-incorporation@0.5.11-2020.0.0.12833
  Reject:
pkg://openindiana.org/system/library/gcc-7-runtime@7.5.0-2020.0.1.1:20200330T115834Z
  Reason:  No version matching 'require' dependency
system/library@0.5.11-2020.0.1.19548 can be installed
  Reason:  This version is excluded by installed incorporation
consolidation/userland/userland-incorporation@0.5.11-2020.0.0.12833
  Reject:
pkg://openindiana.org/system/library/gcc-7-runtime@7.5.0-2020.0.1.2:20200414T194235Z
  Reason:  No version matching 'require' dependency
system/library@0.5.11-2020.0.1.19563 can be installed
  Reason:  This version is excluded by installed incorporation
consolidation/userland/userland-incorporation@0.5.11-2020.0.0.12833


The Interesting part is
Reason:  No version matching 'require' dependency
system/library/g++-7-runtime@7.5.0-2020.0.1.1 can be installed

and indeed pkg contents -m consolidation/userland/userland-incorporation
| grep 'g++' shows:

depend facet.version-lock.system/library/g++-7-runtime=true
fmri=system/library/g++-7-runtime@7.5.0-2020.0.0.1 type=incorporate

notice the 0.1 instead 1.1 at the end.

Is this an artefact because we are preparing for the next snapshot or a
bug in the incorporation? If the later could somebody trigger the
buildserver to bump the incorporation properly?

Thanks and greetings
Till

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

[oi-dev] ntfsprogs update check

[Alexander Pyhalov via oi-dev]

Hi.

Can somebody test ntfsprogs update 
(https://github.com/OpenIndiana/oi-userland/pull/5662 ) ? At least, that ntfs 
partitions are still readable? 
I've found that all my usb sticks are fat-formatted, so I can't easily test it.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ


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

Re: [oi-dev] oi-docs builds

[Alexander Pyhalov via oi-dev]

link_validator step is not compulsory. For example, there are links to 
hg.openindiana.org. It has expired certificate, but honestly, I don't have an 
idea where it's hosted to fix the issue.

Adam, do you by chance have access to this host?

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Carsten Grzemba 
Отправлено: 3 апреля 2020 г. 16:29
Кому: OpenIndiana Developer mailing list; _oi-dev
Копия: Alexander Pyhalov
Тема: Re: [oi-dev] oi-docs builds



Am 03.04.20 13:48 schrieb Alexander Pyhalov via oi-dev :
Hi.
It seems there was some issue with Travis CI oi-docs build, at least last PRs 
were not checked.
I've reconfigured Travis CI integration, results can be found at 
https://travis-ci.com/github/OpenIndiana

It fails with the same error like 2 month ago, where the problem seems to be 
link_validator.py with non working links:

The job exceeded the maximum time limit for jobs, and has been terminated.
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] oi-docs builds

[Alexander Pyhalov via oi-dev]

Hi.
It seems there was some issue with Travis CI oi-docs build, at least last PRs 
were not checked.
I've reconfigured Travis CI integration, results can be found at 
https://travis-ci.com/github/OpenIndiana


С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ


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

Re: [oi-dev] Userland repository rebuild issue

[Alexander Pyhalov via oi-dev]

Well, actually it shouldn't be possible to update to affected package versions, 
as they depend on non-published libdrm.
Anyway, issue has been fixed.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Aurélien Larcher 
Отправлено: 31 марта 2020 г. 16:51
Кому: OpenIndiana Developer mailing list; Discussion list for OpenIndiana
Тема: [oi-dev] Userland repository rebuild issue

Hi,
it seems that libdrm on the build server was upgraded by mistake to my older 
gcc-next repository which contained 2.4.99 (leftover files that I should have 
cleaned by passing options to rsync ).

We need to rebuild some X11 components so you should avoid upgrading if you 
have an Intel adapter.

Sorry about this issue...
Kind regards,

Aurélien

--
---
Praise the Caffeine embeddings
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Binary-only packages

[Alexander Pyhalov via oi-dev]

They are installed on build server currently.
Some of them are binary-only, like cpp, for which we still haven't imported 
replacement.
Most of them are just old crap, which should be marked obsolet.
But some of them are probably useful and open sourced (like different input 
methods, fonts and utils), so can be imported to oi-userland.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Till Wegmüller 
Отправлено: 29 марта 2020 г. 17:18
Кому: oi-dev@openindiana.org
Тема: Re: [oi-dev] Binary-only packages

Hi Alexander

On 29.03.20 16:12, Alexander Pyhalov via oi-dev wrote:
> documentation/gnome/gnome-user-docs   2.32.0-2018.0.0.0  
> i--

Apart from this one all packages are from 2013.

Are they even installable? My guess is the incorporations would block
them from being installed at all.

Looks like a leftover from an older build system.

Greetings
Till

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

[oi-dev] Binary-only packages

[Alexander Pyhalov via oi-dev]

Hi.

While preparing hipster.openindiana.org to gcc-7 full rebuild I've found the 
following packages, which were not provided by Aurelien's repo (these are 
mostly binary-only packages or packages which should be marked obsolete). Some 
of them likely could be imported to oi-userland (like fakeroot).

NAME (PUBLISHER)  VERSIONIFO
benchmark/iozone  3.323-2013.0.0.0   i--
cde/calendar-manager-server   0.5.11-2013.0.0.0  i--
cde/cde-runtime   0.5.11-2013.0.0.0  i--
cde/cde-utilities 0.5.11-2013.0.0.0  i--
cde/help-viewer   0.5.11-2013.0.0.0  i--
consolidation/cde/cde-incorporation   0.5.11-2013.0.0.0  i--
consolidation/dbtg/dbtg-incorporation 0.5.11-2013.0.0.0  i--
consolidation/jdmk/jdmk-incorporation 0.5.11-2013.0.0.0  i--
consolidation/man/man-incorporation   0.5.11-2013.0.0.0  i--
developer/debug/mdb/module/module-ce  0.5.11-2013.0.0.0  i--
developer/fakeroot1.11-2013.0.0.0i--
developer/macro/cpp   0.5.11-2013.0.0.0  i--
documentation/gnome/gnome-user-docs   2.32.0-2018.0.0.0  i--
driver/network/ce 0.5.11-2013.0.0.0  i--
editor/jedit  4.3-2013.0.0.0 i--
library/desktop/gtk1  1.2.10-2013.0.0.0  i--
library/glib1 1.2.10-2013.0.0.0  i--
library/java/activation   1.1.1-2013.0.0.0   i--
library/java/commons-collections  3.2.1-2013.0.0.0   
i-- 

library/java/javadb   10.6.2.1-2013.0.0.0
i-- 

library/java/javamail 1.4.1-2013.0.0.0   
i-- 

library/java/jdmk-runtime 0.5.11-2013.0.0.0  
i-- 

library/java/jrexx1.1.1-2013.0.0.0   
i-- 

library/java/qdox 1.9-2013.0.0.0 
i-- 

library/java/saaj 1.3.2-2013.0.0.0   
i-- 

library/java/trove2.0.4-2013.0.0.0   
i-- 

library/libosip2  3.3.0-2013.0.0.0   
i-- 

library/medialib  0.5.11-2013.0.0.0  
i-- 

library/motif 0.5.11-2013.0.0.0  
i-- 

library/motif/libdpstkxm  0.5.11-2013.0.0.0  i--
library/tooltalk  0.5.11-2013.0.0.0  i--
media/mtx 1.3.11-2013.0.0.0  i--
service/network/load-balancer/pen 0.18.0-2013.0.0.0  i--
system/font/truetype/arabeyes 0.5.11-2013.0.0.0  i--
system/font/truetype/bpg-georgian 0.5.11-2013.0.0.0  i--
system/font/truetype/hanyang-ko   0.5.11-2013.0.0.0  i--
system/font/truetype/hanyang-ko-core  0.5.11-2013.0.0.0  i--

Re: [oi-dev] perl module update questions

[Alexander Pyhalov via oi-dev]

1) REQUIRED_PACKAGES is a list of packages which are used to resolve 
dependencies.
This doesn't mean that packages, built from such component, depends on all 
specified REQUIRED_PACKAGES (or only on them).
2) depend actions in manifest (besides depens fmri=__TBD) are not resolved, but 
used as is.
Likely you have to specify exact perl version in versioned manifest (better - 
via FMRI=__TBD style dependencies).

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Tim Mooney 
Отправлено: 16 марта 2020 г. 22:03
Кому: oi-dev@openindiana.org
Тема: Re: [oi-dev] perl module update questions

In regard to: Re: [oi-dev] perl module update questions, Alexander Pyhalov...:

> Have you run gmake REQUIRED_PACKAGES?

For all other types of software builds, I always build that target,
but for perl modules I've been trying to avoid REQUIRED_PACKAGES,
because it generally adds this to the end of the Makefile:

# Auto-generated dependencies
REQUIRED_PACKAGES += runtime/perl-522
REQUIRED_PACKAGES += runtime/perl-524
REQUIRED_PACKAGES += runtime/perl-530

I've been trying to avoid having a module built for e.g. perl 5.30
also depend on runtime/perl-524 and runtime/perl-522.

That's why I've been manually adding this to the .p5m:

# make this module depend upon only the perl version it was built for.
depend fmri=runtime/perl-$(PLV) type=require

Shouldn't that accomplish the same thing, but more precisely?

> On gmake publish only packages in REQUIRED_PACKAGES variable are
> examined as dependencies.  gmake REQUIRED_PACKAGES tries to populate
> this list , running resolve against all currently installed packages.

Are you saying that pkgdepend resolve does *not* look at any specific
'depend' lines in the manifest?

Tim

> 
> От: Tim Mooney 
> Отправлено: 16 марта 2020 г. 21:17
> Кому: oi-dev@openindiana.org
> Тема: Re: [oi-dev] perl module update questions
>
> In regard to: perl module update questions, Tim Mooney said (at 12:38pm on...:
>
>> All-
>>
>> I'm working my way through rebuilding hipster's perl modules for perl
>> 5.30.1 and I have a couple questions.
>
> I've run into a couple of perl modules for which the publish targets
> "pkgdepend resolve" phase outputs dependency errors like:
>
> /export/home/mooney/oi-userland/components/perl/DBI/build/manifest-i386-DBI-524.depend
>  has unresolved dependency '
> depend type=require fmri=__TBD pkg.debug.depend.file=perl \
> pkg.debug.depend.path=usr/perl5/5.24/bin \
> pkg.debug.depend.reason=usr/perl5/5.24/bin/dbiprof \
> pkg.debug.depend.type=script'.
>
> Or
>
> /export/home/mooney/oi-userland/components/perl/Module-Build/build/manifest-i386-Module-Build-530.depend
>  has unresolved dependency '
> depend type=require fmri=__TBD pkg.debug.depend.file=perl \
> pkg.debug.depend.path=usr/perl5/5.30/bin \
> pkg.debug.depend.reason=usr/perl5/5.30/bin/config_data \
> pkg.debug.depend.type=script'.
>
>
> What, specifically, is pkgdepend saying is missing?  The path (directory)
> usr/perl5/5.30/bin ?  Or is it saying that 'perl' is missing in
> usr/perl5/5.30/bin ?
>
> I can make pkgdepend ignore the error by doing:
>
>  set 
> pkg.depend.bypass-generate .* >
>
> but if there's a way to fix the dependency issue, rather than ignore it,
> I would prefer to take that approach.
>
> At first I thought it was because the perl module was missing a dependency
> on the perl runtime that it's built for.  However, including
>
>depend fmri=runtime/perl-$(PLV) type=require
>
> in the .p5m, although probably a good idea anyway, doesn't resolve the
> issue.
>
> Then I thought it was because perl 5.22 and 5.24 don't actually have
> a 'dir' action for their bin directory, so maybe it was pkgdepend
> complaining that the runtime/perl-$(PLV) isn't actually claiming
> ownership of path=usr/perl/$(PERLVER)/bin .  However, adding dir
> actions like
>
> dir  path=usr/perl5/5.30
> dir  path=usr/perl5/5.30/bin
>
> for the runtime/perl-530 didn't make any difference for the modules
> built against perl 5.30.
>
> With those two tries not solving the dependency issue, I'm not sure what
> the right fix is.  Any suggestions?
>
> Thanks,
>
> Tim
> --
> Tim Mooney tim.moo...@ndsu.edu
> Enterprise Computing & Infrastructure /
> Division of Information Technology/701-231-1076 (Voice)
> North Dakota State University, Fargo, ND 58105-5164
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.or

Re: [oi-dev] hplip update testing

[Alexander Pyhalov via oi-dev]

Hi. I've just committed PR https://github.com/OpenIndiana/oi-userland/pull/5605 
which replaces python-imaging with pillow and provides Python 3.5 pillow 
module. Does it fix hp-scan for you?

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Alexander Pyhalov via oi-dev 
Отправлено: 13 марта 2020 г. 23:39
Кому: Stephan Althaus; oi-dev@openindiana.org
Копия: Alexander Pyhalov
Тема: Re: [oi-dev] hplip update testing

Hi.

Not sure about py-QT, but we have to replace python-imaging with pillow to get 
hp-scan working with Py3.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Stephan Althaus 
Отправлено: 13 марта 2020 г. 22:52
Кому: oi-dev@openindiana.org
Тема: Re: [oi-dev] hplip update testing

Hi!

Did a short test, scan over net works as usual with "scanimage",
scanning via USB does not, but that never worked for me on OI.
So no differences to the previous version.
I Did hope that with the link to libusb-1 and python 3.5 there could ba
a change..

BUT theres a package missing with hp-scan
error: hp-scan requires the Python Imaging Library (PIL). Exiting.

 From what i see theres no PIL package for python-35, we need
pkg:/library/python/python-imaging-35


 From my point of view we could even go to the up-to-date-Version 3.20.3

COMPONENT_NAME= hplip
COMPONENT_VERSION=  3.20.3
COMPONENT_PROJECT_URL=
https://developers.hp.com/hp-linux-imaging-and-printing
COMPONENT_SRC=  $(COMPONENT_NAME)-$(COMPONENT_VERSION)
COMPONENT_ARCHIVE=  $(COMPONENT_SRC).tar.gz
COMPONENT_ARCHIVE_HASH=
sha256:41097ec52af5cce51ec7b0200d9f9ec82649b58ae7105259e82130e9cf63066a

With this build all the same here.
*works for me*


BTW, would it be much work to get py-QT ?


Greetings,
Stephan

On 03/12/20 21:31, Alexander Pyhalov via oi-dev wrote:
> Hi.
>
> I need reviewers and testers for 
> https://github.com/OpenIndiana/oi-userland/pull/5600. I personally have no 
> means to test it. Basic motivation for me was to switch it to Python 3.5.
> To build it you'll need 64-bit sane-backends: 
> https://github.com/OpenIndiana/oi-userland/commit/a793b0414355f0925b42c8ac67a4ef116698c3d7
>
> С уважением,
> Александр Пыхалов,
> программист отдела телекоммуникационной инфраструктуры
> управления информационно-коммуникационной инфраструктуры ЮФУ
>
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



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

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

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

Re: [oi-dev] hplip update testing

[Alexander Pyhalov via oi-dev]

Hi.

Not sure about py-QT, but we have to replace python-imaging with pillow to get 
hp-scan working with Py3.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Stephan Althaus 
Отправлено: 13 марта 2020 г. 22:52
Кому: oi-dev@openindiana.org
Тема: Re: [oi-dev] hplip update testing

Hi!

Did a short test, scan over net works as usual with "scanimage",
scanning via USB does not, but that never worked for me on OI.
So no differences to the previous version.
I Did hope that with the link to libusb-1 and python 3.5 there could ba
a change..

BUT theres a package missing with hp-scan
error: hp-scan requires the Python Imaging Library (PIL). Exiting.

 From what i see theres no PIL package for python-35, we need
pkg:/library/python/python-imaging-35


 From my point of view we could even go to the up-to-date-Version 3.20.3

COMPONENT_NAME= hplip
COMPONENT_VERSION=  3.20.3
COMPONENT_PROJECT_URL=
https://developers.hp.com/hp-linux-imaging-and-printing
COMPONENT_SRC=  $(COMPONENT_NAME)-$(COMPONENT_VERSION)
COMPONENT_ARCHIVE=  $(COMPONENT_SRC).tar.gz
COMPONENT_ARCHIVE_HASH=
sha256:41097ec52af5cce51ec7b0200d9f9ec82649b58ae7105259e82130e9cf63066a

With this build all the same here.
*works for me*


BTW, would it be much work to get py-QT ?


Greetings,
Stephan

On 03/12/20 21:31, Alexander Pyhalov via oi-dev wrote:
> Hi.
>
> I need reviewers and testers for 
> https://github.com/OpenIndiana/oi-userland/pull/5600. I personally have no 
> means to test it. Basic motivation for me was to switch it to Python 3.5.
> To build it you'll need 64-bit sane-backends: 
> https://github.com/OpenIndiana/oi-userland/commit/a793b0414355f0925b42c8ac67a4ef116698c3d7
>
> С уважением,
> Александр Пыхалов,
> программист отдела телекоммуникационной инфраструктуры
> управления информационно-коммуникационной инфраструктуры ЮФУ
>
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



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

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

Re: [oi-dev] pkg broken after recent pkg update?

[Alexander Pyhalov via oi-dev]

OK.
I have an idea what's going on - SFE GCC runtime lives in /usr/gnu/lib{/amd64}, 
and python embeds runpath to /usr/gnu/lib/amd64 due to some ncurses libraries. 
Now we have outdated GCC runtime, which loads before proper one from  
/usr/gcc/6/lib/amd64 .
So, I see two possibilities here
1) SFE uses system compilers,
2) SFE uses some non-standard paths for its compiler runtimes.

As workaround, you can remove SFE runtime libraries out of /usr/gnu/lib... 
Unfortunately, this will likely make SFE packages unusable.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Alexander Pyhalov via oi-dev 
Отправлено: 13 марта 2020 г. 17:26
Кому: Till Wegmüller; Predrag Zecevic - Unix Systems Administrator; 
oi-dev@openindiana.org
Копия: Alexander Pyhalov
Тема: Re: [oi-dev] pkg broken after recent pkg update?

Strange.
rapidjson-35 has dependency on system/library/g++-6-runtime@6.5.0-2019.0.0.2.

Can you show versions of installed pkg, rapidjson-35 and g++-6-runtime?

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ


От: Till Wegmüller 
Отправлено: 13 марта 2020 г. 16:16
Кому: Predrag Zecevic - Unix Systems Administrator; oi-dev@openindiana.org
Тема: Re: [oi-dev] pkg broken after recent pkg update?

Ah it is a problem with your version of
/usr/gcc/6/lib/amd64/libstdc++.so.6 being to old.

Can you revert to the BE before the update and run the pkg commands again?

If your version of system/library/g++-6-runtime is below
6.5.0-2019.0.0.2 you must update that manually first before updating pkg.

That should solve your problem. I have
pkg list system/library/g++-6-runtime
NAME (PUBLISHER)  VERSION
 IFO
system/library/g++-6-runtime  6.5.0-2019.0.0.2
 i--

and my pkg works.

Greetings
Till
On 13.03.20 14:00, Predrag Zecevic - Unix Systems Administrator wrote:
>
>
> On 03/13/20 13:55, Till Wegmüller wrote:
>> Hi Stephan
>>
>> Thanks for the notice.
>>
>> @Predrag looping you in as you have the same problem.
>>
>> Unfortunately you will need to revert to a previous BE to fix it.
>>
>> This seems to be a wird one. The missing symbol ist part of
>> /usr/gcc/6/lib/amd64/libstdc++.so.6 which is installed by
>> system/library/g++-6-runtime. The dependencies of the packages are
>> sound. Which version of library/python/rapidjson-35 have you installed?
>> Do you have packages from other publishers?
>>
>> I just updated a zone to test and have system/library/g++-6-runtime
>> properly installed. No problem with pkg for me.
>>
>> What is the output of the following commands on your systems?
>> ldd /usr/lib/python3.5/vendor-packages/rapidjson.cpython-35m.so
>>
>> nm /usr/gcc/6/lib/amd64/libstdc++.so.6 | grep __gxx_personality_v0
>>
>> pkg contents -m library/python/rapidjson-35 | grep
>> system/library/g++-6-runtime
>>
>> Greetings
>> Till
>>
>
> Thanks Till,
>
> here we go:
>
> :; ldd /usr/lib/python3.5/vendor-packages/rapidjson.cpython-35m.so
> libpython3.5m.so.1.0 =>  /usr/lib/64/libpython3.5m.so.1.0
> libstdc++.so.6 =>    /usr/gnu/lib/amd64/libstdc++.so.6
> libstdc++.so.6 (GLIBCXX_3.4.21) =>   (version not found)
> libstdc++.so.6 (CXXABI_1.3.9) => (version not found)
> libm.so.2 => /lib/64/libm.so.2
> libgcc_s.so.1 => /usr/gnu/lib/amd64/libgcc_s.so.1
> libc.so.1 => /lib/64/libc.so.1
> librt.so.1 =>    /lib/64/librt.so.1
> libintl.so.1 =>  /lib/64/libintl.so.1
> libdl.so.1 =>    /lib/64/libdl.so.1
> libsendfile.so.1 =>  /lib/64/libsendfile.so.1
>
> :; nm /usr/gcc/6/lib/amd64/libstdc++.so.6 | grep __gxx_personality_v0
> 000dadd0 T __gxx_personality_v0
> 001c31e0 d DW.ref.__gxx_personality_v0
>
> :; pkg contents -m library/python/rapidjson-35 | grep
> system/library/g++-6-runtime
> 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/hardlink.py",
> line 33, in 
> from . import generic, link
>   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/va

Re: [oi-dev] pkg broken after recent pkg update?

[Alexander Pyhalov via oi-dev]

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/group.py", line
>>> 33, 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
>>> 
>>>
>>> Did i miss something?
>>>
>>>
>>> Greetings,
>>> Stephan
>>>
>>>
>>> On 03/12/20 21:31, Alexander Pyhalov via oi-dev wrote:
>>>> Hi.
>>>>
>>>> I need reviewers and testers for
>>>> https://github.com/OpenIndiana/oi-userland/pull/5600. I personally
>>>> have no means to test it. Basic motivation for me was to switch it to
>>>> Python 3.5.
>>>> To build it you'll need 64-bit sane-backends:
>>>> https://github.com/OpenIndiana/oi-userland/commit/a793b0414355f0925b42c8ac67a4ef116698c3d7
>>>>
>>>>
>>>>
>>>> С уважением,
>>>> Александр Пыхалов,
>>>> программист отдела телекоммуникационной инфраструктуры
>>>> управления информационно-коммуникационной инфраструктуры ЮФУ
>>>>
>>>>
>>>> ___
>>>> oi-dev mailing list
>>>> oi-dev@openindiana.org
>>>> https://openindiana.org/mailman/listinfo/oi-dev
>>>
>>>
>>>
>>> ___
>>> oi-dev mailing list
>>> oi-dev@openindiana.org
>>> https://openindiana.org/mailman/listinfo/oi-dev
>

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

[oi-dev] hplip update testing

[Alexander Pyhalov via oi-dev]

Hi.

I need reviewers and testers for 
https://github.com/OpenIndiana/oi-userland/pull/5600. I personally have no 
means to test it. Basic motivation for me was to switch it to Python 3.5.
To build it you'll need 64-bit sane-backends: 
https://github.com/OpenIndiana/oi-userland/commit/a793b0414355f0925b42c8ac67a4ef116698c3d7

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ


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

Re: [oi-dev] perl module update questions

[Alexander Pyhalov]

Hi.


>> 1) I've found one or two cases like

 >>  oi-userland/components/perl/xml-simple/xml-simple-PERLVER.p5m

>> where the .p5m file contains an explicit dependency upon the
>> non-perl-specific metapackage:

>>depend fmri=library/perl-5/xml-parser type=require

>> Should all of the perl-version-specific packages have this dependency
>> relation?

Yes, all version-specific packages should depend on non-version-specific 
package, and that one should provide (and automatically provides) conditional 
dependency on version-specific package, I mean:

depend fmri=library/perl-5/xml-parser-522@2.44,5.11-2018.0.0.0 
predicate=runtime/perl-522 type=conditional
depend fmri=library/perl-5/xml-parser-524@2.44,5.11-2018.0.0.0 
predicate=runtime/perl-524 type=conditional


>> 2) If I publish e.g. xml-parser, with my runtime/perl-530 installed,
>> there are 4 xml-parser packages generated:

>>   library/perl-5/xml-parser 2.44-2020.0.0.1

>> What's the correct terminology for the first package
>> (library/perl-5/xml-parser)?  Is it a mediator?

No, mediator is a special image attribute which manages default program 
implementation.
Don't know a correct terminology for this common package.

>> 3) many of the perl modules currently have a 'history' file.  This seems
>> to trigger some additional behavior from the publish target, apparently
>> via make-rules/history.mk.  In these cases, publish is generating an
>> additional versioned package and adding it to my repo.  The package
>> doesn't have any file contents, though, and it's flagged as "obsolete".
>> What's the purpose of all of that?

It generates packages whith pkg.obsolete or pkg.renamed attribute, which makes 
pkg remove this package on update or replace it with another package. This is a 
mechanism of removing old packages.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Tim Mooney 
Отправлено: 6 марта 2020 г. 21:38
Кому: oi-dev@openindiana.org
Тема: [oi-dev] perl module update questions


All-

I'm working my way through rebuilding hipster's perl modules for perl
5.30.1 and I have a couple questions.

1) I've found one or two cases like

   oi-userland/components/perl/xml-simple/xml-simple-PERLVER.p5m

where the .p5m file contains an explicit dependency upon the
non-perl-specific metapackage:

depend fmri=library/perl-5/xml-parser type=require

Because of that depend, if I were to

 pfexec pkg install library/perl-5/xml-parser-530

I would get both library/perl-5/xml-parser-530 and
library/perl-5/xml-parser.

Should all of the perl-version-specific packages have this dependency
relation?  If not, what criteria do I use to determine whether that
should be added to the .p5m file or not?


2) If I publish e.g. xml-parser, with my runtime/perl-530 installed,
there are 4 xml-parser packages generated:

library/perl-5/xml-parser 2.44-2020.0.0.1
library/perl-5/xml-parser-522 2.44-2020.0.0.1
library/perl-5/xml-parser-524 2.44-2020.0.0.1
library/perl-5/xml-parser-530 2.44-2020.0.0.1

What's the correct terminology for the first package
(library/perl-5/xml-parser)?  Is it a mediator?


3) many of the perl modules currently have a 'history' file.  This seems
to trigger some additional behavior from the publish target, apparently
via make-rules/history.mk.  In these cases, publish is generating an
additional versioned package and adding it to my repo.  The package
doesn't have any file contents, though, and it's flagged as "obsolete".

What's the purpose of all of that?

Is there anything I should be doing related to 'history' if I add new
perl modules or update existing ones?

I would like to follow the proper procedure for any modules I add or
update, but at least for 'history', I'm not sure what that is.  It doesn't
seem to be covered in the IPS dev guide, that I can find.

Thanks!

Tim
--
Tim Mooney tim.moo...@ndsu.edu
Enterprise Computing & Infrastructure /
Division of Information Technology/701-231-1076 (Voice)
North Dakota State University, Fargo, ND 58105-5164

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

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

Re: [oi-dev] perl module update questions

[Alexander Pyhalov via oi-dev]

Hi.


>> 1) I've found one or two cases like

 >>  oi-userland/components/perl/xml-simple/xml-simple-PERLVER.p5m

>> where the .p5m file contains an explicit dependency upon the
>> non-perl-specific metapackage:

>>depend fmri=library/perl-5/xml-parser type=require

>> Should all of the perl-version-specific packages have this dependency
>> relation? 

Yes, all version-specific packages should depend on non-version-specific 
package, and that one should provide (and automatically provides) conditional 
dependency on version-specific package, I mean:




2) If I publish e.g. xml-parser, with my runtime/perl-530 installed,
there are 4 xml-parser packages generated:

library/perl-5/xml-parser 2.44-2020.0.0.1
library/perl-5/xml-parser-522 2.44-2020.0.0.1
library/perl-5/xml-parser-524 2.44-2020.0.0.1
library/perl-5/xml-parser-530 2.44-2020.0.0.1

What's the correct terminology for the first package
(library/perl-5/xml-parser)?  Is it a mediator?


3) many of the perl modules currently have a 'history' file.  This seems
to trigger some additional behavior from the publish target, apparently
via make-rules/history.mk.  In these cases, publish is generating an
additional versioned package and adding it to my repo.  The package
doesn't have any file contents, though, and it's flagged as "obsolete".

What's the purpose of all of that?

Is there anything I should be doing related to 'history' if I add new
perl modules or update existing ones?

I would like to follow the proper procedure for any modules I add or
update, but at least for 'history', I'm not sure what that is.  It doesn't
seem to be covered in the IPS dev guide, that I can find.

Thanks!

Tim
--
Tim Mooney tim.moo...@ndsu.edu
Enterprise Computing & Infrastructure /
Division of Information Technology/701-231-1076 (Voice)
North Dakota State University, Fargo, ND 58105-5164

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

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

Re: [oi-dev] Totem sad story

[Alexander Pyhalov via oi-dev]

If it worked for you, it costs looking at. Have you actually used it with 
non-nvidia adapter (at least, in virtualbox or with vesa)?

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Tim Mooney 
Отправлено: 21 февраля 2020 г. 22:36
Кому: Alexander Pyhalov via oi-dev
Тема: Re: [oi-dev] Totem sad story

In regard to: [oi-dev] Totem sad story, Alexander Pyhalov via oi-dev said...:

> Another option is to dig in clutter-gst and recent totem, but I'm not
> sure in the result.

I've built clutter-gst and a bunch of the other prereqs needed for a more
modern totem.  I built totem 3.24 on hipster perhaps 3 or 4 months ago.
At the time, 3.24 was the newest I could build because anything after that
required meson.  I haven't been back to it since hipster got meson and
meson.mk/ninja.mk.

The clutter-based interface is wildly different from the current
interface.  I recall there were some issues with the new grilo-based
plugins, including the youtube & vimeo plugins.  I didn't look any deeper
into that.

I can dust this off and submit pulls for the work that I have, if you want
to take a look at it.

Tim
--
Tim Mooney tim.moo...@ndsu.edu
Enterprise Computing & Infrastructure /
Division of Information Technology/701-231-1076 (Voice)
North Dakota State University, Fargo, ND 58105-5164

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

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

[oi-dev] Totem sad story

[Alexander Pyhalov via oi-dev]

Hi.
Currently we ship slightly patched (just 12 patches ;)) totem 3.0.1. 
The issue is that somewhere between 3.0.1 and 3.1 totem moved to clutter-gst.
Last time I looked at it, totem used OpenGL to draw video and this could work 
really ugly, for example, in VirtualBox non-accelerated environment.
So, we came with 3.0.1 version. This is a bit of context...

Now, why we need totem: due to fact that it's plain gstreamer player, there's 
no license issues with distributing player (v.s. , for example, vlc). 

The problem which made me look at it again is that totem currently depends on 
Python 2. 
And I hope to remove Python 2.7 from base images till 2020.04.  

Now, I came with this solution - https://github.com/pyhalov/totem/tree/py3  
which gets about 60 patches from upstream to switch to python 3. 
I dislike idea just to create component with 60 patches on top of totem 3.0.1, 
so basic idea is to create own outdated totem clone. Sounds perfect, right? But 
at least this approach costs me about a day of the work and is 
already kind of working - https://github.com/OpenIndiana/oi-userland/pull/5565 .
I appreciate some testing of this component.

Another option is to dig in clutter-gst and recent totem, but I'm not sure in 
the result. 

Of course I consider second option to  be correct one, but for now I don't have 
time to dig into it. 

Best regards, 
Alexander Pyhalov, 
system administrator of Southern Federal University IT department



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

Re: [oi-dev] GOCACHE for Jenkins jobs

[Alexander Pyhalov via oi-dev]

Because this time it happened to mongo.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Michal Nowak via oi-dev 
Отправлено: 29 января 2020 г. 10:47
Кому: oi-dev@openindiana.org
Копия: Michal Nowak
Тема: Re: [oi-dev] GOCACHE for Jenkins jobs

We came across this problem before and therefor added

   COMPONENT_BUILD_ENV += GOCACHE="$(SOURCE_DIR)/gocache"

to golang-11{2,3} packages.

Any idea why this still failed?

Michal

On 01/27/20 09:37 AM, Till Wegmüller wrote:
> Hi Aurelien
>
> Yes you must define GOCACHE. Go modules requires this path to download
> and unpack/compile Build dependencies. It will also speed up any
> subsequent runs if this Cache is globally.
>
> Here is my Jenkins config for go 1.11+
>
>  environment {
>   GOCACHE = "${WORKSPACE}/gocache"
>   GO111MODULE = "on"
>   GOPATH = "${WORKSPACE}/../gopath"
>  }
>
> GO111MODULE might not be necessary depending on the Software you are
> building but they have to include a note if they do not support go
> modules yet. Acording to the Go community it is advised to file a
> upstream bug of Go modules are not yet supported.
>
> If you need any Help with Go let me know. I Programm with it as my Day
> Job and maintain the OpenIndiana Packages. Chances are I have come
> accross an issue before :)
>
> Greetings
> Till
>
>
> On 26.01.20 23:49, Aurélien Larcher wrote:
>> Hi,
>> it seems that MongoDB 3.4 fails to build on Jenkins because Go 1.12
>> requires a path used for caching files.
>>
>> "build cache is required, but could not be located: GOCACHE is not
>> defined and neither $XDG_CACHE_HOME nor $HOME are defined Error building
>> bsondump"
>>
>> As a workaround I defined a GOCACHE variable in the Jenkins
>> configuration but that is probably not suitable in the long run.
>>
>> Kind regards,
>>
>> Aurelien
>>
>> --
>> ---
>> Praise the Caffeine embeddings
>>
>> ___
>> oi-dev mailing list
>> oi-dev@openindiana.org
>> https://openindiana.org/mailman/listinfo/oi-dev
>>
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>

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

[oi-dev] DLNA server

[Alexander Pyhalov via oi-dev]

Hi.

I've just removed coherence, as it's not maintained. I suppose we need to 
provide some alternative DLNA server.

I could look at minidlna (but it seems to be dead) or gerbera (rather active, 
but seems to be over-complicated). Are there any other suggestions?

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ


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

Re: [oi-dev] updating the perl stack on hipster

[Alexander Pyhalov via oi-dev]

Hi.

1) perl sun_solaris module is provided by illumos-gate. illumos-gate is 
currently built with Perl 5.22.  The tricky issue is that to build illumos-gate 
with Perl 5.30 you need Perl 5.30 sun_solaris modules. The following sequence 
usually worked:
Compile illumos-gate with Perl 5.30. First build fails, but produces necessary 
modules. Copy them to the build server. Rebuild illumos-gate.
OI-userland component was used to provide modules for perl version different 
from one used to build illumos-gate and now is not used.

2) I think the plan should look like this.
- Deliver Perl 5.30.
- Deliver Perl 5.30 modules.
- Check what dependencies on Perl 5.22 we have, especially depenencies on 
libraries (net-snmp? PostgreSQL?) and try to rebuilt it with Perl 5.30. Can be 
tricky, given that Perl 5.22 was 32-bit. Perhaps, will have to drop some 32-bit 
binaries/libraries.
- Switch illumos-gate to Perl 5.30.
- Deprecate Perl 5.22.
- C


С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Tim Mooney 
Отправлено: 4 января 2020 г. 1:07
Кому: oi-dev@openindiana.org
Тема: [oi-dev] updating the perl stack on hipster


I would like to get both the perl runtime and the collection of perl
modules we ship updated to something recent.

I have packages for runtime/perl-530 (5.30.1) and several of our easiest
modules (those with no additional module dependencies) built for that
runtime.  Before I move on to the more difficult modules, I want to make
certain I'm on the right track.

I have several questions about the sun-solaris perl module collection, and
I'm hoping someone has some guidance.

- this is the only perl module we ship that is in the

/runtime/perl-NNN/module/sun-solaris

namespace, rather than

/library/perl-5/sun-solaris-NNN

   Anyone know why it's in the /runtime namespace, rather than the
   /library namespace?  I'm trying to understand why it's an
   exception that doesn't match any of the other module naming conventions.

- The component we currently ship (runtime/perl-522/module/sun-solaris)
   was not generated from the current oi-userland/perl/sun-solaris sources.
   The files in that directory are still set to perl-516 and the packaged
   component includes PerlGcc and Exacct, both of which appear to have
   been dropped from runtime/perl-522/module/sun-solaris.

   Was the source code moved somewhere else (I've looked and haven't found
   it) or were the changes that built runtime/perl-522/module/sun-solaris
   perhaps never committed?

I'm mainly trying to determine whether I should include Exacct when I
update the sun-solaris module, or drop it as the perl-522 has apparently
done.  PerlGcc should definitely be dropped.

- once I have sun-solaris and remaining modules packaged for perl-530,
   what's the easiest method (from the perspective of the core developers)
   to proceed?

 - a "meta" pull request, that references each individual pull request?
- make 530 and modules available before obsoleting/removing perl-524?
- how do we go about eventually getting rid of perl-522?

I know that long-term we don't want to be providing 3 versions of perl,
I'm just not certain what the transition process should look like.

Tim
--
Tim Mooney tim.moo...@ndsu.edu
Enterprise Computing & Infrastructure /
Division of Information Technology/701-231-1076 (Voice)
North Dakota State University, Fargo, ND 58105-5164

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

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

[oi-dev] How does one stop meson from generating -pie?

[Alexander Pyhalov via oi-dev]

Hi. 
Has someone dealt with meson? 
Our meson generates 

LINK_ARGS = -pie -m32 -O3 -Wno-error=format-nonliteral -m32 -lsocket -lsecdb 
-lnsl glib/libglib-2.0.so.0.6200.3 -lm -pthread '-Wl,-rpath,$$ORIGIN/../glib'...

It seems it has strange logic: build every executable with '-pie' and static 
libraries with '-fpic'...

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ


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

[oi-dev] Slim Source update needs testing

[Alexander Pyhalov via oi-dev]

Hi.

I've prepared PR which switches slim source to Py3:
https://github.com/OpenIndiana/slim_source/pull/61
It needs reviewers.

Also I've prepared test images: http://buildzone.oi-build.r61.net/installer-py3/
They need testing.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ


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

Re: [oi-dev] Would OI be interested in Pale Moon?

[Alexander Pyhalov via oi-dev]

Hi.
I was a bit of uncomfortable to point to this issue, but as others already 
mention this, let this be settled. We will not distribute Pale Moon via OI 
infrastructure. If someone has free cycles, I'd advice him to look at FF 
component, which needs some love.

Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department


От: Adam Števko 
Отправлено: 11 декабря 2019 г. 11:36
Кому: OpenIndiana Developer mailing list
Тема: Re: [oi-dev] Would OI be interested in Pale Moon?

Thanks Michal for pointing that out. I wasn’t aware of that. Additional reason 
to avoid it then :)

> On 11 Dec 2019, at 09:22, Michal Nowak via oi-dev  
> wrote:
>
> On 12/11/19 07:38 AM, Jeremy Andrews wrote:
>> I ported UXP to illumos and Solaris recently, and I got them to take the
>> code upstream. I'm pretty anxious about the process now honestly, and
>> really want everything to work out. There are a few things I'm worried
>> about, though.
>> 1. I'm not very familiar with how packages are actually packaged for OI,
>> and the p5m file for Firefox in particular is... so complicated that
>> I've been holding off creating a Pale Moon system package for OI until
>> now, when they're pushing me to try. I was hoping that the subject
>> wouldn't come up and they'd just want to distribute a binary .tar.xz
>> file like they do for other operating systems (that kind of package is
>> very easy to create with a single command). I'm so mixed up because the
>> .p5m file for Firefox 52 looks so different from the one for Firefox 60,
>> and includes all these header files, is for 32-bit, etc. And I'm trying
>> to figure out which differences are due to a change in package design,
>> and which are due to actual differences in Firefox.
>> 2. Pale Moon has some unusual requirements. For one thing, it can't use
>> the system NSS because Mozilla has changed the API somewhat since they
>> forked. In general, they're leery of using system libraries over the
>> ones in their own tree because sometimes those libraries have to be
>> modified in specific ways for the browser. On top of that, they seem to
>> have a problem with distributing the langpacks with the browser. They
>> have a site where you can download a langpack of your choice, but you
>> can't ship it with the browser for some reason.
>> I'm kind of afraid now that I've done all this for nothing. I'm worried
>> that their packaging requirements and our packaging requirements may not
>> line up, and I'll wind up only being able to distribute a tarball on my
>> own web space that no one will ever download. It's a very good browser,
>> and the people behind it are actually decent people, but... I'm
>> overwhelmed with the sense that I've gotten in over my head.
>
> Given the hostility Pale Moon developers showed towards a license 
> non-complying OpenBSD port at 
> https://github.com/jasperla/openbsd-wip/issues/86, I'd rather avoid this 
> community at all.
>
> The other reason is maintenance cost on the OpenIndiana project. We already 
> have Firefox and due to it's complexity it gives us hard time to keep-up even 
> with ESR releases (currently we are stuck at version 60, 68 is the latest 
> one; the story for the 52->60 transition was the same). Same with 
> Thunderbird. I am afraid Pale Moon would be another chapter of the very same 
> story.
>
> Michal
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev

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

Re: [oi-dev] Where should SPARC go?

[Alexander Pyhalov via oi-dev]

Hi, Gary.



От: Gary Mills 
Отправлено: 18 ноября 2019 г. 0:39
Кому: oi-dev@openindiana.org
Тема: [oi-dev] Where should SPARC go?


> First of all, how much interest do you have in OI on SPARC?  My
interest is as a developer and tester.  What is your interest?
I'd like to determine the size of the audience.

I'm not sure about ways of collaboration which would be beneficial to both x86 
and SPARC build. 
The most important question for me is testing SPARC build.
Let's say, I update component A. It has some SPARC-specific patches. They don't 
apply. What should I do? Drop them and hope someone interested in SPARC fixes 
it? I don't think it'll suit you. 
So, first of all we need some build host, where changes could be checked.
At least that they build. What if they build, but doesn't work? I have to spend 
some time to find out, what's wrong with this package on SPARC. This doesn't 
suit me ;)

So, I see the following 'ideal' world.
1) There's  a set of OI/SPARC build zones, available to OI developers.
2) There's a branch (or clone) of oi-userland, which is 'current OI SPARC head'
3) These repositories/branches are merged when changes are ready.
4) Preferably,  we have means to build each PR on SPARC with little effort.
5) In ideal world, both SPARC/x64 bits would live in one repository, but this 
requires merging packages built for separate architectures. I don't expect this 
to happen (soon?). But at least we need some 'current-state-of-the-art' SPARC 
repository. I suppose we can host it on OI pkg server, if 1-3 are satisfied.

What about current steps which will at least partially lead us to 'ideal' world.
1) We need SPARC zone with jenkins, which automatically builds some subset of 
packages, which are known to be working on SPARC.
2) I can create a oi/sparc branch on OI repo for current SPARC work, which will 
periodically be merged to oi/hipster.
But without 1) I thinks further talk is useless.

P.S. Now I have less and less free time which I can devote to OI. I will not be 
able to spend a lot of time on OI/SPARC (and would prefer to spend it on OI/x64 
if there's choice ;) ).


>>> How should I contribute to OI on SPARC?  I have plans to build more
packages, and to do so with fewer changes to the OI source.  I also
have plans to update the distribution from the current 2018 to 2019 or
2020.  Does this sound reasonable to you?

How should you contribute to OI on SPARC?  I've filed bug reports
for many of the changes I've made.  They can be seen at:

https://www.illumos.org/projects/openindiana/issues

I've attached patches to each bug report, but in order for these
patches to be integrated into the OI source, the patches need to be
turned into PRs for github.  They also need to be tested on x86 to
make sure they don't accidentally change anything there.  Can you help
with any of this?  Can you build packages for SPARC from OI source?
Can you help in any other way?

What type of repository do you prefer?  Should it be file-based, as it
is now, or should it be remote, as for OI x86?  The repository will
only get larger, as people build more packages and publish them.  Will
you download such a large file?  I don't know of any way to merge
repositories, so there must be only one.

Finally, who should coordinate OI on SPARC?  Should this be done by
the OI project, or should it be done separately?  Keep in mind that OI
SPARC uses OI source.  Most of it builds and publishes with no
changes.  When changes are necessary, my plan has been to introduce
them with no harm to x86 packages built from the same source.  Indeed,
some of the changes fix bugs in the corresponding x86 packages.  Also
keep in mind that IPS is designed to handle multiple architectures,
making it easy to integrate SPARC with x86.  In fact, this is already
done for illumos.


--
-Gary Mills--refurb--Winnipeg, Manitoba, Canada-

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

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

[oi-dev] OpenIndiana Hipster 2019.10

[Alexander Pyhalov via oi-dev]

Hi.

OpenIndiana Hipster 2019.10 snapshot is ready.

Images:

http://dlc.openindiana.org/isos/hipster/20191106/OI-hipster-gui-20191106.iso
http://dlc.openindiana.org/isos/hipster/20191106/OI-hipster-gui-20191106.usb

http://dlc.openindiana.org/isos/hipster/20191106/OI-hipster-text-20191106.iso
http://dlc.openindiana.org/isos/hipster/20191106/OI-hipster-text-20191106.usb

http://dlc.openindiana.org/isos/hipster/20191106/OI-hipster-minimal-20191106.iso
http://dlc.openindiana.org/isos/hipster/20191106/OI-hipster-minimal-20191106.usb


SHA 256 checksums are available at ${link}.sha256sum
Signed SHA 256 checksums are available at ${link}.sha256sum.asc
The OpenIndiana Release Engineering key has key id 0x3a021afadbe31887 (
https://sks-keyservers.net/pks/lookup?op=get=0x3A021AFADBE31887 ).

Release notes: http://docs.openindiana.org/release-notes/2019.10-release-notes/

Note, we have an issue with Firefox on live image - it can fail to start 
correctly when launched for the first time in memory-constrained  environment. 
After being killed and restarted it behaves more sane.

Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Pecular dependancies in publishing print/cups-filters

[Alexander Pyhalov via oi-dev]

What are RUNPATH and RPATH of usr/lib/cups/filter/pdftopdf file ?

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Gary Mills 
Отправлено: 14 августа 2019 г. 18:42
Кому: OpenIndiana Developer mailing list
Тема: Re: [oi-dev] Pecular dependancies in publishing print/cups-filters

On Wed, Aug 14, 2019 at 04:14:51PM +0200, Aurélien Larcher wrote:
>On Wed, Aug 14, 2019 at 4:11 PM Aurélien Larcher
><[1]aurelien.larc...@gmail.com> wrote:
>
>The error tells you that no package in the REQUIRED_PACKAGES list
>provides a suitable dependency.

Well, that's what it usually means.  In this case:

depend type=require fmri=__TBD \
pkg.debug.depend.fullpath=usr/lib/libjpeg6-ijg/lib/libgcc_s.so.1 \
pkg.debug.depend.reason=usr/lib/cups/filter/pdftopdf \
pkg.debug.depend.type=elf'.

what is pkg looking for?  Is it libgcc_s.so.1?  That's in the
system/library/gcc-6-runtime package, which is in the
REQUIRED_PACKAGES list.  Or, is it
usr/lib/libjpeg6-ijg/lib/libgcc_s.so.1?  That is not in any package.


--
-Gary Mills--refurb--Winnipeg, Manitoba, Canada-

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

[oi-dev] [HEADS UP] IPS is Python 3-only now

[Alexander Pyhalov via oi-dev]

Hi.

Today large IPS update was merged. It delivered numerous upstream fixes and one 
big change.

IPS doesn't longer deliver Python 2.7 packages.

What does it mean for user? Possibly, not much, perhaps, just some 
UnicodeDecodeError issues ;)

One issue I've seen is that if you update pkg in GZ can be not able to update 
child images, so you'll have to update pkg in zones first.

What does it mean for developer?
1) You can't longer build Python 2.7 illumos-gate tools, so don't forget to add 
export BUILDPY2TOOLS="#"
to your illumos.sh

2) Older oi-userland tools will fail, please ensure your oi-userland has the 
following commit - 
https://github.com/OpenIndiana/oi-userland/commit/fb10babbcfd65ff74cf439bc77a2186fd79ee2a7

3) onbld tools SHOULD use Python 3.5 to work correctly (update to the latest 
package).



Best regards, 
Alexander Pyhalov, 
system administrator of Southern Federal University IT department



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

[oi-dev] pkg move to Python3.5 only

[Alexander Pyhalov via oi-dev]

Hi.

I've prepared two PRs: https://github.com/OpenIndiana/pkg5/pull/65 and 
https://github.com/OpenIndiana/oi-userland/pull/5192. 
First one imports latest fixes from OmniOS CE PKG repo, second switches 
oi-userland tools to use Python 3.5. Second PR should be merged immediately 
after first, as oi-userland uses Python 2.7 pkg modules.

I want some review (mostly, of userland parts) and testing (if possible).

Ideally I'd like to see full oi-userland rebuild with new PKG installed and 
PR#5192 applied.
 

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ


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

Re: [oi-dev] Clang and GCC6 runtime

[Alexander Pyhalov via oi-dev]

It seems LLVM OpenMP library has not a single Solaris-specific line...

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Alexander Pyhalov via oi-dev 
Отправлено: 31 июля 2019 г. 22:28
Кому: Alexander Pyhalov via oi-dev
Копия: Alexander Pyhalov
Тема: Re: [oi-dev] Clang and GCC6 runtime

No, -fopenmp seems to be implemented wrong.
_REENTRANT is not defined, libgomp is not linked.
If we specify "clang++  omp.cc -fopenmp=libgomp -o omp", application is linked, 
but pragma parallel uses just one thread.

When -pthreads is used, _REENTRANT is undefined.

-pthread seems to work as expected.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Bob Friesenhahn 
Отправлено: 31 июля 2019 г. 21:48
Кому: Alexander Pyhalov via oi-dev
Тема: Re: [oi-dev] Clang and GCC6 runtime

On Wed, 31 Jul 2019, Alexander Pyhalov via oi-dev wrote:

> OK
> I have almost working Clang 8.0.1.

Do the normal -pthreads and -fopenmp (OpenMP) options work with this
build?  I was excited when I found Clang 8 available from pkgsrc but
was disappointed when I found that GCC options normally available from
Solaris are not working.  It may be that Clang is lacking
customizations necessary to emulate GCC under Solaris-derived systems.

Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/
Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt

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

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

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

Re: [oi-dev] Clang and GCC6 runtime

[Alexander Pyhalov via oi-dev]

No, -fopenmp seems to be implemented wrong.
_REENTRANT is not defined, libgomp is not linked.
If we specify "clang++  omp.cc -fopenmp=libgomp -o omp", application is linked, 
but pragma parallel uses just one thread.

When -pthreads is used, _REENTRANT is undefined.

-pthread seems to work as expected.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Bob Friesenhahn 
Отправлено: 31 июля 2019 г. 21:48
Кому: Alexander Pyhalov via oi-dev
Тема: Re: [oi-dev] Clang and GCC6 runtime

On Wed, 31 Jul 2019, Alexander Pyhalov via oi-dev wrote:

> OK
> I have almost working Clang 8.0.1.

Do the normal -pthreads and -fopenmp (OpenMP) options work with this
build?  I was excited when I found Clang 8 available from pkgsrc but
was disappointed when I found that GCC options normally available from
Solaris are not working.  It may be that Clang is lacking
customizations necessary to emulate GCC under Solaris-derived systems.

Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/
Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt

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

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

Re: [oi-dev] Clang and GCC6 runtime

[Alexander Pyhalov via oi-dev]

OK
I have almost working Clang 8.0.1.

The only issue, it doesn't include G++ runpaths in resulting binary. But 
(suddenly), resulting binaries seem to work with either runtime (GCC4 or 6)...

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Aurélien Larcher 
Отправлено: 30 июля 2019 г. 18:40
Кому: Alexander Pyhalov
Тема: Re: Clang and GCC6 runtime

I also wonder what caused breakage of this component as I have used it for my 
research projects until last year, including compiled with gcc-8 in my build 
zone.

On Tue, Jul 30, 2019 at 4:36 PM Alexander Pyhalov 
mailto:a...@sfedu.ru>> wrote:
Hi.

I've looked at https://www.illumos.org/issues/11507, and first issue is clear, 
01-openindiana.patch needs fixing.

diff --git a/components/developer/clang-40/patches/01-openindiana.patch 
b/components/developer/clang-40/patches/01-openindiana.patch
index cf4548b7e..f18920444 100644
--- a/components/developer/clang-40/patches/01-openindiana.patch
+++ b/components/developer/clang-40/patches/01-openindiana.patch
@@ -65,15 +65,15 @@ diff -ruN 
llvm-4.0.0.src/tools/clang/lib/Driver/ToolChains.cpp 
llvm-4.0.0.src.pa<http://llvm-4.0.0.src.pa>
 +  std::string GCCVersion = OPENINDIANA_GCC_VERSION;
switch (Triple.getArch()) {
case llvm::Triple::x86:
-+GCCLibPath += ("i386-" + Triple.getVendorName() + "-" + 
Triple.getOSName()).str() + "/"+GCCVersion+"/";
++GCCLibPath += ("/i386-" + Triple.getVendorName() + "-" + 
Triple.getOSName()).str() + "/"+GCCVersion+"/";
case llvm::Triple::sparc:
  break;
case llvm::Triple::x86_64:
-+GCCLibPath += ("i386-" + Triple.getVendorName() + "-" + 
Triple.getOSName()).str() + "/"+GCCVersion+"/amd64";
++GCCLibPath += ("/i386-" + Triple.getVendorName() + "-" + 
Triple.getOSName()).str() + "/"+GCCVersion+"/amd64";
  LibPath += "amd64/";
  break;
case llvm::Triple::sparcv9:
-+GCCLibPath += ("sparc-" + Triple.getVendorName() + "-" + 
Triple.getOSName()).str() + "/"+GCCVersion+"/sparcv9";
++GCCLibPath += ("/sparc-" + Triple.getVendorName() + "-" + 
Triple.getOSName()).str() + "/"+GCCVersion+"/sparcv9";
  LibPath += "sparcv9/";
  break;
default:


The second issue is worse. After applying this patch I see the following issues 
with simple c++ programs:

clang++ 1.cc -o 1
(or  clang++ 1.cc -Wl,-L/usr/gcc/6/lib -Wl,-R/usr/gcc/6/lib -o 1), doesn't 
matter much.

$ ./1
Segmentation Fault (core dumped)
$ pstack core
core 'core' of 18083:   ./1
 feee60d2 _ZNSo6sentryC1ERSo (8047b48, 8061480, 200, 40) + 22
 feee67c8 
_ZSt16__ostream_insertIcSt11char_traitsIcEERSt13basic_ostreamIT_T0_ES6_PKS3_i 
(8061480, 8051181, 1, 30) + 28
 feee6c22 _ZStlsISt11char_traitsIcEERSt13basic_ostreamIcT_ES5_PKc (8061480, 
8051181, 8047c1c, 805114f, 8061184, 8050e5e) + 32
 08051122 main (1, 8047c1c, 8047c24, 8050f52, 0, 0) + 32
 08050f77 _start_crt (1, 8047c1c, fefcfed4, 0, 0, 0) + 96
 08050e4a _start   (1, 8047d10, 0, 8047d14, 8047d28, 8047d41) + 1a


Do I understand correctly that it's issue with GCC C++ ABI and we either have 
to use GCC 4 runntime libraries for clang or update clang ?


С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



--
---
Praise the Caffeine embeddings
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] Let's clean up PR queue

[Alexander Pyhalov via oi-dev]

Hey, people. 

We have over 60 PR in the queue. Let's clean up it a bit.

Please, look at your PR and think why did they stuck in current state? 
Do they need testing? Or updating ? Or a bit more work?

Let's clean up the queue a bit. 
Don't hesistate to contact others if you need some review or test results.

Best regards, 
Alexander Pyhalov, 
system administrator of Southern Federal University IT department

управления информационно-коммуникационной инфраструктуры ЮФУ


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

Re: [oi-dev] DDU testing

[Alexander Pyhalov via oi-dev]

Hi.
I've tried to port DDU to Python 3.5. And I consider it working. It doesn't 
mean it is working - testing GUI Python applications is PITA :)

If someone wants to review or test https://github.com/OpenIndiana/ddu/pull/1 , 
I'll be glad to hear comments.

To test it, I suggest using 
https://github.com/OpenIndiana/oi-userland/pull/5103, just change GIT_REPO to 
https://github.com/pyhalov/ddu and GIT_BRANCH to py3 .

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Alexander Pyhalov via oi-dev 
Отправлено: 24 июня 2019 г. 18:12
Кому: OpenIndiana Developer mailing list
Копия: Alexander Pyhalov
Тема: [oi-dev] DDU testing

Hi.

I've finished replacing DDU binaries with binaries from DDU 1.2 and rewriting 
missing parts.
Result is here: https://github.com/OpenIndiana/ddu/ .
I suggest it can get wider testing.
You can use openindiana/ddu component  from 
https://github.com/OpenIndiana/oi-userland/pull/5103 to build and test it.

I'm waiting for test results and reviews.

Changes from current DDU (shipped with OI now).
1) pt_BR localization files removed as msgunfmt couldn't unparse them;
2) Database of third-party drivers was removed (it was obsolete  with it seems 
one working link from dozen). I suppose nobody volunteers to support it in 
actual state.
3) I hope finally I've made DDU help behave - now it shows help in user locale, 
images are not removed.
4) I've regenerated database of existing OI drivers shipped with DDU, updated 
pci.ids and usb.ids files.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ


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

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

[oi-dev] jenkins update and build server issues

[Alexander Pyhalov via oi-dev]

Hi.

I've updated Jenkins on hipster.openindiana.org and changed it settings to log 
less. Last time Jenkins logs consumed all free space on build server.  One of 
the reasons - https://issues.jenkins-ci.org/browse/JENKINS-25369 . I've also 
disabled MDNS. 

I've also  created https://github.com/OpenIndiana/oi-userland/pull/5123/files , 
but I'm not sure that it's related to recent illumos-gate job build failures.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ


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

Re: [oi-dev] OI Hipster 2019.04

[Alexander Pyhalov via oi-dev]

Hi.
entire is a package which depends on userland-incorporation. That's all. You 
are interested in latest osnet-incorporation and userland-incorporation.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Richard Lowe 
Отправлено: 28 июня 2019 г. 20:43
Кому: OpenIndiana Developer mailing list
Тема: Re: [oi-dev] OI Hipster 2019.04

I think that's me not-remembering whether doing that with entire would
do the right thing, did you try specifying @latest for all the
incorporations in the original error?

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

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

Re: [oi-dev] Toward a SPARC distro of OI

[Alexander Pyhalov via oi-dev]

BTW, while working on DDU I've removed SPARC parts I've encountered ;)
Anyway I had no way (or desire) to test them.
Most interesting is likely dmi_info.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Gary Mills 
Отправлено: 24 июня 2019 г. 18:33
Кому: OpenIndiana Developer mailing list
Тема: Re: [oi-dev] Toward a SPARC distro of OI

On Mon, Jun 17, 2019 at 01:26:59PM +0200, Aurélien Larcher wrote:
>
>Congratulations Gary this is great :)
>If we get to the point that we can setup a build machine this would
>secure your work.

Thanks.  That will be a big help.  I'd recommend weekly builds, rather
than daily builds.  I'm sure that will be adequate.  My build, when
it's completed, will be at least a year behind the current state of
OI.


--
-Gary Mills--refurb--Winnipeg, Manitoba, Canada-

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

[oi-dev] DDU testing

[Alexander Pyhalov via oi-dev]

Hi.

I've finished replacing DDU binaries with binaries from DDU 1.2 and rewriting 
missing parts. 
Result is here: https://github.com/OpenIndiana/ddu/ .
I suggest it can get wider testing.
You can use openindiana/ddu component  from 
https://github.com/OpenIndiana/oi-userland/pull/5103 to build and test it. 

I'm waiting for test results and reviews.

Changes from current DDU (shipped with OI now).
1) pt_BR localization files removed as msgunfmt couldn't unparse them;
2) Database of third-party drivers was removed (it was obsolete  with it seems 
one working link from dozen). I suppose nobody volunteers to support it in 
actual state.
3) I hope finally I've made DDU help behave - now it shows help in user locale, 
images are not removed.
4) I've regenerated database of existing OI drivers shipped with DDU, updated 
pci.ids and usb.ids files.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ


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

Re: [oi-dev] component TODO list for perl components?

[Alexander Pyhalov via oi-dev]

Hi.

I've updated TODO list http://docs.openindiana.org/dev/existing-tasks/ some 
time ago. There are mostly tasks which I'm interested in.

Now I'm looking at removing binary blobs from DDU. Later I'll likely look at 
switching it to Python 3.5.

If you can propose any tasks which you can take (or pehaps, someone else), feel 
 free to update this page. I just don't want it to become a list of never-done 
tasks.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Tim Mooney 
Отправлено: 24 июня 2019 г. 5:24:33
Кому: oi-dev@openindiana.org
Тема: [oi-dev] component TODO list for perl components?


I've been considering packaging the latest stable perl5, 5.30.0, as
perl-530 and then packaging (and in some cases, updating) the perl
modules that are part of hipster, but I want to make certain I'm not
working at cross-purposes to any planned updates for OI and that this
type of update is actually useful.

There's a checklist of small/easy changes to make when updating a
component,


https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/current-tasks.md

but is there a list of the bigger packaging tasks, perhaps prioritized by
need?  Obviously people volunteering their time are going to work on
things that interest them, benefit them, and are within their ability,
but at times it would be helpful to know what the most pressing packaging
needs are.

I'm happy to continue choosing components kind of at random to update, but
if I have a list of easy (but perhaps tedious) packaging tasks that are
priorities for update in OI, I would probably attempt some of them as I
have time, especially if it frees up more time for core contributors to
work on the more difficult tasks.

Does a list like that exist?  Those types of things tend to go stale fast,
so I understand if there isn't one.

Tim
--
Tim Mooney tim.moo...@ndsu.edu
Enterprise Computing & Infrastructure  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

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

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

[oi-dev] Packaging and Delivering Software with the Image Packaging System

[Alexander Pyhalov via oi-dev]

Hi.

Packaging and Delivering Software with the Image Packaging System developes's 
guide has been published to docs.openindiana.org - 
http://docs.openindiana.org/dev/pdf/ips-dev-guide.pdf

It should be mostily identical to Oracle's 
https://docs.oracle.com/cd/E37838_01/html/E61051/index.html, however I've done 
global s/Solaris/OpenIndiana/ and tried to fix some information, unrelevant for 
us.

Best regards, 
Alexander Pyhalov, 
system administrator of Southern Federal University IT department

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

Re: [oi-dev] Image Packaging Developer's Guide

[Alexander Pyhalov via oi-dev]

Created https://github.com/OpenIndiana/pkg5/pull/63
Generated file can be seen here: 
http://buildzone.oi-build.r61.net/dev-guide/book-new.pdf

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Till Wegmüller 
Отправлено: 22 мая 2019 г. 11:34:17
Кому: oi-dev@openindiana.org
Тема: Re: [oi-dev] Image Packaging Developer's Guide

This guide was very helpful in making the Go version of the IPS
Repository server. I would very much like to preserve this.

So +1 for initiating that effort.

As to merging into oi-docs I would like to get the opinion of the Omnios
People about the docs. I don't think it to be wise to diverge IPS
versions between the two illumos distros seing how little manpower we
have. I would thus argue towards a shared documentation in a repository
where both teams work with or regularly update/merge/fork.

Greetings
Till

On 22.05.19 08:53, Alexander Pyhalov via oi-dev wrote:
> Also after fixing a bit more issues, I've got
>
> http://buildzone.oi-build.r61.net/dev-guide/
>
> Looks like real 'Packaging and Delivering Software with the Image Packaging 
> System' guide :)
>
> С уважением,
> Александр Пыхалов,
> программист отдела телекоммуникационной инфраструктуры
> управления информационно-коммуникационной инфраструктуры ЮФУ
>
>
> 
> От: Andreas Wacknitz 
> Отправлено: 22 мая 2019 г. 9:25:34
> Кому: oi-dev@openindiana.org
> Тема: Re: [oi-dev] Image Packaging Developer's Guide
>
> Am 22.05.19 um 06:57 schrieb Michal Nowak:
> On 05/22/19 06:23 AM, Alexander Pyhalov via oi-dev wrote:
> Hi.
>
> We have CDDL-licensed Image Packaging Developer's Guide sources under 
> https://github.com/OpenIndiana/pkg5/tree/oi/doc .
>
> After small changes ( https://github.com/pyhalov/pkg5/tree/dev-guide ) I even 
> could generate http://buildzone.oi-build.r61.net/pkg-guide/ .
>
> I'm just interested, what do you think? Does it worth fixing/supporting this 
> guide in this format or should we just merge relevant information to oi-docs?
>
> Best regards,
> Alexander Pyhalov,
> system administrator of Southern Federal University IT department
>
> Hi,
>
> it looks like interesting documentation. We don't actually have abundance of 
> IPS documentation. I think it should be merged with oi-docs.
>
> Michal
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org<mailto:oi-dev@openindiana.org>
> https://openindiana.org/mailman/listinfo/oi-dev
> +1
>
> Regards,
> Andreas
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>

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

Re: [oi-dev] Image Packaging Developer's Guide

[Alexander Pyhalov via oi-dev]

Also after fixing a bit more issues, I've got

http://buildzone.oi-build.r61.net/dev-guide/

Looks like real 'Packaging and Delivering Software with the Image Packaging 
System' guide :)

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Andreas Wacknitz 
Отправлено: 22 мая 2019 г. 9:25:34
Кому: oi-dev@openindiana.org
Тема: Re: [oi-dev] Image Packaging Developer's Guide

Am 22.05.19 um 06:57 schrieb Michal Nowak:
On 05/22/19 06:23 AM, Alexander Pyhalov via oi-dev wrote:
Hi.

We have CDDL-licensed Image Packaging Developer's Guide sources under 
https://github.com/OpenIndiana/pkg5/tree/oi/doc .

After small changes ( https://github.com/pyhalov/pkg5/tree/dev-guide ) I even 
could generate http://buildzone.oi-build.r61.net/pkg-guide/ .

I'm just interested, what do you think? Does it worth fixing/supporting this 
guide in this format or should we just merge relevant information to oi-docs?

Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department

Hi,

it looks like interesting documentation. We don't actually have abundance of 
IPS documentation. I think it should be merged with oi-docs.

Michal

___
oi-dev mailing list
oi-dev@openindiana.org<mailto:oi-dev@openindiana.org>
https://openindiana.org/mailman/listinfo/oi-dev
+1

Regards,
Andreas

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

[oi-dev] Image Packaging Developer's Guide

[Alexander Pyhalov via oi-dev]

Hi.

We have CDDL-licensed Image Packaging Developer's Guide sources under 
https://github.com/OpenIndiana/pkg5/tree/oi/doc .

After small changes ( https://github.com/pyhalov/pkg5/tree/dev-guide ) I even 
could generate http://buildzone.oi-build.r61.net/pkg-guide/ . 

I'm just interested, what do you think? Does it worth fixing/supporting this 
guide in this format or should we just merge relevant information to oi-docs? 

Best regards, 
Alexander Pyhalov, 
system administrator of Southern Federal University IT department

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

Re: [oi-dev] Importing data from wiki to oi-docs

[Alexander Pyhalov via oi-dev]

Hi.

Look at https://docs.openindiana.org/contrib/getting-started/.
(Likely, you can start reading from 
https://docs.openindiana.org/contrib/getting-started/#install-mkdocs )

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Gary Mills 
Отправлено: 15 мая 2019 г. 22:23:42
Кому: OpenIndiana Developer mailing list
Копия: Alexander Pyhalov
Тема: Re: [oi-dev] Importing data from wiki to oi-docs

On Tue, May 14, 2019 at 03:44:56PM +, Alexander Pyhalov via oi-dev wrote:
>
> I'm asking everyone, creating significant amount of content on wiki
> to look through their pages and - either convert them to markdown,
> update and create corresponding PRs for oi-docs and oi-userland; -
> or mark them as obsolete.

Could you provide instructions on how to do this, for people who
have never created a PR?  Also, how do I locate my pages?


--
-Gary Mills--refurb--Winnipeg, Manitoba, Canada-

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

Re: [oi-dev] Importing data from wiki to oi-docs

[Alexander Pyhalov via oi-dev]

Hi.

I'm asking everyone, creating significant amount of content on wiki to look 
through their pages and
- either convert them to markdown, update and create corresponding PRs for 
oi-docs and oi-userland;
- or mark them as obsolete.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Andreas Wacknitz 
Отправлено: 14 мая 2019 г. 12:29:35
Кому: Alexander Pyhalov via oi-dev
Тема: Re: [oi-dev] Importing data from wiki to oi-docs

Am 14.05.19 um 09:55 schrieb Alexander Pyhalov via oi-dev:

Hi.

I've been looking at updating 'Building oi-userland' oi-docs page.

And found the following isue - we have long top-level menu, which is hard to 
extend (it is splitted in two lines when extended).
Updated mkdocs have third-level menus, which helps with issue.

So I've created two PRs - https://github.com/OpenIndiana/oi-docs/pull/105 and 
https://github.com/OpenIndiana/oi-userland/pull/5006 .

The first one updates oi-docs layout (and brings in information from wiki pate 
'Building oi-userland' to corresponding oi-docs page). The second - updates our 
mkdocs in OI.

Result can be seen here: http://buildzone.oi-build.r61.net/oi-docs/ .

As you can see, theme seems to be changed a bit.

Looking at your comments.
If I receive no negative feedback, I'll push changes tomorrow

Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department


___
oi-dev mailing list
oi-dev@openindiana.org<mailto:oi-dev@openindiana.org>
https://openindiana.org/mailman/listinfo/oi-dev


Hi Aleyander,

looks great but you should consider to also update the copyright notice from 
2016 to 2019.

Best regards,
Andreas

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

[oi-dev] Importing data from wiki to oi-docs

[Alexander Pyhalov via oi-dev]

Hi.

I've been looking at updating 'Building oi-userland' oi-docs page. 

And found the following isue - we have long top-level menu, which is hard to 
extend (it is splitted in two lines when extended). 
Updated mkdocs have third-level menus, which helps with issue.

So I've created two PRs - https://github.com/OpenIndiana/oi-docs/pull/105 and 
https://github.com/OpenIndiana/oi-userland/pull/5006 .

The first one updates oi-docs layout (and brings in information from wiki pate 
'Building oi-userland' to corresponding oi-docs page). The second - updates our 
mkdocs in OI.

Result can be seen here: http://buildzone.oi-build.r61.net/oi-docs/ .

As you can see, theme seems to be changed a bit. 

Looking at your comments. 
If I receive no negative feedback, I'll push changes tomorrow

Best regards, 
Alexander Pyhalov, 
system administrator of Southern Federal University IT department


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

Re: [oi-dev] OI Hipster 2019.04

[Alexander Pyhalov via oi-dev]

Sorry, missed dot in
http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.iso 
link.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Alexander Pyhalov via oi-dev 
Отправлено: 12 мая 2019 г. 10:11:57
Кому: OpenIndiana Developer mailing list
Копия: Alexander Pyhalov
Тема: [oi-dev] OI Hipster 2019.04

Hi.

OI Hipster 2019.04 snapshot is ready.

Images:

http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511iso
http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.usb

http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.iso
http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.usb

http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.iso
http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.usb


SHA 256 checksums are available at ${link}.sha256sum
Signed SHA 256 checksums are available at ${link}.sha256sum.asc
The OpenIndiana Release Engineering key has key id 0x3a021afadbe31887 (
https://sks-keyservers.net/pks/lookup?op=get=0x3A021AFADBE31887 ).

Release notes: http://wiki.openindiana.org/oi/2019.04+Release+notes

Note, we have an issue with Firefox on live image - it can fail to start 
correctly when launched for the first time in memory-constrained  environment. 
After being killed and restarted it behaves more sane.

Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

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

[oi-dev] OI Hipster 2019.04

[Alexander Pyhalov via oi-dev]

Hi.

OI Hipster 2019.04 snapshot is ready.

Images:

http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511iso
http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.usb

http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.iso
http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.usb

http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.iso
http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.usb


SHA 256 checksums are available at ${link}.sha256sum
Signed SHA 256 checksums are available at ${link}.sha256sum.asc
The OpenIndiana Release Engineering key has key id 0x3a021afadbe31887 (
https://sks-keyservers.net/pks/lookup?op=get=0x3A021AFADBE31887 ).

Release notes: http://wiki.openindiana.org/oi/2019.04+Release+notes

Note, we have an issue with Firefox on live image - it can fail to start 
correctly when launched for the first time in memory-constrained  environment. 
After being killed and restarted it behaves more sane.

Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] pulseaudio issues

[Alexander Pyhalov via oi-dev]

Thank you for your work. Can you open GitHub pull request against 
http://github.com/OpenIndiana/oi-userland/ with proposed changes?

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Gary Mills 
Отправлено: 18 апреля 2019 г. 2:32:20
Кому: Alexander Pyhalov
Копия: OpenIndiana Developer mailing list; Udo Grabowski (IMK)
Тема: Re: [oi-dev] pulseaudio issues

On Sun, Apr 07, 2019 at 08:47:17PM -0500, Gary Mills wrote:
>
> Then I tried changing some settings in that GUI application.  When I
> changed Sound theme to `Default', it changed back to `No sounds'.  I
> also tried increasing the output volume.  This display was curious
> because the 100% mark was about 2/3 of the way along the slider.  I
> was able to set it above 100%.  When I checked, the audio had
> disappeared.  Something happened, but I don't know what.  Even when I
> logged out, killed the pulseaudio daemon, and logged in again, I still
> didn't have audio.  So far, I haven't been able to get it back.

I discovered part of the problem.  The commands
usr/lib/pulse/gsettings-helper and its 64-bit equivalent were not
executable.  This omission caused the fork() to succeed but the exec()
to fail in pa_start_child_for_read().  Because there was no logging of
that failure, I was unaware of the problem for some time.  Those
commands read the MATE configuration, in particular the settings in
the Sound Preferences GUI, and pass them on to pulseaudio.  For
example, they are how pulseaudio discovers your volume changes.

I added some code to modules/gsettings/module-gsettings.c that
verifies that the helper command is present and is executable.  This
code solves the visibility problem.  For a temporary fix, I changed
permission on the installed files.  A permanent fix requires appending
`mode=0555' to the two lines of the manifest.

If this bug hasn't already been reported, I'll be happy to file a bug
report and include my patches.


--
-Gary Mills--refurb--Winnipeg, Manitoba, Canada-

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

Re: [oi-dev] Xvnc securitytypes=none and issue #10584

[Alexander Pyhalov via oi-dev]

Hi.

1) securitypes=none should be set as without this Xvnc will ask password set in 
Xvnc global password file.
We don't want this to happen, as lightdm authenticates user, not Xvnc. 

2) current setting works as intended - you can check it yourself.

So, I'd close this bug as invalid. 

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Tim Mooney 
Отправлено: 10 апреля 2019 г. 0:13:48
Кому: oi-dev@openindiana.org
Тема: [oi-dev] Xvnc securitytypes=none and issue #10584


All-

I've been looking at some of the issues in the issue tracker that are
categorized as "bite-size", to see if I could help resolve some of the
easy ones.

In looking at

https://www.illumos.org/issues/10584

Which suggests we should drop the "securitytypes=none" from the commented
Xvnc line in our lightdm.conf, I see that one of our patches specifically
adds that, and also patches the source to include it.

I can provide a patch that alters the existing patch, but I don't
understand the reason for the change in the first place.

It looks like alp and Michal are the only two to have been involved with
that patch (lightdm/patches/17-customize-config.patch).

Can anyone comment on why securitytypes=none is being added?

Tim
--
Tim Mooney tim.moo...@ndsu.edu
Enterprise Computing & Infrastructure  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

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

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

Re: [oi-dev] mate-tweak?

[Alexander Pyhalov via oi-dev]

I don't know how to handle this in Mate theme, but you can create a set of 
dconf settings and import them with dconf - for example see 
https://github.com/OpenIndiana/oi-userland/commit/005fb56930218fbf86686be21f4dca1f5db0bbf3
 . To do more customization to mate-panel we just patch it.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Gordon Ross 
Отправлено: 5 апреля 2019 г. 0:06:22
Кому: OpenIndiana Developer mailing list
Копия: Alexander Pyhalov
Тема: Re: [oi-dev] mate-tweak?

OK, thanks.  I managed to recreate my favorite layout with dragging
things around and deleting the top panel.
Just curious, how hard is it to define a "theme" that does this?  (or
something like that).

On Thu, Apr 4, 2019 at 3:32 AM Alexander Pyhalov via oi-dev
 wrote:
>
> Hi.
> No, we don't ship it. It seems mate-tweak is Ubuntu project, not mate-desktop.
>
> С уважением,
> Александр Пыхалов,
> программист отдела телекоммуникационной инфраструктуры
> управления информационно-коммуникационной инфраструктуры ЮФУ
>
>
> 
> От: Gordon Ross 
> Отправлено: 4 апреля 2019 г. 4:48:12
> Кому: _oi-dev
> Тема: [oi-dev] mate-tweak?
>
> I'm looking for "mate-tweak", which is the recommended way to get a
> single panel on the bottom, or so-called "redmond" theme (according to
> the google search results I see).  Does the OI build of mate have
> "mate-tweak"?  I don't see it.
>
> Thanks!
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev

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

Re: [oi-dev] mate-tweak?

[Alexander Pyhalov via oi-dev]

Hi.
No, we don't ship it. It seems mate-tweak is Ubuntu project, not mate-desktop.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Gordon Ross 
Отправлено: 4 апреля 2019 г. 4:48:12
Кому: _oi-dev
Тема: [oi-dev] mate-tweak?

I'm looking for "mate-tweak", which is the recommended way to get a
single panel on the bottom, or so-called "redmond" theme (according to
the google search results I see).  Does the OI build of mate have
"mate-tweak"?  I don't see it.

Thanks!

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

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

Re: [oi-dev] pulseaudio issues

[Alexander Pyhalov via oi-dev]

It seems reasonable. The issue I see is that our mod_oss is almost a complete 
fork of pulseaudio mod_oss. Solaris somehow manages to use module_oss without 
patches, and I honestly don't understand how this works.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Gary Mills 
Отправлено: 2 апреля 2019 г. 23:05:53
Кому: OpenIndiana Developer mailing list
Копия: Alexander Pyhalov; Udo Grabowski (IMK)
Тема: Re: [oi-dev] pulseaudio issues

On Tue, Apr 02, 2019 at 04:19:29PM +0200, Udo Grabowski (IMK) wrote:
>
> On OI_151a versions this has always been OSS and it worked - so
> if pulse audio only delivers a "Linux version" of OSS this should
> be fixed. Please don't fall back to ancient mod_solaris, that was
> history already ten years ago...

So, the consensus is that I chose the wrong horse to ride.  The
problem begins with the OI Makefile, which contains:

CONFIGURE_OPTIONS += --enable-oss-output
CONFIGURE_OPTIONS += --enable-solaris

It indirectly enables two output modules.  These options only set two
preprocessor variables: HAVE_OSS_OUTPUT and HAVE_SOLARIS,
respectively.  It's module-detect.c that first uses these variables.
That module calls both detect_oss() and detect_solaris() to determine
the device names.  detect_oss() always fails because of an error
reading the status device.  detect_solaris() succeeds by setting the
device name to the contents of AUDIODEV or to /dev/audio if it's
empty.  It loads module-solaris as the active output module.

I'm willing to fix module-detect.c so that it determines the device
name correctly on illumos/OI and that it loads module-oss instead.  I
can test module-oss on a system with one audio device, and on one that
has two devices.  The first change will have to be the OI Makefile, of
course.  No doubt there will be changes to module-oss as well.  Is
that what people want?  There's no simple solution.


--
-Gary Mills--refurb--Winnipeg, Manitoba, Canada-

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

Re: [oi-dev] pulseaudio issues

[Alexander Pyhalov via oi-dev]

I've looked through libmatemixer and pulseaudio sources once again to recollect 
exact issue. Now I see, the original issue is the following: mod_solaris 
doesn't have means to set device volume (it gets volume via AUDIO_GETINFO 
sysctl, and this has no any relation to real audioctl volume setting, 
controlled via /dev/mixer.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Alexander Pyhalov via oi-dev 
Отправлено: 2 апреля 2019 г. 13:54:25
Кому: Gary Mills
Копия: Alexander Pyhalov; OpenIndiana Developer mailing list
Тема: Re: [oi-dev] pulseaudio issues

If selection of device in mate-volume-control works for you, we can just make 
it honor AUDIODEV is it set.

Your patches make pulseaudio use mod_solaris module, and it doesn't provide 
interfaces necessary to select device in mate-volume-control. So we either fix 
mod_solaris to support these interfaces or fix our mod_oss patches to honor 
AUDIODEV.
Sorry, I don't remember details about what interfaces are needed, but one 
should start digging from libmatemixer pulse backend.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Gary Mills 
Отправлено: 1 апреля 2019 г. 20:54:29
Кому: Alexander Pyhalov
Копия: OpenIndiana Developer mailing list
Тема: Re: pulseaudio issues

On Mon, Apr 01, 2019 at 08:04:00AM +, Alexander Pyhalov wrote:

> Gary, I've opened
> https://github.com/OpenIndiana/oi-userland/pull/4922 to discuss your
> proposed changes to pulseaudio.

Thanks.  That will help.

> I honestly don't understand them. I mean, if we accept these
> changes, what use do we have from mod_oss (and our giant patch to
> it)?

My changes are in addition to that patch and modify the same file.

> I've resurrected this patch from JDS when understood that
> current mod_solaris have no means to enumerate and select audio
> devices and just uses AUDIODEV (or /dev/audio). How user is supposed
> to change audio device?

It is possible to enumerate audio devices.  They are all called
/dev/sound/[0-9], where the number is the instance number.  The other
devices have that number embedded in the name.  /dev/audio is simply a
symlink to /dev/sound/0 .

That's the way to select them, with the AUDIODEV environment variable.
It's explained in two existing man pages.  audio(7i) says this:

   Because some systems may contain more than one audio device,
   application writers are encouraged to query the AUDIODEV environment
   variable. If this variable is present in the environment, its value
   should identify the path name of the default audio device.

audioctl(1) says:

   AUDIODEV
   The full path name of the default audio device to use if
   one is not specified on the command line.  If this variable
   is not set, /dev/audio is used.

The login GUI sources several files to set the environment for
application GUIs.  The .profile file is the usual place for the user
to set environment variables.


--
-Gary Mills--refurb--Winnipeg, Manitoba, Canada-

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

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

Re: [oi-dev] pulseaudio issues

[Alexander Pyhalov via oi-dev]

If selection of device in mate-volume-control works for you, we can just make 
it honor AUDIODEV is it set.

Your patches make pulseaudio use mod_solaris module, and it doesn't provide 
interfaces necessary to select device in mate-volume-control. So we either fix 
mod_solaris to support these interfaces or fix our mod_oss patches to honor 
AUDIODEV.
Sorry, I don't remember details about what interfaces are needed, but one 
should start digging from libmatemixer pulse backend.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Gary Mills 
Отправлено: 1 апреля 2019 г. 20:54:29
Кому: Alexander Pyhalov
Копия: OpenIndiana Developer mailing list
Тема: Re: pulseaudio issues

On Mon, Apr 01, 2019 at 08:04:00AM +, Alexander Pyhalov wrote:

> Gary, I've opened
> https://github.com/OpenIndiana/oi-userland/pull/4922 to discuss your
> proposed changes to pulseaudio.

Thanks.  That will help.

> I honestly don't understand them. I mean, if we accept these
> changes, what use do we have from mod_oss (and our giant patch to
> it)?

My changes are in addition to that patch and modify the same file.

> I've resurrected this patch from JDS when understood that
> current mod_solaris have no means to enumerate and select audio
> devices and just uses AUDIODEV (or /dev/audio). How user is supposed
> to change audio device?

It is possible to enumerate audio devices.  They are all called
/dev/sound/[0-9], where the number is the instance number.  The other
devices have that number embedded in the name.  /dev/audio is simply a
symlink to /dev/sound/0 .

That's the way to select them, with the AUDIODEV environment variable.
It's explained in two existing man pages.  audio(7i) says this:

   Because some systems may contain more than one audio device,
   application writers are encouraged to query the AUDIODEV environment
   variable. If this variable is present in the environment, its value
   should identify the path name of the default audio device.

audioctl(1) says:

   AUDIODEV
   The full path name of the default audio device to use if
   one is not specified on the command line.  If this variable
   is not set, /dev/audio is used.

The login GUI sources several files to set the environment for
application GUIs.  The .profile file is the usual place for the user
to set environment variables.


--
-Gary Mills--refurb--Winnipeg, Manitoba, Canada-

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

[oi-dev] pulseaudio issues

[Alexander Pyhalov]

Hi.

Gary, I've opened https://github.com/OpenIndiana/oi-userland/pull/4922 to 
discuss your proposed changes to pulseaudio.
I honestly don't understand them. I mean, if we accept these changes, what use 
do we have from mod_oss (and our giant patch to it)? I've resurrected this 
patch from JDS when understood that current mod_solaris have no means to 
enumerate and select audio devices and just uses AUDIODEV (or /dev/audio). How 
user is supposed to change audio device?

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ


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

Re: [oi-dev] OpenVPN in a local zone

[Alexander Pyhalov via oi-dev]

Hi.
I suppose some of the privileges mentioned in 
/lib/svc/manifest/network/openvpn.xml are not available in zone (look at 
method_credential section).

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Sven Schmeling 
Отправлено: 18 января 2019 г. 23:36:17
Кому: OpenIndiana Developer mailing
Тема: [oi-dev] OpenVPN in a local zone

Hello,

i have installed OpenVPN in a local zone.

Starting the service with "svcadm enable svc:/network/openvpn:default"
(or rebooting the zone) ends in the maintenance mode:

# svcs openvpn
STATE  STIMEFMRI
maintenance19:46:37 svc:/network/openvpn:default

cat /var/svc/log/network-openvpn:default.log

[ Jan 18 19:46:37 Enabled. ]
[ Jan 18 19:46:37 Executing start method ("/usr/sbin/openvpn --daemon
openvpn --config '/etc/openvpn/openvpn.conf'"). ]
[ Jan 18 19:46:37 svc.startd could not set context for method:  ]
setppriv: Not owner
[ Jan 18 19:46:37 Method "start" exited with status 96. ]

Hints to add "limitpriv="default,priv_net_rawaccess" to the zone config
are maded but doesn't change the behavior.

Starting openvpn with "/usr/sbin/openvpn --verb 9 --config
'/etc/openvpn/openvpn.conf'" on the command line works fine and
connections are possible.


Any hints about the "setppriv" error?

--

pkg info openvpn
Name: network/openvpn
Summary: OpenVPN is a full-featured open source SSL VPN solution
Category: Applications/Internet
State: Installed
Publisher: openindiana.org
Version: 2.4.3
Branch: 2018.0.0.1
Packaging Date: Sun Feb 11 13:19:38 2018
Size: 1.19 MB
FMRI:
pkg://openindiana.org/network/openvpn@2.4.3-2018.0.0.1:20180211T131938Z
Project URL: http://openvpn.net
Source URL:
http://swupdate.openvpn.org/community/releases/openvpn-2.4.3.tar.xz

--

Thanks

Sven Schmeling


- --
Sven Schmeling, Oldenburg, Germany
mailto:sven.schmel...@schmeling-ol.de





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

[oi-dev] Virtualbox additions

[Alexander Pyhalov via oi-dev]

Hello.
I'm asking for some kind of review and testing.

I've created several PRs:
https://github.com/OpenIndiana/oi-userland/pull/4637 - Adds virtualbox additions
https://github.com/OpenIndiana/oi-userland/pull/4660 - Allows using swrast with 
virtualbox-provided libGL
https://github.com/OpenIndiana/oi-userland/pull/4664 - Facilitates testing 
virtualbox GL libraries, as they are  64-bit only

Long story short.

VirtualBox guest additions (especially, swrast acceleration)  have always 
worked on OI by chance (or due to some series of bugs).
First of all, /lib/opengl/ogl_vendor_select tried to create links in wrong 
directory /system/volatile/opengl , so script efficiently didn't work.
If we fix this, we find out that Mesa swrast driver is not loaded due to 
missing link to libglapi, which was earlier taken from mesa libGL.so (now it's 
replaced with VirtualBox).

Later, if we fix Mesa and link dri drivers to libglapi, mesa libGL will not 
work , as our build system will consider libGL.so->libglapi.so link 
unnecessary, so we should avoid -Bdirect -z ignore.

Now, we have more-or-less working VirtualBox GL libraries for 64-bit apps, but 
we don't ship 32-bit guest additions, so we use Mesa libraries for 32-bit apps. 
GLXgears seems to be happy with 64-bit libGL from VirtualBox (to test it I had 
to add 64-bit glxgears version), but compiz is not, as virtualbox libraries 
don't set GLX visuals for depth 32 (don't know why)).
So, I've decided to avoid enabling virtualbox GL libraries by default. User can 
explicitly enable them by setting ogl-select service options/vendor property to 
"vbox". 

Happy testing.


Best regards, 
Alexander Pyhalov, 
system administrator of Southern Federal University IT department


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

[oi-dev] iconv_en_US.UTF-8.5 man page source

[Alexander Pyhalov via oi-dev]

Hello.

Does someone remember/know where iconv_en_US.UTF-8.5 man page source is 
obtained from. Looking at OI g11n gate I see that it was extracted from 
original opensolaris package. Do we have a CDDL source for it to include in 
illumos-gate?

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ


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

[oi-dev] OI Hipster 2018.10 snapshot

[Alexander Pyhalov via oi-dev]

Hi.

OI Hipster 2018.10 snapshot is ready.

Images:

http://dlc.openindiana.org/isos/hipster/20181023/OI-hipster-gui-20181023.iso
http://dlc.openindiana.org/isos/hipster/20181023/OI-hipster-gui-20181023.usb

http://dlc.openindiana.org/isos/hipster/20181023/OI-hipster-text-20181023.iso
http://dlc.openindiana.org/isos/hipster/20181023/OI-hipster-text-20181023.usb

http://dlc.openindiana.org/isos/hipster/20181023/OI-hipster-minimal-20181023.iso
http://dlc.openindiana.org/isos/hipster/20181023/OI-hipster-minimal-20181023.usb


SHA 256 checksums are available at ${link}.sha256sum
Signed SHA 256 checksums are available at ${link}.sha256sum.asc
The OpenIndiana Release Engineering key has key id 0x3a021afadbe31887 (
https://sks-keyservers.net/pks/lookup?op=get=0x3A021AFADBE31887 ).

Release notes: http://wiki.openindiana.org/oi/2018.10+Release+notes

Best regards, 
Alexander Pyhalov, 
system administrator of Southern Federal University IT department

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

Re: [oi-dev] Tag for 2018.10 ?

[Alexander Pyhalov via oi-dev]

You will likely be able to update to osnet-incorporation@version1, 
userland-incorporation@version2. Have to check.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Udo Grabowski (IMK) 
Отправлено: 22 октября 2018 г. 17:26:27
Кому: Alexander Pyhalov; OpenIndiana Developer mailing list
Тема: Re: [oi-dev] Tag for 2018.10 ?

On 22/10/2018 16:06, Alexander Pyhalov wrote:
> No, there will not be any repository-level tag.
>
> And why one could need it with our development model? However, I'll create 
> git tags for oi-userland, slim_source and pkg5 repositories.
>

I can imagine people not updating their production servers
everyday (for me: I hate updates...), but hopping from one
major tag to the next. And they clearly won't reinstall from
ISO...so there should be a way to get an update from, say,
2018.04 to 2018.10 on the development line. Although I'm
currently following the development line on a weekly basis
to produce a new stable image for our whole cluster, I would
like to have an update where I can tell that I get exactly what's
on the ISO (and therefore, what corresponds to the git tags).

So if there are no separate publishers, at least there should be
a short period of days where the package server stays on the major
tag so that people can synchronize and snapshot.


> С уважением,
> Александр Пыхалов,
> программист отдела телекоммуникационной инфраструктуры
> управления информационно-коммуникационной инфраструктуры ЮФУ
>
>
> 
> От: Udo Grabowski (IMK) 
> Отправлено: 22 октября 2018 г. 16:43:16
> Кому: Alexander Pyhalov; OpenIndiana Developer mailing list
> Тема: Re: [oi-dev] Tag for 2018.10 ?
>
> On 22/10/2018 15:35, Alexander Pyhalov via oi-dev wrote:
>> What do you mean by 'tag'?
>>
>
> I faintly remember that there were separate publishers
> for those "kind-of-release" versions, so that, by changing
> to that publisher, you got the "fixed" version and could
> update from an earlier release to that.
>
> A real tagging mechanism ' pkg update -tag "2018.10" ' may
> be something worth thinking about for the future. In principle,
> that would be possible today by specifiying entire@201810xx as
> install target ?
>
>> 
>> От: Udo Grabowski (IMK) 
>> Отправлено: 22 октября 2018 г. 15:37:26
>> Кому: oi-dev@openindiana.org
>> Тема: [oi-dev] Tag for 2018.10 ?
>>
>> Hi,
>> for those who are on continous Hipster update currently: Will
>> there be a tag we can update to from any state before to 2018.10 ?
--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026


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

Re: [oi-dev] Tag for 2018.10 ?

[Alexander Pyhalov via oi-dev]

What do you mean by 'tag'?

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Udo Grabowski (IMK) 
Отправлено: 22 октября 2018 г. 15:37:26
Кому: oi-dev@openindiana.org
Тема: [oi-dev] Tag for 2018.10 ?

Hi,
for those who are on continous Hipster update currently: Will
there be a tag we can update to from any state before to 2018.10 ?
--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026


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

Re: [oi-dev] libgee

[Alexander Pyhalov via oi-dev]

Build server has library/desktop/libgee installed.

https://github.com/OpenIndiana/oi-userland/commit/72d3312f48d8ef0b790f2227f8379a9fdb1c51e0#diff-6c38b4e552dbf289b7c09e0741fe00e3

has broken it.
We should add library/libgee to history and use proper FMRI.
Will you handle this?

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Andreas Wacknitz 
Отправлено: 22 октября 2018 г. 10:45:05
Кому: OpenIndiana Developer mailing list
Тема: [oi-dev] libgee

Hi,

I just noticed that we provide two versions of libgee:
  1. library/desktop/libgee  (0.8.6)
  2. library/libgee (0.20.1)

Do we really need both? If so, which one should be installed on a build server?
They have conflicting actions...

Regards,
Andreas

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

Re: [oi-dev] openal repository

[Alexander Pyhalov via oi-dev]

Should be fixed in https://github.com/OpenIndiana/oi-userland/pull/4531

Thanks for reporting.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Rich Reynolds 
Отправлено: 17 октября 2018 г. 20:32:34
Кому: oi-dev@openindiana.org
Тема: Re: [oi-dev] openal repository

repeated fetches for openal with most recent userland pull give the
following error:

...
odd1@userlandbuild:/codebase/oi-userland/components/multimedia/openal$
gmake download
/codebase/oi-userland/tools/userland-fetch  --file
/codebase/oi-userland/archives/openal-soft-1.16.0.tar.bz2 --url
http://kcat.strangesoft.net/openal-releases/openal-soft-1.16.0.tar.bz2
--hash
sha256:2f3dcd313fe26391284fbf8596863723f99c65d6c6846dccb48e79cadaf40d5f
Source /codebase/oi-userland/archives/openal-soft-1.16.0.tar.bz2... not
found, skipping file copy
Source
http://kcat.strangesoft.net/openal-releases/openal-soft-1.16.0.tar.bz2...
 downloading...
Traceback (most recent call last):
   File "/codebase/oi-userland/tools/userland-fetch", line 481, in 
 main()
   File "/codebase/oi-userland/tools/userland-fetch", line 403, in main
 for name in download_from_paths(search_list, file_arg, url_arg,
link_arg):
   File "/codebase/oi-userland/tools/userland-fetch", line 341, in
download_from_paths
 name = download(url, file_arg, quiet)
   File "/codebase/oi-userland/tools/userland-fetch", line 172, in download
 src = urlopen(req)
   File "/usr/lib/python2.7/urllib2.py", line 154, in urlopen
 return opener.open(url, data, timeout)
   File "/usr/lib/python2.7/urllib2.py", line 429, in open
 response = self._open(req, data)
   File "/usr/lib/python2.7/urllib2.py", line 447, in _open
 '_open', req)
   File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain
 result = func(*args)
   File "/usr/lib/python2.7/urllib2.py", line 1228, in http_open
 return self.do_open(httplib.HTTPConnection, req)
   File "/usr/lib/python2.7/urllib2.py", line 1201, in do_open
 r = h.getresponse(buffering=True)
   File "/usr/lib/python2.7/httplib.py", line 1121, in getresponse
 response.begin()
   File "/usr/lib/python2.7/httplib.py", line 438, in begin
 version, status, reason = self._read_status()
   File "/usr/lib/python2.7/httplib.py", line 402, in _read_status
 raise BadStatusLine(line)
httplib.BadStatusLine: ''
gmake: *** [/codebase/oi-userland/make-rules/prep-download.mk:76:
/codebase/oi-userland/archives/openal-soft-1.16.0.tar.bz2] Error 1
...
poking around kcat.strangesoft.net shows a copyright notice and not much
else

browsing about in
http://dlc.openindiana.org/oi-userland/source-archives/ give me a page
that starts with:
...
MNG (Multiple-image Network Graphics) Format Version 1.0

For list of authors, see Credits (Chapter 19).
Status of this Memo

This document is a specification by the PNG development group. It has
been approved by a vote of the group. Future technical changes will
require formal approval by a vote of the group. It is the intent of the
group to maintain backward compatibility if possible.

...
so hunting lower is hunting blind

but even blind hunters occasionally hit some thing:

dlc.openindiana.org/oi-userland/source-archives/openal-soft-1.16.0.tar.bz2
seems to be fetchable  and the hash was good.

rich

On 10/17/2018 10:24 AM, Alexander Pyhalov via oi-dev wrote:
> What do you mean?
> Sources at http://dlc.openindiana.org/oi-userland/source-archives/ are 
> archive copies, which are resynced from build server. So if build server has 
> fetched source successfully, it'll be available for oi-userland (it uses dlc 
> archive mirror as last resort).
>
> С уважением,
> Александр Пыхалов,
> программист отдела телекоммуникационной инфраструктуры
> управления информационно-коммуникационной инфраструктуры ЮФУ
>
>
> 
> От: Rich Reynolds 
> Отправлено: 17 октября 2018 г. 19:06:56
> Кому: oi-dev@openindiana.org
> Тема: [oi-dev] openal repository
>
>
> the openal repository has given me 10 failed fetches over 24 hours
> didnt see one in dlc   got another source home?
>
> rich
> --
> The first rule of propaganda is that if you repeat something enough
> times people will start to believe it, no matter how false.
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>


--
The first rule of propaganda is that if you repeat something enough
times people will star

Re: [oi-dev] openal repository

[Alexander Pyhalov via oi-dev]

What do you mean?
Sources at http://dlc.openindiana.org/oi-userland/source-archives/ are archive 
copies, which are resynced from build server. So if build server has fetched 
source successfully, it'll be available for oi-userland (it uses dlc archive 
mirror as last resort).

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Rich Reynolds 
Отправлено: 17 октября 2018 г. 19:06:56
Кому: oi-dev@openindiana.org
Тема: [oi-dev] openal repository


the openal repository has given me 10 failed fetches over 24 hours
didnt see one in dlc   got another source home?

rich
--
The first rule of propaganda is that if you repeat something enough
times people will start to believe it, no matter how false.

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

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

Re: [oi-dev] mate-system-monitor 1.20.1 dumps core

[Alexander Pyhalov via oi-dev]

Hi.
So far I haven't catched this error on my systems. Can you recompile it with 
-O0 -ggdb and show stack trace once again?

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Aurélien Larcher 
Отправлено: 14 октября 2018 г. 19:14:59
Кому: OpenIndiana Developer mailing list
Тема: Re: [oi-dev] mate-system-monitor 1.20.1 dumps core



did you updated everything to the latest hipster (including MATE themes,
Nimbus, and GTK+ 3.24.1)?
Yes everything is updated to latest:

phainos> LANG=C pkg info gtk3
 Name: library/desktop/gtk3
  Summary: GTK+ - GIMP Toolkit Library for creation of graphical user
   interfaces
 Category: Desktop (GNOME)/Libraries
State: Installed
Publisher: userland
  Version: 3.24.1
   Branch: 2018.0.0.0
   Packaging Date: Sun Oct 14 06:03:10 2018
Last Install Time: Sun Oct 14 14:47:33 2018
 Size: 87.19 MB
 FMRI: 
pkg://userland/library/desktop/gtk3@3.24.1-2018.0.0.0:20181014T060310Z
  Project URL: https://www.gtk.org/
   Source URL: 
http://ftp.gnome.org/pub/GNOME/sources/gtk+/3.24/gtk+-3.24.1.tar.xz


> (gdb) bt
> Python Exception  long too big to convert:
> Python Exception  long too big to convert:
> Python Exception  long too big to convert:
> Python Exception  long too big to convert:

I guess this is a GDB pretty-printer error?

> #0  0x in _free_unlocked ()#1  0x in
> free ()#2  0x in
> Glib::Container_Helpers::ArrayKeeper
>  >::~ArrayKeeper() ()#3  0x in
> Gtk::IconTheme::set_search_path(std::vector std::allocator > const&) [clone .cold.74] ()#4
> 0x004445e9 in procman::IconThemeWrapper::load_icon(Glib::ustring
> const&, int, Gtk::IconLookupFlags) const ()
> #5  0x0042e4cc in PrettyTable::get_icon_from_theme(ProcInfo
> const&) ()
> #6  0x0042efdf in PrettyTable::set_icon(ProcInfo&) ()

Do you use some custom pre-MATE 1.20 theme? Can you try with some stock
MATE 1.20 or Nimbus theme?

I use stock Nimbus theme.


Is there some relevant error output from mate-system-monitor other than
deprecation warnings wrt gtk-widgets.css?

Nothing aside from deprecations in the css.


Michal

> #7  0x00429e33 in insert_info_to_tree(ProcInfo*, ProcData*,
> bool) [clone .constprop.206] ()
> #8  0x0042c448 in proctable_update_list(ProcData*) ()
> #9  0x0042d1fa in proctable_update(ProcData*) ()
> #10 0x00425d88 in cb_switch_page(_GtkNotebook*, _GtkWidget*,
> int, void*) ()
> #14 0x in  [GtkNotebook]> (instance=, signal_id=,
> detail=)
>  at gsignal.c:3447
>  #11 0x in g_closure_invoke (closure=0x89cb60,
> return_value=0x0, n_param_values=3, param_values=0xfd7fffdfee30,
> invocation_hint=0xfd7fffdfedd0) at gclosure.c:806
>  #12 0x in signal_emit_unlocked_R
> (node=node@entry=0x4e43f0, detail=detail@entry=0,
> instance=instance@entry=0x77a240,
> emission_return=emission_return@entry=0x0,
> instance_and_params=instance_and_params@entry=0xfd7fffdf---Type
>  to continue, or q  to quit---
> ee30) at gsignal.c:3635
>  #13 0x in g_signal_emit_valist (instance= out>, signal_id=, detail=,
> var_args=var_args@entry=0xfd7fffdfefe8) at gsignal.c:3391
> Python Exception  long too big to convert:
> Python Exception  long too big to convert:
> #15 0x in gtk_notebook_button_press ()#16
> 0x in _gtk_marshal_BOOLEAN__BOXEDv ()#17
> 0x in _g_closure_invoke_va (closure=0x468950,
> return_value=0xfd7fffdff2a0, instance=0x77a240,
> args=0xfd7fffdff398, n_params=1, param_types=0x49a2b0) at gclosure.c:869
> #18 0x in g_signal_emit_valist (instance=0x77a240,
> signal_id=, detail=,
> var_args=var_args@entry=0xfd7fffdff398) at gsignal.c:3300
> #19 0x in g_signal_emit (instance=,
> signal_id=, detail=) at gsignal.c:3447
> Python Exception  long too big to convert:
> Python Exception  long too big to convert:
> Python Exception  long too big to convert:
> Python Exception  long too big to convert:
> Python Exception  long too big to convert:
> #20 0x in gtk_widget_event_internal ()#21
> 0x in propagate_event ()#22 0x in
> gtk_main_do_event ()#23 0x in _gdk_event_emit ()#24
> 0x in gdk_event_source_dispatch ()#25 0x
> in g_main_context_dispatch (context=0x4b79e0)
>  at gmain.c:3177
> #26 0x in g_main_context_dispatch
> (context=context@entry=0x4b79e0) at gmain.c:3830
> #27 0x in g_main_context_iterate (context=0x4b79e0,
> block=block@entry=1, dispatch=dispatch@entry=1, self=) at
> gmain.c:3903
> #28 0x in g_main_loop_run 

Re: [oi-dev] Git dependency to

[Alexander Pyhalov via oi-dev]

Hi.
It's part of g11n. These are illumos-specific iconv libraries for converting 
files between characterr sets. Something should go very wrong for git to get 
dependency on them.

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Aurélien Larcher 
Отправлено: 28 сентября 2018 г. 14:00:19
Кому: OpenIndiana Developer mailing list
Тема: [oi-dev] Git dependency to

Hi,
latest git component failed to publish in the gcc-8 build zone since it depends 
on /system/library/iconv/extra.

A quick check shows that

system/library/iconv/extra@0.5.11,5.11-2013.0.0.0:20151027T075807Z

is one of those package that have not been migrated to oi-userland.

Any idea where it is located or whether this dependency is actually required at 
all?
The only missing file in the workspace is 
'/usr/share/man/man1/git-commit-graph.1'

Aurélien
--
---
Praise the Caffeine embeddings
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] 2018.10 targets

[Alexander Pyhalov via oi-dev]

Hi, folks.

We are approaching October.
While I have limited time now, I want to coordinate priorities and targets, 
what should we do till end of October (and due to personal reasons, I'd better 
announce snapshot till 20 October or earlier or allow someone else to do this).

We have several regressions and problems, which would be good to fix.

1) Virtualbox failure after FPU changes https://www.illumos.org/issues/9761 , 
https://www.virtualbox.org/ticket/17947 is a serious one, but I'm afraid I lack 
skills to fix it in reasonable time. The stack trace itself doesn't seem 
related to illumos-gate changes, but likely it is. In KVM Joyent fixed this 
using new hma_fpu_* API, but Virtualbox structures to store VM registers differ 
and from brief overlook it has several asm functions to store/restore Host/Base 
registers state. So far I don't have an idea how convert one to another. So, 
this likely will be broken in 2018.10 unless someone skillful dig into this.

2) sbcl issues - threaded sbcl can not be built after KPTI changes, it fails 
FLOCK and posix tests. Needs investigation. It's a serious issue, because 
threaded sbcl is needed to build pgloader.

3) Our Mate is a bit old, but newer Mate requires updated GTK3 .  Updated GTK3 
IIRC has dropped support for theme engines, and so our Nimbus theme based on 
unico engine doesn't work. Also I've heard there were issues with new 
mate-terminal. 
Michal, do you have some comments here?

4) As for new features, I really want to see KVM zones, perhaps, I'll dig into 
this shortly.

Does somebody have another targets/comments? 

Please, avoid turning this topic in bike-shedding, I want to hear OI developers 
in a way "I ll take item #N" or "I expect to finish feature A before snapshot", 
not "please, also fix this and that". 

Best regards, 
Alexander Pyhalov, 
system administrator of Southern Federal University IT department



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

Re: [oi-dev] Whitespace in Makefiles in oi-userland keep causing Problems

[Alexander Pyhalov via oi-dev]

Does
COMPONENT_CLASSIFICATION=   System/Administration and Configuration
work?

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Till Wegmüller 
Отправлено: 27 сентября 2018 г. 22:03:14
Кому: OpenIndiana Developer mailing list
Тема: [oi-dev] Whitespace in Makefiles in oi-userland keep causing  Problems

Hello Fellow developers.

I have a confusing Problem with our buildsystem.
Since today it keeps behaving Inconsistently when I have a Whitespace in
a Value of a variable.

A Makefile like so:


COMPONENT_NAME=salt
COMPONENT_VERSION=2018.3.2
COMPONENT_SUMMARY='Portable, distributed, remote execution and
configuration management system'
COMPONENT_PROJECT_URL=http://saltstack.com
COMPONENT_FMRI=system/management/$(COMPONENT_NAME)
COMPONENT_CLASSIFICATION='System/Administration and Configuration'


Something like COMPONENT_CLASSIFICATION would break pkgmogrify with:
pkgmogrify: File
/export/home/toast/workspace/openindiana/userland/components/python/salt/build/manifest-i386-salt-27.p5m
line 18: Malformed action at position: 90: whitespace in key:
set name=info.classification
value=org.opensolaris.category.2008:System/Administration and Configuration

I could manage to supress this by using escape characters like " or '.
But not in all cases. And with the Classification the Whitespaces are
required as that Category has Whitespaces in their name. Thus it won't
publish.

I remember that Whitespaces where no problem not long ago. How will we
handle this? Packages like puppet and many others have also Whitespaces
in the Makefiles.

Greetings
Till

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

[oi-dev] HEADS UP: distro const doesn't longer create 32-bit boot archive

[Alexander Pyhalov via oi-dev]

Hi.

With integration of https://github.com/OpenIndiana/slim_source/pull/45 
distro_const doesn't longer create 32-bit boot archive nor support stripping 
them. GUI and text installer were updated to cope with this. If you use custom 
distro_const manifests, be sure to remove 

Re: [oi-dev] [developer] Re: open-vm-tools works great!

[Alexander Pyhalov via oi-dev]

On Mon, Sep 24, 2018 at 9:24 AM Gordon Ross  wrote:
>
> Thanks again for the help with building and packaging the desktop
> parts of the open-vm-tools.
> I recently had reason to setup an OI VM under vmware fusion (on the
> Mac) and once I loaded that package, resize works, copy/paste works
> between the guest and the host.  (I love it when stuff "just works"!
> :)
>
> BTW, vmware fusion on this mac was about 5 times faster than virtualbox.
> Yeah, not free, but definitely worth the $80 in my case.
> (Oh, and a little "pro tip": one can edit the VM *.vmx file and change
> ethernet0.virtualDev from e1000 to vmxnet3 for better network performance.)
>
> Oh yeah, a question:  Should that package have installed automatically
> when I installed the VM? Or maybe when I updated?  I had to run "pkg
> install ..." to get it.

Hi.
I'm not sure, if it should come with server image, but it likely should be 
present with Mate image. 

If we consider that it's not needed on server, we have to add it to 
https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/components/meta-packages/install-types/includes/desktop_common
 
else it should go to
https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/components/meta-packages/install-types/includes/server_desktop
 
I'm sure it shouldn't be present in "minimal" or "core".

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ

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

Re: [oi-dev] How to kill old sfe package meta-data?

[Alexander Pyhalov via oi-dev]

От: Till Wegmüller 
Отправлено: 31 августа 2018 г. 0:43
Кому: oi-dev@openindiana.org
Тема: Re: [oi-dev] How to kill old sfe package meta-data?

> Hrmm ips does aparently not keep any Manifests locally. Which is not
> nice. One would assume that IPS would keep more data in it's sate
> database. Considering it always tries to ensure the system is in a
> specific state.


Hi. This is not true. 
When you do pkg unset-publisher, you can see at 
https://github.com/OpenIndiana/pkg5/blob/oi/src/modules/client/image.py#L3391 
that pkg builds a list of manifests to keep and doesn't remove them.

Gordon, does /var/pkg/publisher/sfe/pkg/ contain manifests of installed 
packages?

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

[oi-dev] VirtualBox and recent illumos-gate

[Alexander Pyhalov via oi-dev]

Recent illumos-gate changes have broken KVM and VirtualBox. 
Issue: https://www.illumos.org/issues/9761. 

Note, that we've never delivered VirtualBox for OI and Solaris binaries just 
worked. Now it's no longer a case, and VirtualBox kernel modules should be 
patched. Well, I don't have enough skills (and perhaps even more important - 
free time) to do this, so any help would be appreciated...

Best regards, 
Alexander Pyhalov, 
system administrator of Southern Federal University IT department


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

Re: [oi-dev] hwloc ABI incompatible update

[Alexander Pyhalov]

On 05/22/18 03:44 PM, Aurélien Larcher wrote:

Hi,
hwloc was updated to 2.x and requires recompilation of dependent code.
If you use parallel numerical libraries like PETSc you are affected by the
update.
Kind regards


Hi. Please, add a note about this to 
https://wiki.openindiana.org/oi/oi_hipster .



--
Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department

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

[oi-dev] OI Hipster 2018.04 snapshot

[Alexander Pyhalov]

Hi.

OI Hipster 2018.04 snapshot is ready.

Images:

http://dlc.openindiana.org/isos/hipster/20180427/OI-hipster-gui-20180427.iso
http://dlc.openindiana.org/isos/hipster/20180427/OI-hipster-gui-20180427.usb

http://dlc.openindiana.org/isos/hipster/20180427/OI-hipster-text-20180427.iso
http://dlc.openindiana.org/isos/hipster/20180427/OI-hipster-text-20180427.usb

http://dlc.openindiana.org/isos/hipster/20180427/OI-hipster-minimal-20180427.iso
http://dlc.openindiana.org/isos/hipster/20180427/OI-hipster-minimal-20180427.usb


SHA 256 checksums are available at ${link}.sha256sum
Signed SHA 256 checksums are available at ${link}.sha256sum.asc
The OpenIndiana Release Engineering key has key id 0x3a021afadbe31887 ( 
https://sks-keyservers.net/pks/lookup?op=get=0x3A021AFADBE31887 ).


Release notes: http://wiki.openindiana.org/oi/2018.04+Release+notes


--
Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department

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

Re: [oi-dev] Silent upgrade failure when using ONU to upgrade OI from illumos-gate nightly build

[Alexander Pyhalov]

On 02/26/18 08:48 PM, Prakash Surya wrote:

Hi,

I'm having a problem using ONU to upgrade an OI Hipster system to a nightly
build of the illumos-gate. Basically, after I upgrade via ONU and reboot,
the system is running the new BE, but the new kernel (and other packages)
aren't running (i.e. they're not part of the new BE).

I'm guessing this is a result of how I'm setting the PKGVERS_BRANCH
illumos.sh variable, where I set it like so:

PKGVERS_BRANCH=$(pkg info -r pkg://openindiana.org/SUNWcs | awk '$1 ==
"Branch:" {print $2}')

Is this how I should be setting this variable? How do others upgrade OI to
a nightly build of illumos-gate?


Hi.
I usually set PKGVERS_BRACNH to RELEASE_MAJOR.RELEASE_MINOR+1.0.0 (where 
RELEASE_MAJOR and RELEASE_MINOR matches OI versions). To find out what 
is going on, it would be interesting to see the output of pkg update -vv 
osnet-incorporation@YOUR_VERSION.




--
Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department

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

[oi-dev] GCC 6 switch

[Alexander Pyhalov]

Hello.

We've just finished (or almost finished) with GCC-6 migration.

What does it mean?

1) GCC 6 is the default oi-userland compiler now. GCC 4.9 is used only 
to compile gcc-49 and illumos-gcc. Illumos-gcc 4.4.4 is still used to 
build illumos-gate and gfx-drm.
(So you have no excuse for submitting components, which don't build with 
GCC 6).


2) As GCC 6 runtime libraries live in /usr/gcc/6/lib and 
/usr/gcc/6/lib/$(MACH64), we  have runpath embedded in a lot of 
libraries. illumos-gate check_rtime doesn't like this, so build will 
fail if you have -r flag in NIGHTLY_OPTIONS. So far, just remove it, 
we'll try to find appropriate fix with illumos-gate developers a bit later.


3) We've merged code from 
https://github.com/OpenIndiana/oi-userland/pull/3883 . This drastically 
decreases time, spent by oi-userland in pkgdepend resolve phase. But 
this also means, that if pkgdepend finds some dependency for the 
component, it should be present in REQUIRED_PACKAGES (otherwise, resolve 
will fail). Note, that on build server the whole world is installed. Be 
sure to disable unused options or to test component with all possible 
dependencies from oi-userland (and add them to REQUIRED_PACKAGES).
Due to this change we populated REQUIRED_PACKAGES for many components 
and in theory could shrink build-essential to 'strictly required' 
components ('gmake env-prep' is your friend).


4) There were some updates, not directly related to gcc-6:
- IIIM was finally removed (while I rebuilt everything, found that it's 
broken and had no motivation to fix it), use ibus or xkbd.

- OpenJDK 8 was updated to 1.8.152.

5) Known issues:
- we found some issues with tmux, it seems it now can't properly handle 
ctrl^c (likely related to the fact that now compiler links it to 
/usr/lib/values-xpg6.o, and libraries suddenly become XPG6-aware).

- as due to gcc-6 migration oi-userland was completely rebuilt,
our /hipster repository significantly grew in size, we are likely going 
to clean it up from old packages this week.


--
Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department

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