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

2019-08-14 Thread 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

2019-08-08 Thread 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

2019-08-04 Thread 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

2019-07-31 Thread 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

2019-07-31 Thread 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

2019-07-31 Thread 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
 +  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] Clang and GCC6 runtime

2019-07-30 Thread Alexander Pyhalov via oi-dev
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
 +  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 ? 


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

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


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

2019-07-19 Thread 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

2019-07-16 Thread 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

2019-07-12 Thread 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

2019-06-28 Thread 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

2019-06-24 Thread 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

2019-06-24 Thread 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?

2019-06-24 Thread 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

2019-05-22 Thread 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

2019-05-22 Thread 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

2019-05-22 Thread 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

2019-05-21 Thread 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

2019-05-15 Thread 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

2019-05-14 Thread 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

2019-05-14 Thread 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

2019-05-12 Thread 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

2019-05-12 Thread 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

2019-04-18 Thread 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

2019-04-10 Thread 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?

2019-04-04 Thread 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?

2019-04-04 Thread 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

2019-04-03 Thread 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

2019-04-02 Thread 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

2019-04-02 Thread 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


Re: [oi-dev] rsync at dlc-origin.openindiana.org

2019-02-05 Thread Alexander Pyhalov via oi-dev
Hi, Marcel.
It's not intentional. I've contacted EC support yesterday, so far haven't 
received  detailed information on what is going on from them.

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




От: Marcel Telka 
Отправлено: 5 февраля 2019 г. 11:25:25
Кому: oi-dev@openindiana.org
Тема: [oi-dev] rsync at dlc-origin.openindiana.org

Hi,

For about a week now I have a problem to connect to the rsync service at 
dlc-origin.openindiana.org:

rsync: failed to connect to dlc-origin.openindiana.org (91.194.75.37): 
Connection timed out (145)
rsync error: error in socket IO (code 10) at clientserver.c(122) 
[Receiver=3.0.9]

What happened?  Is this intentional?


Thanks.

--
+---+
| Marcel Telka   e-mail:   mar...@telka.sk  |
|homepage: http://telka.sk/ |
|jabber:   mar...@jabber.sk |
+---+

___
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] OpenVPN in a local zone

2019-01-20 Thread 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

2018-12-20 Thread 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

2018-11-17 Thread 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

2018-10-24 Thread 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 ?

2018-10-22 Thread 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 ?

2018-10-22 Thread 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

2018-10-22 Thread 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] components.mk

2018-10-17 Thread Alexander Pyhalov via oi-dev
no

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



От: Rich Reynolds 
Отправлено: 18 октября 2018 г. 6:20:20
Кому: oi-dev@openindiana.org
Тема: [oi-dev] components.mk


hi all

is there anything in the build/publish process of userland that is
dependent on the order of things in components.mk?

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] openal repository

2018-10-17 Thread 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

2018-10-17 Thread 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

2018-10-14 Thread 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

2018-09-28 Thread 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

2018-09-28 Thread 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

2018-09-28 Thread 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

2018-09-24 Thread 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!

2018-09-24 Thread 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?

2018-08-31 Thread 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

2018-08-27 Thread 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