Re: [oi-dev] oi-vagrantfiles

[Adam Števko]

Hello,

instead of using sourceforge.net I would recommend creating the project
under OI Github organization. Scattering resources around the Internet is
not helpful and can be confusing for new comers.
I would also recommend basing these vagrant files on the stock ones. I
think there was a way how you could just say to use OI base vagrant box and
then modify it with the vagrantfile for particular app.

Thanks,
Adam

On Tue, Sep 21, 2021 at 7:56 PM s...@pandora.be  wrote:

>
> As a generalisation of the idea to have a Vagrantfile for Cuis and Squeak,
> I created an oi-vagrantfiles project to setup VM's with vagrant.
>
> The ability to deploy OpenIndiana with/by vagrant can be used for example
> to create a VM to have oi-docs or oi-userland contributions, or for running
> Smalltalk in a VM.
>
> The Vagrantfile project is at
> https://sourceforge.net/projects/oi-vagrantfiles/
>
> Currently there is the excellent Vagrantfile in the oi-userland repo,
> by Adam Stevko and Michael Nowak and I copied that file (while retaining
> the copyright of course),
> to the oi-vagrantfiles repo.
>
> The idea of oi-vagrantfiles is to collect all sorts of Vagrantfiles for
> OpenIndiana development.
>
> If there is interest, this could perhaps also be hosted at
> https://github.com/OpenIndiana/
>
> David Stes
>
> ___
> 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 Developer Edition

[Adam Števko]

Hello,

out or curiosity, what exactly is the point and added of your proposed fork? 
Those packages can be easily installed any time after installing OI.

I am not sure which exact changes were rejected, but if your raise a discussion 
and explain clearly why they are needed, OI developers are more than happy to 
accept.

So, instead of forking and creating a “new distribution”, further fragmenting 
the illumos distribution market, cooperate and help us improve the existing 
project. There are lot of gaps where improvements are needed and extra manpower 
is more than welcome. At the end, I can’t tell you want to do, but can try and 
nicely ask you to collaborate. Please, collaborate with OI team to improve the 
current experience, more people will benefit from it!

P.S: Keeping python-27 around is quite dangerous as the upstream ended any kind 
of support of Python 2.x and without proper experience you are just put 
potential users in danger.

Thanks for understanding,
Adam

 

> On 16 Jan 2021, at 11:02, Hung Nguyen Gia via oi-dev  
> wrote:
> 
> Someone on this list challenged me of forking OpenIndiana in order for my 
> changes to be accepted. This is exactly what I'm going to do now. But I will 
> do it moderately, according to my skills.
> 
> I wanted to build something like in the title.
> 
> It's the normal desktop OI plus the following packages:
> 
> build-essential
> cmake
> ninja
> meson
> yasm
> autoconf-213
> header-audio
> sunpro
> motif
> python-27
> 
> More packages would be included in the future, if needed.
> 
> My computer power doesn't allow me to build everything myself, so I think I 
> will just pull the packages from OI repo.
> 
> The goal is to have a live ISO/USB images contain these additional packages.
> 
> I have come across this wiki:
> 
> http://docs.openindiana.org/dev/distribution-constructor/
> 
> But it's still not very clear to me. Any help would be appreciated.
> 
> ___
> 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] test 4

[Adam Števko]

test email, disregard please
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] test 3

[Adam Števko]

please discard this email
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] Test email 2

[Adam Števko]

Please disregard this email
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] Test email

[Adam Števko]

Hello,

please disregard this email.

Cheers,
Adam
___
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?

[Adam Števko]

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] Stale PRs are now closed automatically after 67 days

[Adam Števko]

Hello,

Aurelien and I integrated Stale bot (https://probot.github.io/apps/stale/),
that will automatically close stale PRs. We used the default values, so the
process will look like the following:

- 60 days since the last activity in the PR, bot will label it as stale and
bot will comment
- 7 days since marking the PR as stale, PR will be closed

Activity in this context could be anything: comments, code pushes etc.

The bot is configured to avoid touching PRs labelled "testing_needed" and
"pending".

Hopefully, this will be an useful integration.

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

Re: [oi-dev] HEADS UP: loader FB console

[Adam Števko]

Nice job Toomas!

You really deserve a big pack of cookies!

/me sends cookies to tsoome

Cheers,
Adam

On Mon, Jan 7, 2019 at 5:51 PM Toomas Soome via oi-dev <
oi-dev@openindiana.org> wrote:

> Hi!
>
> With "10028 loader: implement framebuffer console “, the loader does
> attempt to use framebuffer console as default. We still do not provide FB
> console for kernel/userland, but stay tuned:)
>
>
> The change does provide some notable features:
>
> framebuffer command to set/get/list the modes, and switch FB off.  It can
> be used in /boot/loader.rc.local (or remove .local) to set gfx mode.
>
> loadfont command for manual loading of console fonts (provided in
> /boot/fonts). Default built in font is 8x16, default loaded font depends on
> gfx mode.
>
> set screen-font= to switch font based on size
>
> set tem.fg_color=
> set tem.bg_color=
> set tem.inverse=
> set tem.inverse-screen=
>
> we do support standard ansi colors by name or values 0-7, variables can be
> set in loader.conf or /boot/conf.d/* (without set command, just name=value).
>
> thanks,
> toomas
> ___
> 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] GCC 8.2

[Adam Števko]

Hey Aurelien,

wonderful job!

Regards,
Adam

On Wed, Aug 15, 2018 at 11:01 PM, Aurélien Larcher <
aurelien.larc...@gmail.com> wrote:

> Hi,
> back from vacation, GCC 8.2 available for testing from the main repository
> in a moment.
> Additionnally I just fixed some component rebuilds and
> pkg.openindiana.org/gcc-next built with gcc-8 is now in sync again with
> the main repository, modulo that GCC 8.2 was already republished there.
>
> 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

Re: [oi-dev] Please stop! Re: Bill Gates is a typical rogue ..

[Adam Števko]

Hello,

the matter has been taken care of. Please, move on.

Thanks for understanding!

Cheers,
Adam

> On Jun 2, 2018, at 4:59 PM, Reginald Beardsley via oi-dev 
>  wrote:
> 
> None of this is relevant or appropriate.
> 
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



signature.asc
Description: Message signed with OpenPGP
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] GCC 6 switch

[Adam Števko]

Good job!

> On 12 Feb 2018, at 11:40, Alexander Pyhalov  wrote:
> 
> 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

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

Re: [oi-dev] GCC6 build zone status

[Adam Števko]

Aurelien,

Good job!

Adam

> On 4 Dec 2017, at 10:45, Aurelien Larcher  wrote:
> 
> Only ocaml remains :)
> So aside from openjdk-8 I'll have 100% gcc-6 compiled userland repository by 
> the end of the day :) 
> 
> Le Samedi 2 décembre 2017, Aurelien Larcher a écrit :
>> It seems that only ocaml and open-vm-tools remain since Andreas fixed 
>> spidermonkey.
>> Thanks :) 
>> 
>> Le Samedi 2 décembre 2017, Aurélien Larcher a écrit :
>>> With some more help from Ken, remaining packages follow:
>>> 
 
> runtime/ocaml
 
 Needs update.
 
> sysutils/open-vm-tools
 
 Needs update
 
> library/ spidermonkey
 
 Needs gcc6 patches.
>>> 
>>> 
>>> Updated page here https://wiki.openindiana.org/oi/GCC+6 and still openjdk-8
>>> to be considered at some point.
>>> 
>>> That leaves 4 packages out of 1390.
>>> 
>>> Thanks
>>> 
>>> Aurélien
>>> 
 
> 
> If someone knows about Lua, there are issues with hexchat and libpeas
> regarding luajit and LGI support.
> 
> Kind regards
> 
> Aurelien
> 
> --
> ---
> Praise the Caffeine embeddings
> 
 
 --
 Envoyé depuis mon Jolla
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> ---
>>> Praise the Caffeine embeddings
>>> 
>> 
>> -- 
>> Envoyé depuis mon Joll
> 
> -- 
> Envoyé depuis mon Jolla
> ___
> 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] Any test iso's newer than those from 170502?

[Adam Števko]

Hey,

no newer has been produced. ISOs are produced twice a year, the next ones will 
come in October.

Adam

> On Sep 9, 2017, at 8:07 AM, Harry Putnam  wrote:
> 
> Has anyone produced any test iso's since those of 170502?
> If so, where can they be found?
> 
> 
> ___
> 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] Presentación, miniconsulta e interés participativo

[Adam Števko]

Hola Echeley,

bienvenidos a la communidad OpenIndiana. Nuestro idioma principal es ingles.

> On 4 Sep 2017, at 05:36, Echedey López Romero  wrote:
> 
> Buenas noches desde España.
> 
> Llevo tiempo haciendo seguimiento a este proyecto, nunca he profundizado
> en la participación por falta de tiempo pero he llegado a instalar el
> sistema operativo OpenIndiana y leido algo de la documentación.

Comentarios bienvenidos.

> Me he percatado de que recientemente se han retirado dos distribuciones
> de IllumiOS y que la paquetería de OpenIndiana está algo escasa, lo cual
> me entristece.

Puedes elaborar? No tenemos todo, pero la mayoría del software común se puede 
encontrar en los repositorios. Siempre estamos buscando nuevos colaboradores.

> Tengo la intención de participar en el proyecto, en la medida de lo
> posible, portando software. Principalmente a las arquitecturas 64 y 32
> bits. Si se tiene la intención de alguna ARM podría colaborar (dispongo
> de una RPI 3).

Estamos siempre dispuestos a ayudar. Los esfuerzos de portado de software son 
bienvenidos. Para ARM contactar a illumos developer mailing list.

> Informo de que no cuento con experiencia en empaquetamiento pero sí
> compilando software para otras distribuciones de otros sistemas
> operativos como GNU/Linux ya seas por hobbie o necesidad y también estoy
> bastante interesado en el mundo del Software Libre y el Código Abierto.

Somos comunidad pequena, pero podemos ayudarte a aprender. Tenemos 
documentacion en https://wiki.openindiana.org y https://docs.openindiana.org. 

> Si hay algo que pueda hacer por favor, avisadme. Me tenéis a disposición
> en ciertas ocasiones por aquí, por MATRIX (matrix.org) como
> @cppms:matrix.org y por XMPP como citoplas...@movim.eu.

Usamos IRC #oi-dev @ irc.freenode.net o esta lista.

P.S: Lo siento por mi español, todavia estoy aprendiendo (estoy basado en 
Barcelona)

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

Re: [oi-dev] Phoronix again

[Adam Števko]

Hello Ken,

testing on VMWare or in public clouds won't help you at all as they are not 
emulating new hardware. The 'exotic' hardware we are talking here about is 
supposed to be for high-performance desktop/workstation systems and was 
released in May i.e. nearly 3 months ago.

Sure, it sucks that we don't support Core i9 yet, but given the size of the 
illumos developer community and focus, this is to be expected. The hardware 
will be supported sooner or later, like always.

When it comes to tge article I personally consider it unprofessional. That's 
all I am going to say on this matter.

Cheers,
Adam

> On 3 Aug 2017, at 16:08, ken mays via oi-dev  wrote:
> 
> You can use the Phoronix forums in relation to the article.
> Also, the OI wiki provides a way to report on our own 'test analysis' on 
> compatible OI-related hardware.
> 
> Phoronix is just another independent test and review website. Anyone can 
> report and test on what 'works for them' to 
> challenge what is said there or anywhere else.
> 
> You can simulate in VMware or virtual clouds, so having esoteric and exotic 
> physical hardware on hand/in-house is not a requirement.
> 
> ~K
> 
> 
> 
> On Monday, July 31, 2017 11:45 AM, Aurélien Larcher 
>  wrote:
> 
> 
> 
> 
> 
> It needs 3 things - hardware, engineer and time. AFAIK right now there are 2 
> companies behind illumos who have more direct relations with hardware - 
> Joyent and Nexenta and those companies are still most likely interested about 
> the server class hardware.
> 
> Anything else is really about the community - if anyone has such hardware and 
> is willing to help with diagnostics and testing, then we can do something, 
> otherwise...
> 
> I do not know if we could better communicate how to report such issues ...
> 
>  
> 
> rgds,
> toomas
> 
> __ _
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/ mailman/listinfo/oi-dev
> 
> 
> 
> 
> -- 
> ---
> 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

Re: [oi-dev] Plan for Hipster SPARC edition

[Adam Števko]

Hi Gary,

I will keep this short as I will be repeating what disccused the last time. I 
am not very happy about this because it evolved exactly like I thought it 
would. More message are inline.

> On 21 Jun 2017, at 23:30, Gary Mills  wrote:
> 
> I've now completed my build of oi-userland on SPARC hardware, at least
> to the extent that was possible with oi_151a8 .  Yes, the latest OI
> SPARC ISO is version oi_151a8 .  This is a major obstacle to Hipster
> development on the SPARC platform.

Great job! However, how does it help if there are no up-to-date SPARC illumos 
bits available? The plan was to get minimal illumos up and running, so we could 
self-host Jenkins on SPARC. What happened with this? Instead of SPARC people 
working together, we get multiple SPARC initiatives with no major milestone 
achieved anywhere.

> I propose, first of all, to create a Hipster ISO.  It won't be
> current, but it will be a much better base for further development.
> With this as a base, I and other developers will be able to build many
> more oi-userland packages.

You can build the ISO yourself and share it. I will be able to host undet 
contrib/ section on DLC and mirror it worldwide.

> I also propose to create a SPARC package repository to go along with
> the ISO.  Any SPARC developer will be able to contribute to this
> repository.  I haven't built illumos-gate, but perhaps other
> developers have already done this, and can contribute packages.  If
> not, I can do it.

With no build host, no build platform we are not able to self-host SPARC 
Jenkins and cannot do builds. Setting up a repository and blindly accepting 
built packages from people is not a very good approach from security point of 
view and I wouldn't recommend it. With the current setup, we are getting 
reviews from people and are able to spot potentionaly suspicious things at 
least.

> We need a few facilities to proceed with this plan.  One is a set of
> instructions for creating ISOs, particularly the text ISO, along with
> a list of packages to be included.

Distribution constructor files for hipster are available at 
https://hipster.openindiana.org/distro_const/, how to build ISOs can be found 
on the wiki.


> We also need a repository for SPARC packages, with a mechanism to
> permit any SPARC developer to upload packages to this repository.


> Finally, we need storage for a few ISO files.
> 
> The ultimate goal, of course, is an automatic procedure for building
> SPARC packages from the same code base as the current x86 packages.

Why not provide with the illlumos SPARC first and then go for oi-userland? We 
tried to put you, SPARC guys, in touch and create a joint effort for SPARC 
version of OpenIndiana, so we could release a reasonsble and instead we got 
fragmentation again. I don't think a lot can be achieved without SPARC build 
host, build platform and people willing to maintain SPARC version.

Please, don't take it badly, but I think we should follow one common cause if 
we want this project to stay alive, healthy and somewhat relevant. We have 
limited resources and we shall do better coordination. After all, fragmentation 
doesn't help anyone.

Cheers,
Adam



> 
> 
> -- 
> -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] no new illumos-gate builds?

[Adam Števko]

Hi,

I will have a look at it tonight once I come back home. Until then, it will 
have to wait.

Adam

> On 2 Jun 2017, at 18:53, Andreas Wacknitz  wrote:
> 
> Hi,
> 
> I find it suspect that our jenkins didn't produce new packages for almost one 
> week.
> There have been some patches since 27th of May in illumos-gate. What is wrong?
> 
> 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] [HEADS UP] bass-o-matic now supports incremental builds

[Adam Števko]

Hello,

I just merged bass-o-matic rewrite and incremental build changes. The 
incremental mode can be activated in the following way:

export BASS_O_MATIC_MODE=incremental

With the following change I was able to get down Jenkins build time from 3h 50 
minutes to 12 minutes. This is best used in Jenkins environment as incremental 
mode depends on tracking of last successfully build commits. Jenkins set 
GIT_PREVIOUS_SUCCESSFUL_COMMIT variable. if the variable is not found, 
bass-o-matic defaults to HEAD~1. The main motivation behind this change was to 
significantly speed up builds and integration process, so newly merged PR will 
be published in the repository in the matter of minutes, not hours.


This change is useful only for build machines or building PRs. In every day 
component development workflow, it won’t change much.

Cheers,
Adam


signature.asc
Description: Message signed with OpenPGP
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Discussing maintainers visibility in oi-userland

[Adam Števko]

Hello,

I would like to keep the status quo in this. We don’t have formal maintainers 
and basically every change to the package/component is reviewed by relevant 
person (me/alp/aurelien//jimklimov/wacki/agnar). I would really like to see 
this list to grow and reach the phase that we need to start think about 
maintainers, but we are not yet there. The situation right now is that even if 
a person reviews the change and think that other person should have a look, 
e.g. me when I am reviewing some libs that might affect GUI i ask alp for 
crossreview or when alp touches X11 things, he ask aurelien etc.

I would avoid creating a dedicated maintainers for now. If people really think 
it should be done, I would say it should be done on a technology stacks, e.g. 
Python, Ruby, webservers, X11, databases etc. In such cases every change would 
need to be approved by a relevant person. However, I think that might introduce 
latency and bureaucracy, which is really non-existent right now. I would like 
to keep it that way if possible.

Cheers,
Adam

> On May 11, 2017, at 9:13 PM, Peter Tribble  wrote:
> 
> On Thu, May 11, 2017 at 6:56 PM, Aurélien Larcher  > wrote:
> 
> The question raised is whether we should formalize a maintaining process for 
> some important components or groups of components.
> 
> At some point I joked about a campaign going like "Adopt a package".
> 
> There are downsides to having a formal owner: they can become a
> bottleneck, and it might discourage others to contribute in an area
> where there's an individual (or individuals) listed. Also, people may be
> reluctant to contribute if there's a prospect of being lumbered with
> the responsibility going forward.
> 
> But, if you can avoid that, then there are benefits to having what we
> would call "Subject Matter Experts" for components or groups. Having
> someone who is reasonably familiar with the component, preferably
> someone who uses it, is useful as a source of help and advice, and
> having a list of such people and their specialities would be useful to
> other contributors.
> 
> Putting such a list on display would also show that OI wasn't just a
> one or two person effort, which would be good.
> 
> --
> -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



signature.asc
Description: Message signed with OpenPGP
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Volunteer needed to take over the Twitter feed

[Adam Števko]

Hey Darek,

unfortunately, we can’t automate it. Right now, only valuable PRs are tweeted 
and doing that automatically would be spamming people. Social media requirement 
a dedicated person unfortunately. With Twitter we saw a nice boost in the 
project marketing and spreading news.

Cheers,
Adam

> On May 9, 2017, at 4:07 PM, Dariusz Sendkowski  wrote:
> 
> I thought the twitter feeds were done automatically, at least when a PR was 
> merged.
> If this is not the case, maybe it could be better to make it auto?
> 
> regards,
> Darek
> 
> 2017-05-08 19:32 GMT+02:00 Aurélien Larcher  >:
> Hi,
> I have managed the Twitter feed:
> 
> https://twitter.com/OpenIndiana 
> 
> in the past months but I will not have time to do so anymore.
> 
> We need a volunteer to handle this task, at least for a few weeks/months.
> This news feed is important to update people on the activity of the project 
> and advertise security updates.
> Kind regards
> 
> Aurélien
> 
> --
> ---
> 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



signature.asc
Description: Message signed with OpenPGP
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] exiv2 broken?

[Adam Števko]

Hey,

yes and possibly submit a fix, please.

Thanks,
Adam

> On May 9, 2017, at 7:56 PM, Andreas Wacknitz  wrote:
> 
> Ok, after reading the sources a little bit more I found out that the missing 
> include file should be generated.
> So it's a problem in our build. Shall I create a ticket?
> 
> Andreas
> 
> 
> Am 09.05.17 um 19:15 schrieb Andreas Wacknitz:
>> Hi,
>> 
>> when I try to build geeqie or gthumb packages with exiv2 installed I get 
>> compiler errors like this:
>> 
>> In file included from /usr/include/exiv2/types.hpp:35:0,
>> from /usr/include/exiv2/image.hpp:39,
>> from 
>> /oibuild/oi-userland/components/image/geeqie/geeqie-1.3/src/exiv2.cc:25:
>> /usr/include/exiv2/config.h:10:23: fatal error: exv_conf.h: No such file or 
>> directory
>> # include "exv_conf.h"
>>   ^
>> compilation terminated.
>> 
>> It seems as if the exiv2 package is missing this important configuration 
>> file. As far as I can tell this not
>> only a problem with our exiv2 package but also with the original sources as 
>> well. For me it looks as if
>> this library has only been used and tested with Visual Studio. What do you 
>> think?
>> 
>> 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



signature.asc
Description: Message signed with OpenPGP
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] OI 2017-05 snapshot: AMD Athlon 64 (K8) compatibility issues

[Adam Števko]

Hey Ken,

there is no 2017.05 snapshot, onlt 2017.04, which was released on 2 May.

Cheers,
Adam

> On May 5, 2017, at 5:04 PM, ken mays via oi-dev  
> wrote:
> 
> Hello,
> 
> If you are using AMD Athlon 64 (K8) CPUs, it is possible that the current 
> release of OI 2017.05 snapshot will not boot fully.
> Please bug report if you are using those specific CPUs.
> 
> Otherwise, all previous OI snapshots were tested as working.
> 
> ~ Ken
> 
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



signature.asc
Description: Message signed with OpenPGP
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] How to build minimal install DVD?

[Adam Števko]

Hi,

@alp: could you publish those?

Thinking about it would be great id we could package these and community could 
use them/contribute to them, what do you think Michal?

Cheers,
Adam

> On 28 Apr 2017, at 23:17, Michal Nowak  wrote:
> 
> Hi -
> 
> how do I build "minimal install DVD"?
> 
> I have a distribution constructor prescripts for text and live install, but I 
> could not find similar XML prescript for the minimal variant anywhere. Does 
> anyone have it?
> 
> Thank you,
> 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

Re: [oi-dev] [CFT] Xorg 1.18.4 update repository

[Adam Števko]

Hey,

great job aurelien and gordon!

Cheers,
Adam

> On Apr 25, 2017, at 6:01 PM, Alexander Pyhalov  wrote:
> 
> Hi, all.
> 
> In recent weeks we have fixed several issues with Intel drm driver and Xorg 
> server 1.18. So we are ready for second round of testing.
> Kudos go to Aurélien and Gordon for their hard work and, of course,
> to Alan for his help and consulting.
> 
> Lower is original Aurélien's message.
> Please, test packages from updated http://pkg.openindiana.org/xorg-testing/ 
> repository.
> Instructions available here 
> https://www.openindiana.org/2016/10/04/call-for-testing-repository-with-xorg-1-18-4-now-available/
>  are still relevant.
> 
> 
> On 10/ 4/16 11:11 PM, Aurélien Larcher wrote:
>> Hi,
>> I am happy to announce that we have prepared a repository with updated X11 
>> bits:
>> 
>> http://pkg.openindiana.org/xorg-testing/
>> 
>> On the menu:
>> 
>> ... a handful of libraries and apps updated,
>> ... Xorg 1.18.4, TurboVNC refreshed with Xorg 1.18,
>> ... some drivers bumps,
>> ... and CVEs picked fresh from the market today.
>> 
>> Find below a short article about the repository and instructions to
>> install the packages:
>> 
>> https://www.openindiana.org/2016/10/04/call-for-testing-repository-with-xorg-1-18-4-now-available/
>> 
>> Many thanks to Martin for his hard work on drm/i915, of course to
>> Alexander, Ken, Adam, and also to Alan and the Solaris team with whom
>> I have been playing catch up in the past months in order to
>> migrate/update the X11 gate in oi-userland.
>> 
>> Thank you in advance for your feedback.
>> Kind regards
>> 
>> Aurélien
>> 
> 
> 
> --
> 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



signature.asc
Description: Message signed with OpenPGP
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] "Fixed Enlightenment" or "Beware of epoll"

[Adam Števko]

Hey,

lx separatiom is being worked on by me, but I had more important things to 
attend, so I lost focus. I will see what I can do during the weekend.

The implementatuon was already reviwed and Joyent people were OK with. I just 
meed to publish the final webrev on illumos-developer.

Cheers,
Adam

> On 12 Apr 2017, at 09:25, Vincent Torri  wrote:
> 
>> On Wed, Apr 12, 2017 at 9:06 AM, Joshua M. Clulow  wrote:
>>> On 11 April 2017 at 23:57, Vincent Torri  wrote:
>>> I can provide a fix in the build system of the EFL for the next
>>> release, but indeed, it would be better to hide the linux emulation
>>> layer. I can do that today
>> 
>> I'd still like to understand the precise nature of the issue with
>> epoll before we just paper over the problem.  It might be something we
>> can fix.
> 
> ok, I'll wait
> 
> Vincent Torri
> 
> ___
> 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] Automated oi-userland reviews: feedback

[Adam Števko]

Hello,

I have been playing with Danger today and I was able to put up together a 
system, which will check incoming pull requests for style fixes / notify people 
about things that are usually forgotten e.g. bumping COMPONENT_REVISION, 
claiming copyrights, WS_TOP -> WS_MAKE_RULES, adding REQUIRED_PACKAGES and etc.

Workflow (how it work once merged):
  - open a PR against openindiana/oi-userland
  - Travis (3rd party CI service) will be notified and will spawn Ubuntu 
container, which will run Danger and do the magic
  - results will be posted in a form of Github reviews to the PR and 
contributor can check it. If problems arise, he can fix it until the build 
passes the check

Example: https://github.com/xen0l/oi-userland/pull/3 


I would be interested in feedback on usability / text formatting (e.g. file 
paths can be made a link to file directly) / additional check types. I am also 
investigating option of inline commenting.

Cheers,
Adam





signature.asc
Description: Message signed with OpenPGP
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Wiki comments

[Adam Števko]

Hello Nikola,

> On 30 Mar 2017, at 17:29, Nikola M  wrote:
> 
> Obviously, since I mentioned it, someone has the time...
> So it is not true that "nobody has the time", since I am here.

As much as I dislike to speak about this publicly, but I don't think there is 
any other option. 

The fact that wiki was mess was known for a long time. We have asked you 
multiple time in the past if you would be interested in reorganizing wiki. 
Apart from saying "good idea", you never did anything in this regard. 

After Aurelien was tired of listening to complaints about the current state of 
Wiki and realized that with outdated content and comments, people won't give a 
chance to OI, because they can't find a up to date content, he picked up this 
job with other contributions (updating xorg/scientific stack, doing tweeting 
and increasing activity on social media by 1000% and still having time to hack 
on virtualbox/qt).

And what did he receive? Reverting of his work by you, your constant whining 
and worthless talking how it should be done, yet when you had opportunity to 
change the state of thing you did nothing, exactly nothing! What's more, you 
behave like a spoiled child and a complete energy sucker, which demovative 
other. Tell me exactlt one good reason, why we as a community should tolerate 
your behaviour? 

What did you achieve? Aurelien unsubscribed? Are you happy now? I hope you are! 
What's the point of your activity? You are not helping the community, the 
project, developers and yourself.

I wish we wouldn't need to deal with the same thing all over again. Please, 
consider doing some self-reflection.

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

Re: [oi-dev] Dropping java interfaces to Gnome libraries

[Adam Števko]

Hey,

+1 from me. If the upstream dropped, we can safely assume we don't need it 
either.

Cheers,
Adam

> On 28 Feb 2017, at 23:49, Alexander Pyhalov  wrote:
> 
>> On 28.02.2017 23:43, Franklin Ronald wrote:
>> Hello,
>> I don't know any real world application that make use of Java-Gnome stack.
>> In official site the latest beta was released on 2013, May.
>> The most notable Java Desktop applications are written with Swing or
>> SWT. If anyone write a java desktop application normally is because
>> "portability" (or are completely crazy), and make a glue between Java
>> and specific desktop API is nonsense IMHO.
>> I think that libraries can be dropped.
>> Em 28/02/17 17:30, Alexander Pyhalov escreveu:
>>> Hello, people.
>>> Need your opinion on the following question.
>>> We currently provide several jni libraries, wrapping
>>> Gnome native libraries -
>>> cairo-java
>>> java-atk-wrapper
>>> libgconf-java
>>> libglade-java
>>> libgnome-java
>>> libgtk-java
>>> glib-java
>>> libvte-java
> 
> There's a little mess.
> I believe that we've never shipped java-gnome, 
> http://ftp.gnome.org/pub/GNOME/sources/java-gnome/4.1/ (from 2013).
> We shipped only libgnome-java, 
> https://ftp.gnome.org/pub/gnome/sources/libgnome-java/2.12/ (from 2007).
> 
> Oracle has dropped these libraries (except java-atk-wrapper) at 2015-12-15, 
> according to solaris-desktop~spec-files Changelog.
> I'm inclined to do the same...
> 
> ---
> System Administrator of Southern Federal University Computer Center
> 
> 
> ___
> 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] Wiki comments

[Adam Števko]

Hello,

I also support this step. I will be for every solution that helps us clean up 
wiki even more. Seeing outdated comments is bad thing. I’d rather see people 
update wiki content or contribute to oi-docs (hey, we need you!). If they want 
to discuss, there are channels for that: mailing lists and IRC.

I am not going to react to everything, only to few key things:

- number of mailing lists - historically, there might have been more mailing 
lists for different sub projects, but it doesn’t make sense to return to such 
setup unless we grow our contributor base significantly. It isn’t very 
practical to have 20 mailing lists and only 2-3 people on them. We can use 
existing lists.

- #oi-documentation is not an official IRC channel and any talk regarding 
development, documentation, asking question etc can be done in #openindiana / 
#oi-dev. So, if there is an interest in moving documentation forward, please 
let’s reuse existing channels and not fragment the already small community.

As for disabling comments, I think we should set a deadline.

Cheers,
Adam

> On Feb 25, 2017, at 5:43 PM, Aurélien Larcher  
> wrote:
> 
> Hi,
> could we disable comments on the wiki and remove all the existing ones.
> Most discussions are outdated, either irrelevant or incorrect.
> Discussions happen on IRC or the ML, no need for duplicates.
> We could argue about the lack of forums but in any case the Wiki is not one.
> 
> Aurélien
> 
> --
> ---
> Praise the Caffeine embeddings
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



signature.asc
Description: Message signed with OpenPGP
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] FOSDEM 2017 hackathon

[Adam Števko]

Hello,

as you all know FOSDEM 2017 is organized during the first weekend in February, 
which is almost in two weeks' time. There will be a gathering of almost all OI 
developers.

We will have 2 days of time available for hacking and discussions. I would like 
us to make the maximum use of this time and leverage the fact that there will 
be a huge presence of OI developers to work on projects that will benefit from 
having all these people available literally next to you.
For that reason, I would like to do some small planning in advance, so we know 
what projects we will be able to finish during this time / move *significantly* 
forward. I would like us to avoid working on projects, which are one man's work 
(those can be done anytime).

I would also like to encourage people, who are not attending FOSDEM and will be 
available during that time to engage. With more people, we are able to do more 
things!

I would also like to hear your feedback on this and propose projects, which you 
think should be finished / worked on. Also, if you need access to more build 
resources, please let me know in advance. I might have one spare VM for builds 
/ testing.

For myself, I know that Jim and I will be working on the build system.

I would also like this thread to stay on topic.
With good organization, we are able to deliver good results. 

Thanks!

Cheers,
Adam



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

Re: [oi-dev] illumos-gate build time

[Adam Števko]

Anyone interested in creating FlameGraph like visualization?

Adam

> On Jan 2, 2017, at 6:19 PM, Gordon Ross  wrote:
> 
> Time for a new topic :)
> 
> On Sun, Jan 1, 2017 at 10:11 AM, Jim Klimov  wrote:
> [...]
>> By the way, regarding builds of illumos-gate, I estimate that most of the 
>> time is spent walking the makefiles and directories, several rounds while 
>> nightly.sh works. On lesser computers this alone adds up to tens of minutes 
>> if not hours.
>> 
>> Are there any hints or efforts on optimising this? Maybe somehow precompile 
>> a single big makefile to reduce walks and forks, or something?
> 
> As with any serious optimization effort, the best recommendation is to
> first try to measure where the time is being spent.  The last time I
> heard of anyone doing that for the build, it was (in general) I/O
> bound.  I vaguely recall that a large factor of the I/O time was
> dominated by "stat" calls, and I thing those were mostly for files or
> directories that do not exist.
> 
> Trying to make some new measurements would be a great place to start.
> 
> One reason for excessive stat calls in our build is the widespread use
> of shared makefiles that have lots of pattern rules (i.e.
> uts/*/Makefile.rules), and where only one or a couple of those pattern
> rules are in use.  In such cases, make has to do stats of many
> (typically nonexistent) objects to find out that a pattern rule does
> not apply.  But before anyone goes trying to "fix" that, we'll need
> measurements.
> 
> ___
> 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] Ansible modules for managing illumos networking - help with review/testing needed

[Adam Števko]

Hello,

this might matter to people who use Ansible to manage any illumos 
distributions. I have opened a PR on Ansible's Github 
(https://github.com/ansible/ansible/pull/19396), which brings in these modules:

dladm_iptun
dladm_linkprop
dladm_vlan
ipadm_addr
ipadm_addrprop
ipadm_ifprop

I would like to ask people using Ansible to have a look at these modules, test 
them and review them, so they can be merged into Ansible before 2.3 is released 
(January/February). With these modules, 90% of illumos networking can be 
configured via Ansible. The review is as easy as writing “shipit” in the PR 
discussion.

After these modules are merged, only remaining network-related pieces missing 
to be contributed are:

- link aggregations - I don’t have an access to a machine where I could test 
this (if somebody is interested in this and is able to provide testing 
environment, feel free to contact me privately)
- bridges - I have never needed to use them on illumos. (If there is interest, 
I can implement this as it quite simple to do).
- routeadm - to manage ipv(4|6)-(forwarding|routing) options via routeadm 
command.

In the upcoming months, I want to work on more modules and making illumos based 
systems much easier to automate via Ansible. I have created a repository 
(https://github.com/xen0l/ansible-illumos-modules), where I have collected all 
the ideas for modules I want to develop. I am always interested in getting new 
ideas about modules, so if people have any, feel free to send me a PR with the 
idea! I also plan to fix any illumos-related bug that appears in Ansible.

Those, who might review networking PR, might be also interested in reviewing 
these PRs:

- Gather uptime and device facts from Solarish systems 
(https://github.com/ansible/ansible/pull/18733)

These PRs have already been reviewed, but more reviews will speed up inclusion:

- Add module for managing boot environments on FreeBSD/Solaris/illumos systems 
(https://github.com/ansible/ansible/pull/19180)
- Modules for gathering facts about ZFS datasets and pools 
(https://github.com/ansible/ansible/pull/19181)

I would like to thank everyone in advance for helping me 
test/review/contributing new module ideas.

Cheers,
Adam


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

[oi-dev] Hipster 2016.10 vagrant box is now available!

[Adam Števko]

Hello,

I updated hipster vagrant box to 2016.10 snapshot. Feel free to test it, use it 
and develop on it.

I also created a repository, which I used for building it: 
https://github.com/OpenIndiana/oi-packer 


Cheers,
Adam

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

[oi-dev] HEADS UP: /dev images are archived

[Adam Števko]

Hello,

I moved all /dev and old OpenSolaris isos under archive directory at 
http://dlc.openindiana.org/isos/archive/ 
. This change is going to be 
propagated to mirrors after they sync.

Cheers,
Adam

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

Re: [oi-dev] USB installation instructions

[Adam Števko]

Hi,

i have the same opinion as Alexander. If the article appears in the oi-docs it 
will also be shipped on the media thanks to Aurelien.
Offline documentation is a good thing to have in cases when you need to 
configure network, but don't know how etc.

Cheers,
Adam

> On 22 Nov 2016, at 08:39, Alexander Pyhalov  wrote:
> 
>> On 11/14/16 09:16 PM, Aurélien Larcher wrote:
>> Hello,
>> the download page points to the following instructions which are outdated:
>> 
>> https://wiki.openindiana.org/oi/Installing+OpenIndiana
>> 
>> Maybe we should have reviewed the installation instructions beforehand,
>> this is a bit unfortunate :S
>> 
>> What is the plan? Pointing to OI Docs or updating the Wiki?
>> 
> 
> Hello.
> I think the long term plan is to move polished user documentation to 
> http://docs.openindiana.org/. In my opinion, Wiki should be preserved for 
> everything else: untypical system usage scenarios (like manual installation), 
> development documentation, some internal notes (like migration status), 
> constantly changing information (like changelog or uid/gid reservation list) 
> and so on.
> -- 
> 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] Fwd: USB 3.0 (xHCI) Beta Testing and Review

[Adam Števko]

> Begin forwarded message:
> 
> From: Robert Mustacchi <r...@joyent.com>
> Subject: USB 3.0 (xHCI) Beta Testing and Review
> Date: November 18, 2016 at 9:13:40 PM GMT+1
> To: illumos Developer <develo...@lists.illumos.org>
> Cc: Toomas Soome <tso...@me.com>, Dan McDonald <dan...@omniti.com>, Adam 
> Števko <adam.ste...@gmail.com>
> 
> Hi,
> 
> Thanks to everyone who's helped test some alpha builds of xhci, I think
> we have something that's getting pretty close to being a useful initial
> integration of USB 3 and xhci support.
> 
> I'd like to thank Toomas Soome, Dan McDonald, and Adam Števko I have
> images for SmartOS, OmniOS, OI hipster, and OI/Loader for ready testing.
> While there are a few known issues with the current code, if you see
> panics or hangs of any kind, please reach out to me with more
> information and if at all possible, a crash dump. Please note, this is
> all *beta* software. While I don't expect folks to encounter problems,
> you certainly may.
> 
> So far, we've tried to test as many of the major classes of devices as
> possible. Including audio, storage, serial, Ethernet, keyboard, mouse,
> hubs, etc. We've also had a lot of luck so far on the following
> chipsets: VMware Fusion controller, Fresco Logic FL1100EX, Intel 8
> Series/C220 series chipset, Sunrise Point-H USB 3.0 xHCI Controller, and
> Intel Celeron N2000 Series USB xHCI.
> 
> If you do test it, and things are working, it'd help me if you could
> share the output of the following two commands for my notes:
> 
> mdb -ke '::prtusb'
> prtconf -dD | grep -i xhci
> 
> With that, here are links to builds and images:
> 
> Toomas has put together his loader branch with the xhci changes. There
> are OI ISO/USB images here:
> 
> https://us-east.manta.joyent.com/rmustacc/public/preview/xhci/20161110/oi/OI_Loader_xhci_Text_X86.iso
> https://us-east.manta.joyent.com/rmustacc/public/preview/xhci/20161110/oi/OI_Loader_xhci_Text_X86.usb
> 
> Dan McDonald has put together OmniOS bloody repo available at:
> http://pkg.omniti.com/omnios/USB3/. For more information on how to use
> it, please reach out to OmniOS
> 
> Adam Števko has put together an OI Hipster repository. It's available at
> http://pkg.openindiana.org/hipster-xhci. For more information or
> questions on the repo, please reach out to the OI Developer list.
> 
> 
> SmartOS builds:
> 
> https://us-east.manta.joyent.com/rmustacc/public/preview/xhci/20161110/smartos/platform-20161117T180610Z.tgz
> https://us-east.manta.joyent.com/rmustacc/public/preview/xhci/20161110/smartos/platform-20161117T180610Z.iso
> https://us-east.manta.joyent.com/rmustacc/public/preview/xhci/20161110/smartos/platform-20161117T180610Z.usb.bz2
> 
> 
> SmartOS debug builds:
> 
> https://us-east.manta.joyent.com/rmustacc/public/preview/xhci/20161110/smartos-dbg/platform-20161116T183444Z.tgz
> https://us-east.manta.joyent.com/rmustacc/public/preview/xhci/20161110/smartos-dbg/platform-20161116T183444Z.iso
> https://us-east.manta.joyent.com/rmustacc/public/preview/xhci/20161110/smartos-dbg/platform-20161116T183444Z.usb.bz2
> 
> 
> Finally, if you're interested in review, we've started the process of
> our public review at Joyent. It's available at
> https://cr.joyent.us/#/c/872/. We will likely land this in
> illumos-joyent and get a little bit more soak time and then RTI it for
> illumos.
> 
> Once again, I'd like to thank everyone who's helped test, given me
> advice, or helped me through while debugging nasty bugs.
> 
> Thanks,
> Robert

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

Re: [oi-dev] FOSDEM 2017

[Adam Števko]

Hi,

FOSDEM is big and can have like 4000 visitors. However, that doesn't imply 
there are any OI users nor developers.

I was just checking the interest in the event and by knowing, which people are 
going to be there will allow us to better organize the hackathon (e.g. choose 
specific areas. There is no need to hackthon for problems that can be solved 
over IRC etc).

Cheers,
Adam

> On 17 Nov 2016, at 19:20, Ali Muhammed Patrash <uni...@outlook.com> wrote:
> 
> How Do You Do?
> 
> @Adam, what do you mean saying if there is enough people we could possibly 
> have a hackathon organized?
> Browsing the info about FOSDEM I've learned that usually this event is being 
> visited by somewhere about 4,000 people...
> 
> Best Regards from Belarus,
> Ali Muhammed (Ali for short),
> hyperor@
> 
> P.S.: Would like to meet oi-family while being presented<OutlookEmoji-.png>
> 
> From: Olaf Bohlen <olboh...@eenfach.de>
> Sent: Thursday, November 17, 2016 4:28:21 AM
> To: OpenIndiana Developer mailing list; Adam Števko
> Subject: Re: [oi-dev] FOSDEM 2017
>  
> Hi,
> 
> I will be there and think a hackathon would be great.
> 
> Regards,
> 
> Am 9. November 2016 15:10:56 MEZ, schrieb "Adam Števko" 
> <adam.ste...@gmail.com>:
>> 
>> Hello,
>> 
>> how mahy people will attend FOSDEM 2017? If there is enough people, we could 
>> possibly have a hackathon organized.
>> 
>> Let us know your interest.
>> 
>> Cheers,
>> Adam
>> 
>> 
>> 
>> oi-dev mailing list
>> oi-dev@openindiana.org
>> https://openindiana.org/mailman/listinfo/oi-dev
> 
> -- 
> Olaf Bohlen
> ___
> 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] FOSDEM 2017

[Adam Števko]

Hello,

how mahy people will attend FOSDEM 2017? If there is enough people, we could 
possibly have a hackathon organized.

Let us know your interest.

Cheers,
Adam


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

[oi-dev] Fwd: [developer] HEADS UP: new driver for Intel WifiLink 4965/100/1000/2000/5000/6000

[Adam Števko]

> Begin forwarded message:
> 
> From: "Hans Rosenfeld" 
> Subject: [developer] HEADS UP: new driver for Intel WifiLink 
> 4965/100/1000/2000/5000/6000
> Date: November 9, 2016 at 1:40:30 PM GMT+1
> To: disc...@grumpf.hope-2000.org, develo...@lists.illumos.org
> Reply-To: develo...@lists.illumos.org
> 
> Hi,
> 
> if you're not using Intel wifi devices with illumos you can safely
> ignore this message.
> 
> Illumos just received the new port of the NetBSD iwn driver for Intel
> WifiLink 4965/100/1000/2000/5000/6000 series of devices.
> 
> This driver was so far only tested with 6000 series devices. I would
> appreciate to receive any test results on any of the other supposedly
> supported hardware, especially the 4965 and 5000 series that are
> currently supported by the iwk and iwh drivers. To switch to iwn for
> such a device you'll need to run update_drv twice, once to remove the
> PCI ID from the old driver and again to add it to iwn. Here's an
> example of how to do this for a 4965 device:
> 
> # update_drv -d -i pciex8086,4229 iwk
> # update_drv -a -i pciex8086,4229 iwn
> 
> 
> The iwp driver, which supports some older variants of the 6000 series,
> was changed to no longer attach to any devices by default. If you've
> been using iwp until now you will automatically be using iwn after
> updating illumos. If you run into any problems with iwn you can file a
> bug report and temporarily switch back to iwp using the update_drv
> method described above.
> 
> 
> Hans
> 
> 
> -- 
> %SYSTEM-F-ANARCHISM, The operating system has been overthrown
> 
> 
> ---
> illumos-developer
> Archives: https://www.listbox.com/member/archive/182179/=now
> RSS Feed: https://www.listbox.com/member/archive/rss/182179/25033492-6af06f0e
> Modify Your Subscription: 
> https://www.listbox.com/member/?member_id=25033492_secret=25033492-fa2f869b
> Powered by Listbox: http://www.listbox.com

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

[oi-dev] Call for contributors: New OpenIndiana documentation

[Adam Števko]

Hello folks,

After severals months of Michael’s hard work, we are glad to present a future 
basis for new OpenIndiana documentation. The documentation can be found at 
http://docs.openindiana.org. 

Michael tried to make the contribution barrier as low as possible, so here are 
couple of things:

• Documentation fixes/additions/removals all leverage the Github pull 
request (PR) system.
• Every PR is automatically built and the result of each build is marked in 
the PR menu. With this, you will know in a matter of minutes whether the change 
you made is mergeable and satisfies our checks.
• After a PR is merged, the change is automatically built and deployed to 
http://docs.openindiana.org

To begin contributing, the process is described in great detail at 
http://docs.openindiana.org/contrib/getting-started/. Contributing directly 
from OI is fully supported (either follow steps in the guide or "pkg install 
mkdocs"). You may also contribute from non-OI operating systems. 

With this pipeline, we can achieve fast and automated deployments and people 
can contribute with confidence.  Therefore, I would like to invite _ALL_ people 
that are somehow related to OpenIndiana, most notably _USERS_ to participate in 
the contributions. 

Here are some of the ways you may contribute:

• Proofreading the documentation. The more times the documentation is read, 
the better and more precise it will be. Having more eyes on the content will 
boost our chance to spot errors and outdated content. As the ranks of OI 
developers are steadily growing and new features/changes are being incorporated 
faster than ever, the documentation will quickly become out of date. With more 
people contributing to the documentation effort, this problem can be prevented.

• Review contributed content. There is never enough reviewers for the 
content. So, any PR with content addition/modification/removal can use your 
review.

• Write new content and add new section. The more content we can get, the 
better the documentation will be.

• Adopt certain sections and actively maintain them as more new features 
are being delivered to OpenIndiana.

I would also like to warn people that you still have to consider this project 
as work in progress and it does not serve as Wiki replacement. The longterm 
plan of this project is to serve as the end user documentation and fulfill a 
role within the OI community much as the FreeBSD handbook does for the FreeBSD 
community. Those who have used the FreeBSD handbook will know what I’m talking 
about. 

The OpenIndiana wiki has a lot of content, but a huge amount of it is outdated 
and not relevant any more. However, this will be solved in the future by doing 
another call for participants. Notes related to the OpenIndiana development are 
to stay on our wiki in the future.

I hope the majority of you will like this project and we will see new 
contributions flowing in!

P.S: In the future, we also plan to deliver an offline copy of this 
documentation included with the installation medias. More information will be 
provided later.

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

Re: [oi-dev] SFW Packages left for migration

[Adam Števko]

Never mind, I have looked at the wrong repo.

> On Oct 12, 2016, at 5:06 PM, Adam Števko <adam.ste...@gmail.com> wrote:
> 
> Hi,
> 
>> On Oct 12, 2016, at 4:20 PM, Aurélien Larcher <aurelien.larc...@gmail.com 
>> <mailto:aurelien.larc...@gmail.com>> wrote:
>> 
>> benchmark/iozone
> 
> this one is already in hipster.
> 
> Cheers,
> Adam

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

Re: [oi-dev] SFW Packages left for migration

[Adam Števko]

Hi,

> On Oct 12, 2016, at 4:20 PM, Aurélien Larcher  
> wrote:
> 
> benchmark/iozone

this one is already in hipster.

Cheers,
Adam___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Lithuanian OpenIndiana users / developers

[Adam Števko]

Guys, are you in Vilnius so we can debate? ;)

Cheers,
Adam

> On Sep 21, 2016, at 8:34 PM, Cedric Blancher <cedric.blanc...@gmail.com> 
> wrote:
> 
> Better AFTER a LOT of beer AND lots of pints AND a bottle of whiskey,
> or the depressions about the state of Illumos will kill ya.
> 
> Ced
> 
> On 21 September 2016 at 20:22, Hans J. Albertsson
> <hans.j.alberts...@gmail.com> wrote:
>> A better ide is to debate BEFORE beer, not over beer.
>> 
>> 
>> On 2016-09-21 19:47, Adam Števko wrote:
>> 
>> Hello,
>> 
>> this is aimed at any Lithuanian users / developers living in Vilnius. I am
>> staying here for few nights and would like to know and meet people in person
>> if there are any. I would like to debate few things over beer with them. :)
>> 
>> Cheers,
>> Adam
>> 
>> 
>> ___
>> 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
> 
> 
> 
> --
> Cedric Blancher <cedric.blanc...@gmail.com>
> [https://plus.google.com/u/0/+CedricBlancher/]
> Institute Pasteur
> 
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] Lithuanian OpenIndiana users / developers

[Adam Števko]

Hello,

this is aimed at any Lithuanian users / developers living in Vilnius. I am 
staying here for few nights and would like to know and meet people in person if 
there are any. I would like to debate few things over beer with them. :)

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

Re: [oi-dev] Build Failed - oi-userland

[Adam Števko]

Hi,

can you join #oi-dev @ irc.freenode.net ?

Cheers,
Adam

> On Sep 12, 2016, at 10:27 PM, Franklin  wrote:
> 
> Hi team,
> 
> I'm configuring a bare-metal server to build oi-userland and make a private 
> server for IPS packages for Quality Assurance of packages contributed by 
> Wiselabs (my company).
> 
> I've installed build-essential and anothers some packages that be required 
> during compilation (like libpthread-stubs), but, the ORbit2 won't compile.
> 
> Anyone can help?
> 
> oot@oi_build:/root/.hudson/jobs/oi-userland/workspace/components/ORBit2# 
> gmake build
> ( cd 
> /root/.hudson/jobs/oi-userland/workspace/components/ORBit2/ORBit2-2.14.19 && 
> aclocal -I. && autoheader && libtoolize --automake --copy --force && automake 
> -a -f -c && autoconf )
> aclocal: warning: autoconf input should be named 'configure.ac 
> ', not 'configure.in '
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at /usr/bin/automake line 3936.
> automake: warning: autoconf input should be named 'configure.ac 
> ', not 'configure.in '
> automake: warning: autoconf input should be named 'configure.ac 
> ', not 'configure.in '
> gtk-doc.make:7: error: GTK_DOC_USE_LIBTOOL does not appear in AM_CONDITIONAL
> docs/api/Makefile.am:63:   'gtk-doc.make' included from here
> gtk-doc.make:52: error: ENABLE_GTK_DOC does not appear in AM_CONDITIONAL
> docs/api/Makefile.am:63:   'gtk-doc.make' included from here
> gtk-doc.make:53: error: GTK_DOC_BUILD_HTML does not appear in AM_CONDITIONAL
> docs/api/Makefile.am:63:   'gtk-doc.make' included from here
> gtk-doc.make:58: error: GTK_DOC_BUILD_PDF does not appear in AM_CONDITIONAL
> docs/api/Makefile.am:63:   'gtk-doc.make' included from here
> gtk-doc.make:211: error: ENABLE_GTK_DOC does not appear in AM_CONDITIONAL
> docs/api/Makefile.am:63:   'gtk-doc.make' included from here
> Makefile.shared:6: warning: '%'-style pattern rules are a GNU make extension
> include/orbit/dynamic/Makefile.am:18:   'Makefile.shared' included from here
> Makefile.shared:7: warning: *: non-POSIX variable name
> include/orbit/dynamic/Makefile.am:18:   'Makefile.shared' included from here
> Makefile.shared:8: warning: *D: non-POSIX variable name
> include/orbit/dynamic/Makefile.am:18:   'Makefile.shared' included from here
> Makefile.shared:8: warning: *F: non-POSIX variable name
> include/orbit/dynamic/Makefile.am:18:   'Makefile.shared' included from here
> Makefile.shared:9: warning: *: non-POSIX variable name
> include/orbit/dynamic/Makefile.am:18:   'Makefile.shared' included from here
> Makefile.shared:17: warning: ':='-style assignments are not portable
> include/orbit/dynamic/Makefile.am:18:   'Makefile.shared' included from here
> Makefile.shared:17: warning: shell mkdir .deps > /dev/null 2>&1 || :: 
> non-POSIX variable name
> Makefile.shared:17: (probably a GNU make extension)
> include/orbit/dynamic/Makefile.am:18:   'Makefile.shared' included from here
> Makefile.shared:6: warning: '%'-style pattern rules are a GNU make extension
> include/orbit/orb-core/Makefile.am:45:   'Makefile.shared' included from here
> Makefile.shared:7: warning: *: non-POSIX variable name
> include/orbit/orb-core/Makefile.am:45:   'Makefile.shared' included from here
> Makefile.shared:8: warning: *D: non-POSIX variable name
> include/orbit/orb-core/Makefile.am:45:   'Makefile.shared' included from here
> Makefile.shared:8: warning: *F: non-POSIX variable name
> include/orbit/orb-core/Makefile.am:45:   'Makefile.shared' included from here
> Makefile.shared:9: warning: *: non-POSIX variable name
> include/orbit/orb-core/Makefile.am:45:   'Makefile.shared' included from here
> Makefile.shared:17: warning: ':='-style assignments are not portable
> include/orbit/orb-core/Makefile.am:45:   'Makefile.shared' included from here
> Makefile.shared:17: warning: shell mkdir .deps > /dev/null 2>&1 || :: 
> non-POSIX variable name
> Makefile.shared:17: (probably a GNU make extension)
> include/orbit/orb-core/Makefile.am:45:   'Makefile.shared' included from here
> Makefile.shared:6: warning: '%'-style pattern rules are a GNU make extension
> include/orbit/poa/Makefile.am:24:   'Makefile.shared' included from here
> Makefile.shared:7: warning: *: non-POSIX variable name
> include/orbit/poa/Makefile.am:24:   'Makefile.shared' included from here
> Makefile.shared:8: warning: *D: non-POSIX variable name
> include/orbit/poa/Makefile.am:24:   'Makefile.shared' included from here
> Makefile.shared:8: warning: *F: non-POSIX variable name
> include/orbit/poa/Makefile.am:24:   'Makefile.shared' included from here
> Makefile.shared:9: warning: *: non-POSIX variable name
> include/orbit/poa/Makefile.am:24:   'Makefile.shared' included from here
> Makefile.shared:17: warning: 

Re: [oi-dev] Broken components

[Adam Števko]

Hi,

_ALL_ source tarballs will be available at 
http://dlc.openindiana.org/oi-userland/source-archives/ in an hour or so (I am 
copying it). I am also investigating the possibility to use mirroring 
infrastructure worldwide, but I don’t think it is a great idea as it will take 
disk space for no reason.

Let me know if something doesn’t work for you.

Cheers,
Adam

> On Sep 9, 2016, at 11:36 AM, Andrey Sokolov <kere...@solaris.kirov.ru> wrote:
> 
> Hi. Yes, I do. It would be great.
> 
> 2016-09-09 12:23 GMT+03:00 Adam Števko <adam.ste...@gmail.com 
> <mailto:adam.ste...@gmail.com>>:
> Hi,
> 
> thanks for reporting, we have source tarballs on the build machine. Do you 
> want me to make them available?
> 
> Cheers,
> Adam
> 
>> On Sep 9, 2016, at 11:20 AM, Andrey Sokolov <kere...@solaris.kirov.ru 
>> <mailto:kere...@solaris.kirov.ru>> wrote:
>> 
>> Subdirectory and broken links:
>> 
>> apache2-modules/mod_wsgi
>> http://modwsgi.googlecode.com/files/mod_wsgi-3.4.tar.gz 
>> <http://modwsgi.googlecode.com/files/mod_wsgi-3.4.tar.gz>
>> 
>> desktop/nimbus
>> http://gnome-look.org/CONTENT/content-files/164641-nimbus-gtk3-theme-4.2.tar.gz
>>  
>> <http://gnome-look.org/CONTENT/content-files/164641-nimbus-gtk3-theme-4.2.tar.gz>
>> 
>> desktop/openoffice
>> http://serf.googlecode.com/files/serf-1.2.1.tar.bz2 
>> <http://serf.googlecode.com/files/serf-1.2.1.tar.bz2>
>> http://ucpp.googlecode.com/files/ucpp-1.3.2.tar.gz 
>> <http://ucpp.googlecode.com/files/ucpp-1.3.2.tar.gz>
>> http://ooo-extras.apache-extras.org.codespot.com/files/ada24d37d8d638b3d8a9985e80bc2978-source-9.0.0.7-bj.zip
>>  
>> <http://ooo-extras.apache-extras.org.codespot.com/files/ada24d37d8d638b3d8a9985e80bc2978-source-9.0.0.7-bj.zip>
>> http://ooo-extras.apache-extras.org.codespot.com/files/24be19595acad0a2cae931af77a0148a-LICENSE_source-9.0.0.7-bj.html
>>  
>> <http://ooo-extras.apache-extras.org.codespot.com/files/24be19595acad0a2cae931af77a0148a-LICENSE_source-9.0.0.7-bj.html>
>> http://ooo-extras.apache-extras.org.codespot.com/files/48470d662650c3c074e1c3fabbc67bbd-README_source-9.0.0.7-bj.txt
>>  
>> <http://ooo-extras.apache-extras.org.codespot.com/files/48470d662650c3c074e1c3fabbc67bbd-README_source-9.0.0.7-bj.txt>
>> http://ooo-extras.apache-extras.org.codespot.com/files/ea570af93c284aa9e5621cd563f54f4d-bsh-2.0b1-src.tar.gz
>>  
>> <http://ooo-extras.apache-extras.org.codespot.com/files/ea570af93c284aa9e5621cd563f54f4d-bsh-2.0b1-src.tar.gz>
>> http://ooo-extras.apache-extras.org.codespot.com/files/35efabc239af896dfb79be7ebdd6e6b9-gentiumbasic-fonts-1.10.zip
>>  
>> <http://ooo-extras.apache-extras.org.codespot.com/files/35efabc239af896dfb79be7ebdd6e6b9-gentiumbasic-fonts-1.10.zip>
>> http://ooo-extras.apache-extras.org.codespot.com/files/1756c4fa6c616ae15973c104cd8cb256-Adobe-Core35_AFMs-314.tar.gz
>>  
>> <http://ooo-extras.apache-extras.org.codespot.com/files/1756c4fa6c616ae15973c104cd8cb256-Adobe-Core35_AFMs-314.tar.gz>
>> http://ooo-extras.apache-extras.org.codespot.com/files/fdb27bfe2dbe2e7b57ae194d9bf36bab-SampleICC-1.3.2.tar.gz
>>  
>> <http://ooo-extras.apache-extras.org.codespot.com/files/fdb27bfe2dbe2e7b57ae194d9bf36bab-SampleICC-1.3.2.tar.gz>
>> http://ooo-extras.apache-extras.org.codespot.com/files/61f59e4110781cbe66b46449eadac231-croscorefonts-1.21.0.tar.gz
>>  
>> <http://ooo-extras.apache-extras.org.codespot.com/files/61f59e4110781cbe66b46449eadac231-croscorefonts-1.21.0.tar.gz>
>> http://multidimalgorithm.googlecode.com/files/mdds_0.3.1.tar.bz2 
>> <http://multidimalgorithm.googlecode.com/files/mdds_0.3.1.tar.bz2>
>> http://ooo-extras.apache-extras.org.codespot.com/files/1f24ab1d39f4a51faf22244c94a6203f-xmlsec1-1.2.14.tar.gz
>>  
>> <http://ooo-extras.apache-extras.org.codespot.com/files/1f24ab1d39f4a51faf22244c94a6203f-xmlsec1-1.2.14.tar.gz>
>> 
>> fastcgi
>> http://www.fastcgi.com/dist/fcgi-2.4.0.tar.gz 
>> <http://www.fastcgi.com/dist/fcgi-2.4.0.tar.gz>
>> 
>> filebench
>> http://sourceforge.net/projects/filebench/files/filebench/filebench-1.4.9.1/filebench-1.4.9.1.tar.gz/download
>>  
>> <http://sourceforge.net/projects/filebench/files/filebench/filebench-1.4.9.1/filebench-1.4.9.1.tar.gz/download>
>> 
>> fonts/baekmuk-ttf
>> http://kldp.net/download.php/1429/ <http://kldp.net/download.php/1429/>
>> 
>> image/imagemagick
>> http://www.imagemagick.org//download/ImageMagick-6.9.4-5.tar.xz 
>> <http://www.imagemagick.org//download/ImageMagick-6.

Re: [oi-dev] Broken components

[Adam Števko]

Hi,

thanks for reporting, we have source tarballs on the build machine. Do you want 
me to make them available?

Cheers,
Adam

> On Sep 9, 2016, at 11:20 AM, Andrey Sokolov  wrote:
> 
> Subdirectory and broken links:
> 
> apache2-modules/mod_wsgi
> http://modwsgi.googlecode.com/files/mod_wsgi-3.4.tar.gz 
> 
> 
> desktop/nimbus
> http://gnome-look.org/CONTENT/content-files/164641-nimbus-gtk3-theme-4.2.tar.gz
>  
> 
> 
> desktop/openoffice
> http://serf.googlecode.com/files/serf-1.2.1.tar.bz2 
> 
> http://ucpp.googlecode.com/files/ucpp-1.3.2.tar.gz 
> 
> http://ooo-extras.apache-extras.org.codespot.com/files/ada24d37d8d638b3d8a9985e80bc2978-source-9.0.0.7-bj.zip
>  
> 
> http://ooo-extras.apache-extras.org.codespot.com/files/24be19595acad0a2cae931af77a0148a-LICENSE_source-9.0.0.7-bj.html
>  
> 
> http://ooo-extras.apache-extras.org.codespot.com/files/48470d662650c3c074e1c3fabbc67bbd-README_source-9.0.0.7-bj.txt
>  
> 
> http://ooo-extras.apache-extras.org.codespot.com/files/ea570af93c284aa9e5621cd563f54f4d-bsh-2.0b1-src.tar.gz
>  
> 
> http://ooo-extras.apache-extras.org.codespot.com/files/35efabc239af896dfb79be7ebdd6e6b9-gentiumbasic-fonts-1.10.zip
>  
> 
> http://ooo-extras.apache-extras.org.codespot.com/files/1756c4fa6c616ae15973c104cd8cb256-Adobe-Core35_AFMs-314.tar.gz
>  
> 
> http://ooo-extras.apache-extras.org.codespot.com/files/fdb27bfe2dbe2e7b57ae194d9bf36bab-SampleICC-1.3.2.tar.gz
>  
> 
> http://ooo-extras.apache-extras.org.codespot.com/files/61f59e4110781cbe66b46449eadac231-croscorefonts-1.21.0.tar.gz
>  
> 
> http://multidimalgorithm.googlecode.com/files/mdds_0.3.1.tar.bz2 
> 
> http://ooo-extras.apache-extras.org.codespot.com/files/1f24ab1d39f4a51faf22244c94a6203f-xmlsec1-1.2.14.tar.gz
>  
> 
> 
> fastcgi
> http://www.fastcgi.com/dist/fcgi-2.4.0.tar.gz 
> 
> 
> filebench
> http://sourceforge.net/projects/filebench/files/filebench/filebench-1.4.9.1/filebench-1.4.9.1.tar.gz/download
>  
> 
> 
> fonts/baekmuk-ttf
> http://kldp.net/download.php/1429/ 
> 
> image/imagemagick
> http://www.imagemagick.org//download/ImageMagick-6.9.4-5.tar.xz 
> 
> 
> inputmethod/ibus
> http://ibus.googlecode.com/files/ibus-1.3.9.tar.gz 
> 
> 
> junit
> https://github.com/junit-team/junit/archive/r4.11.tar.gz 
> 
> downloading...
> validating... corruption detected
> expected: 
> sha256:7f427e18a21006ea5394fb71b268d2fa1d12a9f4575b5743ff093547c7ac7b37
> actual:   
> sha256:65c0688d4491864ac53bf50164a02fa2169e14eb10bda6730934d6749d86587d
> payload:  
> sha256:5f40548bfd7af77b363b91473df76b686f241ea4ed3a0c2ccefc04f5a3369850
> 
> library/audiofile
> Source http://www.68k.org/~michael/audiofile/audiofile-0.2.7.tar.gz 
> 
> downloading...
> validating... Not a gzipped file corruption detected
> expected: 
> sha256:a61c4036c2600a645843f16bec4be166093a9df5f15b02c85291213aa9cf15a2
> actual:   
> sha256:9e497c08038c1dd1a6903090a980d84d23eaba83a1892375811792545da11f9e
> payload:  
> sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
> 
> library/libdnet
> http://libdnet.googlecode.com/files/libdnet-1.12.tgz 
> 
> 
> library/libevent2
> 

Re: [oi-dev] Netboot on OpenIndiana

[Adam Števko]

Hi Till,

> On 06 Sep 2016, at 19:14, Till Wegmüller  wrote:
> 
> Due to the fact that distro constructor takes 2+ hours to build an iso on 
> every change and my need for some experimentation, I built some scripts based 
> on alhazred's Firefly Recovery Image, Jimklimov's make firefly from root and 
> Peter Tribbles minimal viable Illumos.

Do you know why it takes so long? Do you know if the problem is IO bound and a 
SSD might help speed this up? Or is something else?

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

Re: [oi-dev] libfuse update

[Adam Števko]

Hi,

> On Aug 26, 2016, at 10:20 AM, Jean-Pierre André 
>  wrote:
> 
> Alexander Pyhalov wrote:
>> On 08/26/16 09:52 AM, Jean-Pierre André wrote:
>> 
>>> What is the need ? AKAIK gvfs is related to Gnome and
>>> is not supported on Linux any more.
>> 
>> I see the following fuse-related errors, trying to compile gvfs with
>> fuse support
>> 
>> 
>> error: 'struct fuse_conn_info' has no member named 'want'
> 
> This field exists in fuse 2.7, it is declared in the fuse-lite
> library used by ntfs-3g.
> 
>> error: 'FUSE_CAP_ATOMIC_O_TRUNC' undeclared
> 
> This is one of the bits going into the field "want". Is is
> about the file system telling it supports the O_TRUNC as an
> argument of open()... which current fuse expects anyway.
> 
> Both can be easily added to fuse_common.h, but this will
> not make libfuse to 2.8.
> 
> Patch proposal attached.
> 
> By the way, I sent several patches to libfuse to Adam
> last may. Did you take them into account ?

Patches have been delivered since May: 
https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/library/libfuse/patches
Though, I have to go through our communication and check if that’s all. I 
recall I haven’t applied everything.

Adam


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Brazilian Volunteer

[Adam Števko]

Hi,

if you are not using OI for development, but some different platcorm, ypu might 
have a look at 
https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/vagrant.md 
<https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/vagrant.md>.

Vagrant will allow you to bootstrap new development environment only in few 
commands. If you inspect the VM, you might see the suggested workflow.

This might help you as well: 
https://wiki.openindiana.org/oi/Building+with+oi-userland 
<https://wiki.openindiana.org/oi/Building+with+oi-userland>

Cheers,
Adam

> On Aug 23, 2016, at 7:26 PM, Franklin Ronald <franklin.des...@gmail.com> 
> wrote:
> 
> Hi Adam,
> I can start with issue in OpenJDK 8. Initially I'm thinking of devoting 8-16 
> hours per week for OpenIndiana.
> Before taking the 7227 to solve, I will setup the build environment in my 
> machine and explore the source organization.
> When I'm familiar I started my work on this issue. Ok?
> 
> 
> Any questions I sent a message here.
> 
> Thanks Adam,
> 
> Time to hack! :-)
> 
> Em 23/08/16 14:09, Adam Števko escreveu:
>> Hi,
>> 
>> I would propose you try out contributing to oi-userland first. We already 
>> have an issue with OpenJDK 8, which you possibly might be interested in - 
>> https://www.illumos.org/issues/7227 <https://www.illumos.org/issues/7227>. I 
>> you want to look into C/C++, you should check out adding ARC data to top - 
>> https://www.illumos.org/issues/7305 <https://www.illumos.org/issues/7305>. 
>> Building the distribution is a good way to get knowledge, but we are before 
>> the next snapshot (to be relased in October) and more hands available to 
>> solve existing bugs, would be appreciated.
>> 
>> If you need to know your way around I suggest you join #oi-dev on 
>> irc.freenode.net <http://irc.freenode.net/>, where people idle and will be 
>> available for questions/debates.
>> 
>> Welcome to the community!
>> 
>> Cheers,
>> Adam
>> 
>>> On Aug 23, 2016, at 6:36 PM, Franklin Ronald <franklin.des...@gmail.com 
>>> <mailto:franklin.des...@gmail.com>> wrote:
>>> 
>>> Hi OpenIndiana Community!
>>> 
>>> My name is Franklin Ronald. I'm a Brazilian software developer and when 
>>> OpenSolaris was active, I was a member of the community OpenSolaris Brazil. 
>>> I contributed with tutorials in wiki as and some developments. I made the 
>>> driver to support the HP notebook function keys on OpenSolaris, and some 
>>> small ports like OpenDS.
>>> 
>>> I would like to help OpenIndiana. Today, i have more experience and 
>>> currently i'm the owner of Wiselabs Software (http://www.wiselabs.com.br 
>>> <http://www.wiselabs.com.br/>).
>>> Wiselabs have an own Operating System for internal projects based on 
>>> FreeBSD, but now, i will migrate to OpenIndiana.
>>> 
>>> My first step now is build all source tree and make a ISO of OpenIndiana 
>>> from scratch. With all source working on my machine, i can try to solve 
>>> some bugs and start one project (packaging projects for Java EE application 
>>> servers is good for me).
>>> 
>>> Well... I'll try to build OpenIndiana now.
>>> 
>>> Little bit about me:
>>> 
>>> Java SE and EE Developer - Sênior
>>> Oracle Solaris Administrator - Certified ( I am currently working on a 
>>> project with Oracle Super Cluster and Solaris 11 to a large network of 
>>> stores in Brazil)
>>> C and C++ developer - Sênior (case on Brazilian Air Force in partner with 
>>> Omnisys/Thales Group)
>>> Python and Ruby - Sênior
>>> 
>>> Thanks. Thanks to all community to maintain a great enterprise class 
>>> operating system. I will be very happy to help.
>>> ___
>>> oi-dev mailing list
>>> oi-dev@openindiana.org <mailto:oi-dev@openindiana.org>
>>> https://openindiana.org/mailman/listinfo/oi-dev 
>>> <https://openindiana.org/mailman/listinfo/oi-dev>
>> 
>> 
>> ___
>> oi-dev mailing list
>> oi-dev@openindiana.org <mailto:oi-dev@openindiana.org>
>> https://openindiana.org/mailman/listinfo/oi-dev 
>> <https://openindiana.org/mailman/listinfo/oi-dev>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Brazilian Volunteer

[Adam Števko]

Hi,

I would propose you try out contributing to oi-userland first. We already have 
an issue with OpenJDK 8, which you possibly might be interested in - 
https://www.illumos.org/issues/7227 . I 
you want to look into C/C++, you should check out adding ARC data to top - 
https://www.illumos.org/issues/7305 . 
Building the distribution is a good way to get knowledge, but we are before the 
next snapshot (to be relased in October) and more hands available to solve 
existing bugs, would be appreciated.

If you need to know your way around I suggest you join #oi-dev on 
irc.freenode.net , where people idle and will be 
available for questions/debates.

Welcome to the community!

Cheers,
Adam

> On Aug 23, 2016, at 6:36 PM, Franklin Ronald  
> wrote:
> 
> Hi OpenIndiana Community!
> 
> My name is Franklin Ronald. I'm a Brazilian software developer and when 
> OpenSolaris was active, I was a member of the community OpenSolaris Brazil. I 
> contributed with tutorials in wiki as and some developments. I made the 
> driver to support the HP notebook function keys on OpenSolaris, and some 
> small ports like OpenDS.
> 
> I would like to help OpenIndiana. Today, i have more experience and currently 
> i'm the owner of Wiselabs Software (http://www.wiselabs.com.br 
> ).
> Wiselabs have an own Operating System for internal projects based on FreeBSD, 
> but now, i will migrate to OpenIndiana.
> 
> My first step now is build all source tree and make a ISO of OpenIndiana from 
> scratch. With all source working on my machine, i can try to solve some bugs 
> and start one project (packaging projects for Java EE application servers is 
> good for me).
> 
> Well... I'll try to build OpenIndiana now.
> 
> Little bit about me:
> 
> Java SE and EE Developer - Sênior
> Oracle Solaris Administrator - Certified ( I am currently working on a 
> project with Oracle Super Cluster and Solaris 11 to a large network of stores 
> in Brazil)
> C and C++ developer - Sênior (case on Brazilian Air Force in partner with 
> Omnisys/Thales Group)
> Python and Ruby - Sênior
> 
> Thanks. Thanks to all community to maintain a great enterprise class 
> operating system. I will be very happy to help.
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Looking back at the past 8 months...

[Adam Števko]

Hi people,

> On 19 Aug 2016, at 09:29, Aurélien Larcher  wrote:
> 
> If you fell like learning how to contribute to oi-userland and want to
> help out: these font packages are very easy components, thus perfect
> for getting started.
> Also there is always a short-list of components in need of a small bump ;)

If you feel that you could try it out, I would encourage you to do so even if 
you don't run OpenIndiana. i put together a little HOWTO to get development 
enviroment up and running as easy as possible.

URL: https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/vagrant.md

Contributing can't be easisr enough now.

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

Re: [oi-dev] Mate is here (as well as new test ISOs)

[Adam Števko]

Hi Peter,

> On Aug 17, 2016, at 11:47 AM, Peter Tribble  wrote:
> 
> 
> 
> On Tue, Aug 16, 2016 at 4:10 PM, Alexander Pyhalov  > wrote:
> 
> Two new image types: OI_MATE - this is Mate-based LiveDVD and OI_minimal (we 
> tried to strip down OI a bit). One thing about minimal image - it doesn't 
> deliver sudo, so initial user just gets root role. Note, these are test 
> images and not official snapshots.
> 
> Well done on shifting to MATE.
> 
> Some notes on the "minimal" iso:
> 
> Why prompt for language when there's only one option?

I think this has to do with the fact that we didn’t modify installer to reflect 
this. Do you think we should ship more languages or it’s fine as it is (+ 
language selection screen in that case)?

> Calling it minimal doesn't quite seem right. It's got bits of X, tcl, tk, 
> cairo,
> GL, berkelydb, mariadb, apr, apr-util, gdbm, graphite, openblas, cdrtools,
> 2 copies of python, ruby, fortran, apache. One or two bits I can imagine
> being pulled in via dependencies, but a lot of this seems wrong.
> 
> Doesn't have the man command (although it does have a lot of man
> pages). I would expect to be able to read man pages
> 

Alexander and I worked on the minimal list and we put in there we though was 
needed. The list is contained here: 
https://github.com/OpenIndiana/oi-userland/blob/6bb1bbacebdf2ae843ff749275ab6d9d45a81ad3/components/meta-packages/install-types/includes/minimal
 


I suppose the most of those packages where dragged in via dependencies. For 
packages:

- runtime/python-26 it is used by pkg/illumos-gate and unless pkg in OmniOS is 
updated (we spoke to Dan about it already, but is busy with LX, so we can’t 
drop the package. Some illumos-gate consumers also need python 2.6)
- runtime/python-27 is provided for the userland and it also used explicitly by 
the userland.

We tried to minize the amount of packages depending on python-26, but the 
packages coming of out illumos-gate are the main consumers, so there isn’t 
really another right now.

system/man was not omitted on purpose, I added it to the file list now.


> 
> We'd like to hear your opinion, which images are necessary for next snapshot 
> (supposedly, 2016.10). We think that minimal one, Mate and Gnome one are 
> enough. We are going to avoid delivering Gnome ISO image after next snapshot 
> (in 2017).
> 
> Presumably minimal is the new "text" iso.

We don’t consider it to be a replacement for text as of this moment. It’s just 
a much stripped down versions of text installer and in the future, text 
installer might be deprecated. However, this hasn’t been decided yet.

Cheers,
Adam



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Mate is here (as well as new test ISOs)

[Adam Števko]

Hi,

> On Aug 16, 2016, at 6:07 PM, Udo Grabowski (IMK)  
> wrote:
> 
> On 16/08/2016 17:32, Alexander Pyhalov wrote:
>> On 08/16/16 06:22 PM, Udo Grabowski (IMK) wrote:
>>> On 16/08/2016 17:10, Alexander Pyhalov wrote:
>> 
 We'd like to hear your opinion, which images are necessary for next
 snapshot
 (supposedly, 2016.10). We think that minimal one, Mate and Gnome one
 are enough.
 We are going to avoid delivering Gnome ISO image after next snapshot
 (in 2017).
 
 Also we are interested to hear if community needs VM images, and if it
 needs,
 then what exactly (qcow2, vmdk or something else).
>>> 
>>> Good work ! But under qemu-kvm, the MATE iso fails by starting Caja
>>> in an endless loop (visible in the lower panel), so the desktop remains
>>> mostly black, and Mate does not stop starting...
>> 
>> Can you start with ssh enabled, login as jack remotely and see if there are 
>> any
>> messages in ~/.xsession-errors?
> 
> ssh connection refused (sshd is running) - either misconfigured or not 
> starting
> correctly; if jack has an empty password, the sshd configuration
> denies logins with empty passords. But I can get a terminal after
> the Caja processes seemingly all died, the desktop still black,
> no border decoration, the terminal constantly moving to the lower
> right...after patient double typing  get these .xsession-errors:
> ---
> mate-settings-daemon MateDesktop-Warning: Call to screen_info_new
> is too frequent, skipping...
> caps.c Normally all extra capabilities would be dropped down, but
> that's impossible because PulseAudio was built without capabilities
> support.
> /usr/bin/dispswitch exiting: too few crtcs: 1
> pygobject_register_sinkfunc is  deprecated (GtkWindow,GtkInvisible,Gtkobject)
> mate-panel: couldn't get background pixmap
> Connection failure: Connection refused
> Initializing gksu extension
> The program caja received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadLength (poly request too large or internal Xlib
> lenght error (Details: serial 262 error_code 16 request_code 72
> minor_code 0)
> ---
> This goes on for a while, then the caja clients are killed:
> --
> Maximum number of clients reached
> caja: MateDesktop-Warning: Unable to open display :0 when setting
> background pixmap
> caja: Gdk-critical: IA__gdk_cairo_create asserttion 'GDK_IS_DRAWABLE
> (drawable) failed.
> recvmsg: Connection refused
> 
> a couple of those messages, then
> -
> process 3535 (one PID beyond the caja PID): arguments to dbus_message_unref()
> were incorrect, assertion "!message->in_cache" failed in file
> /jenkins/jobs/oi_userland/workspace/components/library/dbus/dbus-1.10.8/dbus/dbus-message.c
>  line 1719.
> This is normally a bug in some application using the D_Bus Llibrary.
> D-Bus not built with -rdynamic so unable to print a backtrace.
> -
> and more of the caja background pixmap and cairo IA__... messages.
> Then a heap of Xlib messages related to the caja breakdown:
> ---
> Bug in window manager: Unexpected X error: BadLength (poly request too
> large or internal Xlib
> lenght error (Details: serial 815 error_code 16 request_code 72
> minor_code 0)
> --
> the same messages repeating endlessly with other serials like
> 832 and 835. The terminal flickers endlessly while bumping into
> the lower right corner like a dumb zombie and is nearly unusable.
> 
> Hope that helps.

I will see if I can reproduce this. Just to clarify: are you running this on 
illumos qemu-kvm?

Cheers,
Adam



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] HEADS UP: HTTPS available on pkg.openindiana.org

[Adam Števko]

Hi Nikola,

> On Aug 13, 2016, at 8:39 PM, Nikola M <minik...@gmail.com> wrote:
> 
> On 08/ 9/16 06:49 PM, Adam Števko wrote:
>> Hello,
>> 
>> I gave our infrastructure some love and have following announcements:
>> 
>> - HTTPS availability
> 
> As I remember https was turned on some month ago, but turned off and turned 
> on again now.

Aren’t you talking about pkg.openindiana.org <http://pkg.openindiana.org/>? 
There never was HTTPS available on wordpress before.

> Just to mention,
> there is currently no solution for a problem that https is now forced and 
> redirected
> with no http access anymore to openindiana.org web site and openindiana.org 
> redirects to www.openindiana.org <http://www.openindiana.org/>.


The wordpress site name is www.openindiana.org <http://www.openindiana.org/>, 
so openindiana.org <http://openindiana.org/> redirect to www.openindiana.org 
<http://www.openindiana.org/> is a correct thing here. HTTP to HTTPS redirect 
exist to ensure that people always land on HTTPS variant and there is nothing 
wrong about it.
HTTPS access also gives us a better ranking on search engines.

Only thing, that has no HTTP variant is dlc.openindiana.org 
<http://dlc.openindiana.org/>, but that one doesn’t need HTTPS as media signing 
is coming with the next version.

Cheers,
Adam



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] HEADS UP: HTTPS available on pkg.openindiana.org

[Adam Števko]

Hello,

I gave our infrastructure some love and have following announcements:

- HTTPS availability on pkg.openindiana.org 

There were some calls to bring HTTPS to the package repository and we have it 
now. If you want to use it, run the following commands:

pfexec pkg set-publisher -g https://pkg.openindiana.org/hipster -G 
http://pkg.openindiana.org/hipster openindiana.org
pfexec pkg set-publisher -g https://pkg.openindiana.org/hipster-encumbered -G 
http://pkg.openindiana.org/hipster-encumbered hipster-encumbered

HTTPS is available for all repositories, but unfortunately I wasn’t able to get 
it working from /dev (if there is big enough demand I might have a deeper look 
on the issue).

- HTTPS availability on www.openindiana.org  / 
 wiki.openidniana.org 
 / 
 mailing 
 list archives

SSL certificates are provided by Let’s Encrypt.

This one should have been available much sooner, but at last we have it now. 
There were some troubles with mixed content on the Wordpress instance and I 
made sure and fix as many warnings as possible, so the website should be 
warning-free now. If you encounter some problem, please let me know.

Cheers,
Adam





signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] OpenIndiana Code of Conduct

[Adam Števko]

Hi Peter,

> I think somebody already mentioned this, but the address shouldn't be
> abuse@ which is a well-known email address designed for something else.

The abuse@ is general address to report any kind of abuses widely used in ISP 
space. These addresses are mostly obtainable via WHOIS or looking at RIR handle 
(in our case it’s RIPE). As OpenIndiana isn’t a registered member nor has 
separate handle in RIPE, any WHOIS request will reach EveryCity. Also, this 
email address hasn’t existed till I set it up 2 weeks ago, so it couldn’t have 
been abused. I replaced it with cond...@openindiana.org 
. Are you OK with that?

> There ought to be some detail of how a report is dealt with. The Django code
> of conduct is pretty good for that, but presupposes a formal structure we
> do not (yet) have.

I like the way how Django used that and we might reuse some parts of it. Thanks 
for suggestion.

Cheers,
Adam




signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] OpenIndiana Code of Conduct

[Adam Števko]

Hello,

any more comments on this?

http://wiki.openindiana.org/oi/Code+of+Conduct+proposals 
 - Modified proposed 
version
http://wiki.openindiana.org/pages/viewpage.action?pageId=31391953 
 - Nikola’s 
version

Cheers,
Adam

> On Jul 27, 2016, at 12:47 AM, Aurélien Larcher  
> wrote:
> 
> 
> 
> À mar. juil. 26 20:49:56 2016 GMT+0100, Michael Kruger a écrit :
>> On 07/26/2016 09:58 AM, WebDawg wrote:
>> 
>>> 
>>> For instance in this response:
>>> 
>>> "No unfinished half-things should be put on site like this."
>>> 
>>> Is this a decision that needs decided still? Is there a consensus in any
>>> direction that  http://www.openindiana.org/community/ is for drafts or
>>> not for drafts?  I get that the support docs had a new complete format
>>> and required possibly a different type of server but this stuff is just
>>> text.
>>> 
>>> 
>>> I also like mailing lists and hate wiki talk pages.
>> 
>> 
>> Hi WebDawg,
>> 
>> I am not aware of a formally established process for submitting draft
>> documents for consideration. For the purpose of discussing such a
>> document, conceivably, it could have been hosted anywhere (www, wiki,
>> google docs, github gist, etc.), or not hosted at all (e.g. the entire
>> text sent as a post to the mailing list).
>> 
>> As I understood it, the original idea was for people to view the
>> document and submit comments via the mailing list.
>> 
>> I don't believe it was ever intended for anyone but the original authors
>> to directly edit the document as hosted on the www site.
> 
> Indeed, the website being intended for publication only, the initial proposal 
> was meant to serve as reference for discussion on the mailing list first.
> 
> Editable versions on other media (like the wiki) from the discussion could be 
> then created as the discussion moved forward.
> 
> But in any case, the reference should still be available and unmodified so 
> that any participant can evaluate the differences/improvements.
> 
> Basically ... what Michael said.
> 
>> 
>> As for alternate proposals, comments, etc., they could have been
>> delivered in any form (IRC, mailing list, github gist, etc).
>> 
>> The need to provide an editable version of the document to be directly
>> edited by community members wasn't (I don't believe) ever considered.
>> 
>> Michael
>> 
>> ___
>> oi-dev mailing list
>> oi-dev@openindiana.org 
>> http://openindiana.org/mailman/listinfo/oi-dev 
>> 
>> 
> 
> --
> Thanks for sailing Jolla :)
> ___
> oi-dev mailing list
> oi-dev@openindiana.org 
> http://openindiana.org/mailman/listinfo/oi-dev 
> 


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] OpenIndiana Code of Conduct

[Adam Števko]

Hello,

I restored the copy on different wiki subpage, so people are able to see it: 
http://wiki.openindiana.org/oi/Code+of+Conduct+proposals 
<http://wiki.openindiana.org/oi/Code+of+Conduct+proposals>

Cheers,
Adam

> On Jul 24, 2016, at 8:59 PM, Adam Števko <adam.ste...@gmail.com> wrote:
> 
> Hello everybody,
> 
> I added draft of proposed CoC to wiki here: 
> http://wiki.openindiana.org/oi/Code+of+Conduct+proposals
> 
> I modified the Wiki entry to contain both versions.
> 
> Modified version of initial CoC text contains following changes:
> 
> - added to "Core principles and expectations:” part:
> 
> • Always seek to maintain a welcoming environment for new contributors.
>   • Welcome new people to the project and guide them in their 
> contributions.
>   • Give them the time you were given when you first joined the community.
>   • And if you weren't given enough time please set a new example for 
> others to live by.
> • Be open and transparent so others can participate on an equal footing and 
> contribute to the project in their own way.
>   • Everyone has something to contribute.
> 
> - added to “What will not be tolerated:” part:
> 
> Discrimination based on gender, race, nationality, sexuality, religion, age 
> or physical disability.
> 
> - “Reporting violations” part was changed:
>   • Violations of the CoC should be reported to the distribution 
> maintainers via ab...@openindiana.org.
>   • Neither reporters nor reported persons will, or should be, 
> made public.
>   • Upon receipt of a problem report, the distribution maintainers will 
> investigate the issue and determine whether it warrants further action. Any 
> further action will be proportional to the severity of the problem.
> 
> Changed things are based on former OpenSolaris Code of Conduct and 
> solicitations from the OpenIndiana community.
> 
> I hope that people are OK with these changes. I also expect this to be the 
> final draft unless some comments appear.
> 
> Cheers,
> Adam
> 
>> On Jul 24, 2016, at 5:56 PM, Aurélien Larcher <aurelien.larc...@gmail.com> 
>> wrote:
>> 
>> 
>> Le 24 juil. 2016 17:17, Nikola M <minik...@gmail.com> a écrit :
>>> 
>>> On 07/24/16 05:10 PM, Nikola M wrote:
>>>> As long it is there site is under occupation from that troll document.
>>> 
>>> And I won't try to change it anymore, since Aurelien objected and want
>>> it unchanged for whatever reason it is...
>>> Wanting to have document unchanged is obvious obstacle in community
>>> process, but hey, you have it..
>>> 
>> 
>> I just object to change without consultation of authors. :)
>> 
>> Adam, would you mind adding at least a référence to the WIP on the wiki and 
>> a line of context  to specify that the proposed document is only a basis and 
>> subject to improvement and acceptance by the community ?
>> 
>>> 
>>> ___
>>> oi-dev mailing list
>>> oi-dev@openindiana.org
>>> http://openindiana.org/mailman/listinfo/oi-dev
>> ___
>> oi-dev mailing list
>> oi-dev@openindiana.org
>> http://openindiana.org/mailman/listinfo/oi-dev
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] OpenIndiana Code of Conduct

[Adam Števko]

Hello everybody,

I added draft of proposed CoC to wiki here: 
http://wiki.openindiana.org/oi/Code+of+Conduct+proposals

I modified the Wiki entry to contain both versions.

Modified version of initial CoC text contains following changes:

- added to "Core principles and expectations:” part:

• Always seek to maintain a welcoming environment for new contributors.
• Welcome new people to the project and guide them in their 
contributions.
• Give them the time you were given when you first joined the community.
• And if you weren't given enough time please set a new example for 
others to live by.
• Be open and transparent so others can participate on an equal footing and 
contribute to the project in their own way.
• Everyone has something to contribute.

- added to “What will not be tolerated:” part:

Discrimination based on gender, race, nationality, sexuality, religion, age or 
physical disability.

- “Reporting violations” part was changed:
• Violations of the CoC should be reported to the distribution 
maintainers via ab...@openindiana.org.
• Neither reporters nor reported persons will, or should be, 
made public.
• Upon receipt of a problem report, the distribution maintainers will 
investigate the issue and determine whether it warrants further action. Any 
further action will be proportional to the severity of the problem.

Changed things are based on former OpenSolaris Code of Conduct and 
solicitations from the OpenIndiana community.

I hope that people are OK with these changes. I also expect this to be the 
final draft unless some comments appear.

Cheers,
Adam

> On Jul 24, 2016, at 5:56 PM, Aurélien Larcher  
> wrote:
> 
> 
> Le 24 juil. 2016 17:17, Nikola M  a écrit :
>> 
>> On 07/24/16 05:10 PM, Nikola M wrote:
>>> As long it is there site is under occupation from that troll document.
>> 
>> And I won't try to change it anymore, since Aurelien objected and want
>> it unchanged for whatever reason it is...
>> Wanting to have document unchanged is obvious obstacle in community
>> process, but hey, you have it..
>> 
> 
> I just object to change without consultation of authors. :)
> 
> Adam, would you mind adding at least a référence to the WIP on the wiki and a 
> line of context  to specify that the proposed document is only a basis and 
> subject to improvement and acceptance by the community ?
> 
>> 
>> ___
>> oi-dev mailing list
>> oi-dev@openindiana.org
>> http://openindiana.org/mailman/listinfo/oi-dev
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> http://openindiana.org/mailman/listinfo/oi-dev



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] OpenIndiana Code of Conduct

[Adam Števko]

Hi Peter,

> On Jul 22, 2016, at 2:00 PM, Peter Tribble  wrote:
> 
> Adam,
> 
> Thanks for doing this. In my view, it's long overdue.

Thanks for you support. It might be long overdue, but rather late than never.  
I hope this step will make former developers come back.


> Comments below.
> 
> As part of a larger effort at providing a more formal governance structure 
> for the OpenIndiana project,
> 
> So, there is a wider context to this. Which is a good thing, but it would be 
> good to have
> that fleshed out. Not necessarily conclusions, but it would be good for the 
> community at
> large to understand what's missing and what's being done about it.

Yes, the wider context exists. The idea is to make every possible step to move 
project out of decline. There are few more things current developer have in the 
pipeline:
  - CoC (debated now),
  - governing board elections,
  - mission statement update,

  - new end-user documentation (based on Michael’s work),
  - oi-userland changes and further simplifications to lower barrier for 
contributing. There will be a call for new package contributions,
  - new ways to try out and develop OI (vagrant boxes, qcow2 images and 
netboot.xyz integration),
  - some infrastructure work (wiki update, long needed cleanup and 
reorganization, infra reinstall and better coverage via more mirrors),
  - forum, so people can communicate and help each other (it seems that mailing 
lists and IRC channels are not sufficient),

  - stable version based on hipster (/dev -> /stable will be a seamless 
transition. So far, plain upgrade works, but zones complicate it a little bit 
and that has to be sorted out).

There is a lot of work to be done, but unless we can get more developers on 
board, not everything can be accomplished in reasonable time. With stable 
release, we might need a few more devs, who could fill the ranks and help with 
maintenance. So I hope that the order of steps is logical and reasonable to 
everybody. To be clear, some things are already happening (mostly technical 
related). Political ones are a matter of discussion of course and shall be 
discussed and further agreed. The idea is to come up with some proposal, which 
could be discussed.

This list is very brief and I could write a blog post detailing every point if 
interested. However, it will take me a few days. Just let me know if you want 
to have it in more details or enough information was provided.

> 
> I’d like to announce on the behalf of OI developers the adoption of an 
> OpenIndiana Code of Conduct. The draft text for this new document can be 
> found at http://www.openindiana.org/community/code-of-conduct/ 
> .
> 
> We would also like to point out this draft document is open to discussion and 
> acceptance by the community.
> Our desire is for the discussion to be civil and for it to center around the 
> verbiage of the Code of Conduct.
> We do not wish for the discussion to go off topic, or question the need for 
> such a document.
> 
> Please compose your thoughts and comment with as few replies as necessary so 
> the community may solidify the final text of this document.
> 
> Overall, I'm happy with most of this. It's about the right length, as well.
> 
> I think you need an explicit reporting mechanism. Something like "email 
> ab...@openindiana.org "
> or the like. (Of course, you need that to be routed somewhere.) And the first 
> statement about
> confidentiality means that the 2nd part about not being made public is 
> redundant. There's also
> no mention of consequences.

Michael and I slightly modified our initial proposal to include your points:
Violations of the CoC should be reported to the distribution maintainers via 
ab...@openindiana.org .
Neither reporters nor reported persons will, or should be, made public.
Upon receipt of a problem report, the distribution maintainers will investigate 
the issue and determine whether it warrants further action. Any further action 
will be proportional to the severity of the problem.
I also discussed your points with Alexander in Saint Petersburg and we came to 
the conclusions that mentioning every possible way to handle punishment would 
be a much longer list. So, we thought that putting it this way is better.
I hope that you are OK with it. If you have any further comments, please let us 
know.

Cheers,
Adam


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] OpenIndiana Code of Conduct

[Adam Števko]

Hi Till,

I added slightly modified draft to 
http://wiki.openindiana.org/oi/Code+of+Conduct+proposals and it contains the 
sentence you wanted, but slightly modified and expanded:

Always seek to maintain a welcoming environment for new contributors.
• Welcome new people to the project and guide them in their 
contributions.
• Give them the time you were given when you first joined the community.
• And if you weren't given enough time please set a new example for 
others to live by.

Modifications come from former OSOL CoC. I hope you like this even better.

Cheers,
Adam

> On Jul 20, 2016, at 10:04 AM, Till Wegmüller <toaster...@gmail.com> wrote:
> 
> On 18.07.2016 23:35, Adam Števko wrote:
>> 
>> Please compose your thoughts and comment with as few replies as
>> necessary so the community may solidify the final text of this document.
>> 
>> Cheers,
>> Adam
>> 
> 
> Hi Adam, Hi Nikola
> 
> Thanks both of you for the work put into this.
> 
> Here are my thought and comments:
> When reading Adams text it refers to a body of Leadership. Both source 
> Projects (FreeBSD and FiFo) have such a Role defined. Do we have that?
> 
> Adams text is more worded towards being a set of rules. Nikolas more in the 
> sense of expectations. I prefer expectations.
> 
> When I read the words "will not be tolerated" it imediatly raises the 
> question what will hapen if i break those? Who punishes and how? In my 
> opinion "Discouraged behaviour" is the better wording.
> 
> I prefer the managing misuse and escalation section over the reporting 
> violations. We have a very friendly community. There should not be a need to 
> involve a third party to resolve issues from the very beginning.
> 
> The very notion of twitter is that everything is public.
> 
> I find the point "Maintain welcoming environment for new contributors and 
> guide them in contributions." very important. I would like to have that in.
> 
> What is the desired outcome of a code of conduct? Should it be a set of 
> rules? Or a set of expectations from each other? Is it assumed to be the same 
> for all codes of conducts? If so should we link to that definition? or do we 
> need to define that?
> 
> 
> Greetings
> Till
> 
> 
> 
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> http://openindiana.org/mailman/listinfo/oi-dev



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] OpenIndiana Code of Conduct

[Adam Števko]

Hi Till,

> On Jul 20, 2016, at 10:04 AM, Till Wegmüller <toaster...@gmail.com> wrote:
> 
> On 18.07.2016 23:35, Adam Števko wrote:
>> 
>> Please compose your thoughts and comment with as few replies as
>> necessary so the community may solidify the final text of this document.
>> 
>> Cheers,
>> Adam
>> 
> 
> Hi Adam, Hi Nikola
> 
> Thanks both of you for the work put into this.
> 
> Here are my thought and comments:
> When reading Adams text it refers to a body of Leadership. Both source 
> Projects (FreeBSD and FiFo) have such a Role defined. Do we have that?

Not anything official right now. Every decision was made by one of the 
contributors and we tried to reach a consensus. If the decision was too 
important, project contributors consulted those topics with various people and 
tried to do their best. However, most things were mostly technical and not 
political. Unless leader steps up or different governing body is found, there 
isn’t anything. The deciding comes as a part of moving the project forward.

I have also discussed this topic with Alexander today and we both concluded 
that we has just killed the time with it. We are small developer community, 
(mostly) nice to each other and try to help. I also think that every 
contributor has found his place within a project already. If any proposal came 
from me, I’d just make the present situation official, but there are certainly 
drawbacks to it.

> Adams text is more worded towards being a set of rules. Nikolas more in the 
> sense of expectations. I prefer expectations.

Problem with expectations in Nikola’s list is that majority of them are already 
in practice and the situation is out of hands.

> When I read the words "will not be tolerated" it imediatly raises the 
> question what will hapen if i break those? Who punshes and how? In my opinion 
> "Discouraged behaviour" is the better wording.

The point of using “strong” words is to show that we take it seriously. If 
rules are broken, the situation is going to be handled privately to avoid any 
(more) drama on the mailing list and ensure that the problem is solved. And who 
punishes? The CoC states that distribution maintainers are the one to do so. We 
can change it as it is a draft. Perhaps, somebody could volunteer. I can assure 
you that nobody wants to do it and behave like a teacher in the kinder garden. 
Fortunately, the community hadn’t had to solve any serious issues and there 
weren’t any

> I prefer the managing misuse and escalation section over the reporting 
> violations. We have a very friendly community. There should not be a need to 
> involve a third party to resolve issues from the very beginning.
> 
> The very notion of twitter is that everything is public.

Twitter as a medium has private DM and it's rather usual to use it. It just an 
another communication channel. If you insist, we can remove it.

> I find the point "Maintain welcoming environment for new contributors and 
> guide them in contributions." very important. I would like to have that in.

I’ll add it, thanks.

> What is the desired outcome of a code of conduct? Should it be a set of 
> rules? Or a set of expectations from each other? Is it assumed to be the same 
> for all codes of conducts? If so should we link to that definition? or do we 
> need to define that?

The whole idea behind the code of conduct is to show the community and the 
outside world that we are a community of people, who don’t tolerate toxic 
people. There are multiple problems with such people, most present in OI:

- community members are unsubscribing from the list - there has been too much 
drama in the past few months and it needs to be stopped. Nobody wants to deal 
with toxic people. You could see one example right in this email thread.
- public debates - many things are debated in the private because people want 
to work on the project and have something done. If you send out an email to 
oi-dev mailing list, the email is quickly going to hijacked or made off-topic. 
Who has the energy to deal with it every time?

With CoC in place, we can simply show the potential new users and also those, 
who unsubscribed that situation changed and that we mean it seriously. After 
all, everybody wants to have a peaceful and enjoyable time while 
using/developing OI.
However, that can’t be reached while toxic people are present.

Cheers,
Adam


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] OpenIndiana user survey

[Adam Števko]

Hi,

On behalf of the OI developers, I’d like to ask all the community members and 
developers to complete a short OpenIndiana survey form located at 
https://docs.google.com/forms/d/1k2LNzxQxGdUZ7joL_tI3Aid_fzTGPxSDEAp83PbCmus/viewform
 
.

This will give us answers to several questions and the information will help us 
improve OpenIndiana.

Completing this form should not take more than 15 minutes and will help us 
tremendously, so I’d like to encourage all people on both lists to participate.

I’ll leave the form open till the end of August  2016.

Thanks for all answers!

Cheers,
Adam



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] how to reg wiki.openindiana.org ?

[Adam Števko]

HI Michael,

mkdocs is very nice! I used it for a few projects already and it’s easy to 
setup and great for writing documentation. I’m looking forward seeing  some 
demonstration.

Cheers,
Adam

> On Jun 8, 2016, at 11:28 AM, Michael Kruger  wrote:
> 
> More recently I teamed up with some *nix enthusiasts from outside the project 
> and we have started using a different framework (MKDOCS), and a different 
> markup language (Markdown) but have not yet published the results.



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] Vagrant

[Adam Števko]

Hello guys,

while working on OI infra I came across a need to rapidly provision OI hipster 
boxes. 

I'd be interested in how many people actually use vagrant and would do on Oi 
hipster. If there is enough interest, I might package it and bring it to Oi. 
I'll also need testers. We will be able to build VirtualBox base boxes only (I 
don't use vmware on OS X).

I'll also start producing official OI vagrant boxes.

Let me know the interest in the package and how many people are to help test 
vagrant on Oi.

Cheers,
Adam
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] OpenIndiana Docs - updated

[Adam Števko]

+1

> On 16 May 2016, at 09:22, Alexander Pyhalov  wrote:
> 
>> On 05/16/2016 09:43, Nikola M wrote:
>>> On 05/16/16 05:58 AM, Michael Kruger wrote:
>>> Hello All,
>>> 
>>> Reporting my progress so nobody gets the idea this little technology
>>> demonstration project has been abandoned. Far from it, there has been
>>> continued development.
>>> 
>>> See it all here: http://makruger.github.io/website/
>> 
>> STOP calling your private site "Openindiana docs" they are not , simply
>> because you just wrote something on your site and you just say so.
>> Working on things alone and then coming up with aspiration to turn
>> around everything is not friendly behavior to Openindiana and it's
>> community.
> 
> Please, Nikola, stop it...  If you have technical notices to the docs, 
> please, post them. Michael is trying to do something which will become 
> official OI docs site one day. He has posted links to get feedback on his 
> work. Once we are satisfied with the site, it will be moved to OI 
> infrastructure. At least, it's the plan.
> 
> We need technical reviews, not personal attacks.
> 
> -- 
> Best regards,
> Alexander Pyhalov,
> system administrator of Southern Federal University IT department
> 
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> http://openindiana.org/mailman/listinfo/oi-dev

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

Re: [oi-dev] Go 1.6.2 available

[Adam Števko]

Hello,

there is one known issue, which we are working on and that go get might fail 
for some sites. Workaround for now is to run this command:

curl -o /etc/certs/ca-certificates.crt https://curl.haxx.se/ca/cacert.pem 


The ca-certificates.crt will be delivered by ca-certificates package, but it 
might take a few days till the fix is pushed.

If you find any other bugs, please report them. I tested this package by 
building go and syncthing.

Cheers,
Adam

> On May 5, 2016, at 4:26 PM, Aurélien Larcher  
> wrote:
> 
> Hi,
> yesterday Go 1.6.2 was pushed to Hipster: this is a vanilla install without 
> extra package.
> 
> helios> go version
> go version go1.6.2 solaris/amd64
> 
> Our oi-userland component:
> 
> https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/developer/golang-16
>  
> 
> 
> is based on the component from solaris-userland and benefit from their 
> porting effort on Go 1.5. Warm thanks go to them, as their work makes Go 
> possible on OpenIndiana.
> 
> The Go distribution is installed in /usr/lib/golang-16 and /usr/bin/go is a 
> symlink.
> As mentioned, it does not come with extra-package: if there is interest, they 
> can be added to oi-userland but we need to think about adding Makefiles 
> specific to Go packages.
> 
> Thanks to Sergey and Adam for reviewing, testing and contributing fixes to 
> the component.
> Best regards
> 
> Aurélien
> 
> 
> --
> ---
> Praise the Caffeine embeddings
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> http://openindiana.org/mailman/listinfo/oi-dev



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] oi-userland categories

[Adam Števko]

Sound reasonable. This would also make oi-userland more like freebsd 
ports/pkgsrc.

+1 from me.

Adam

> On Feb 18, 2016, at 3:43 PM, Aurélien Larcher  
> wrote:
> 
> Hello,
> 
> I suggest:
> 1) agree on several (~20 ) categories (something like in pkg-src);
> 2) move individual components to corresponding categories as they are touched;
> 3) avoid creating new top-level components;
> 4) allow creating sub-categories.
> 
> As for top-level categories, I'd like to see something like
> 
> archivers
> closed  # closed source components
> databases
> devel  # development tools and libraries
> desktop-environments # gnome, enlightenment\
> deskutils
> encumbered
> fonts
> games
> graphics
> lang   # languages and language modules
> inputmethod
> meta-packages
> multimedia
> openindiana # illumos and OI-specific software
> scientific
> shells
> sysutils
> textproc
> www
> x11
> 
> 
> What do you think?
> 
> Agreed.
> For some categories the FMRI gives already a prefix that could be used as 
> directory name e.g. 'devel' -> 'developer', 'archivers' -> 'archiver' 
> (without appended 's'), 'textproc' -> 'text', we also have 'network' and some 
> other categories.
> Even if is not 1:1 maybe we should avoid creating new labels when existing 
> can be used, regardless of how much we like them, and ensure some kind of 
> consistency.
> 
> Do you want subcategories in x11 as well to follow upstream ?
> The 'fonts' directory will exist in x11 as well since ttf fonts are 
> delivered, should it be moved therein ?
> 
> 
> 
> 
> 
> 
> --
> Best regards,
> Alexander Pyhalov,
> system administrator of Southern Federal University IT department
> 
> ___
> oi-dev mailing list
> oi-dev@openindiana.org 
> http://openindiana.org/mailman/listinfo/oi-dev 
> 
> 
> 
> 
> --
> ---
> Praise the Caffeine embeddings
> ___
> oi-dev mailing list
> oi-dev@openindiana.org 
> http://openindiana.org/mailman/listinfo/oi-dev 
> 


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] oi-userland component build and directory structure

[Adam Števko]

Hi,

search some example Makefikes for cloney. It will link source directory 
contents to the build one. 

However, isn't myfile.h generated by som configuration command?

Cheers,
Adam

> On 19 Jan 2016, at 04:35, benta...@chez.com wrote:
> 
> Hi,
> I'm trying to build simple software as packages.
> If I understand correctly, the way the oi-userland works is package is 
> compiled in a build directory different from the source tarball extraction.
> 
> My issue is that some include files are not transferred from the source to 
> the build directory and the code refer to "#include " so the make 
> fails whereas going into the source directory and perform the build works 
> fine.
> 
> How would be the oi way to tackle this ?
> 
> Ben
> 
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> http://openindiana.org/mailman/listinfo/oi-dev

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

Re: [oi-dev] Hipster Build Zone?

[Adam Števko]

Hi,

build-essential is everything needed for package building (compiler, make, 
libraries etc). Packages ypu want to build may have different dependencies, 
which needs to be installed.

Cheers,
Adam

> On Jan 13, 2016, at 9:43 PM, Andreas Wacknitz  wrote:
> 
> Hi,
> 
> Is there any documentation on how to prepare a build zone for Hipster 
> development?
> 
> I have installed a build zone like it is proposed on the wiki (eg. install 
> build-essential).
> Alas I am not able to build many of the userland packages. I found out that 
> there still
> seem a lot of prerequsites missing (eg. for building GNOME packages like 
> zenity).
> 
> So at the moment it's hard for me to distinguish real problems from problems 
> due to missing
> packages in the build zone. I want to avoid building in the GZ (IMO it would 
> make zones
> worthless).
> So, is there any receipt to follow in order to install all prerequisites?
> 
> Further: How can I install the whole GNOME desktop environment?
> 
> Regards
> Andreas
> 
> 
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> http://openindiana.org/mailman/listinfo/oi-dev



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] libjpeg-turbo and VLC

[Adam Števko]

Hi,

maybe you will be interested in other codecs such as x264 or libvpx, which can 
be found in ec-userland: 
https://github.com/everycity/ec-userland/tree/master/components
Those components are already in oi-userland-like format and need only minor 
tweaks (p5m modifications as we use different prefix).

Hope this helps.

Merry christmas!

Adam

> On Dec 24, 2015, at 12:41 AM, Aurélien Larcher  
> wrote:
> 
> Also I should add support for opus.



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Issue building the illumos component on OpenIndiana

[Adam Števko]

Hi,

welcome to the community. Are you using /dev version of OpenIndiana? If so, I’d 
recommend switching to hipster. ISOs can be found here: 
http://dlc.openindiana.org/isos/hipster/ 
.

For making illumos development on OI hipster easy, there is a build-essential 
package, which you will need to install right after OI installation via:

pkg install build-essential

If there is anything else, just ask.

Cheers,
Adam

> On Nov 14, 2015, at 9:15 PM, Kirtikar Kashyap  wrote:
> 
> Hi,
> 
> My name is Kirtikar Kashyap and along with my team-mate Aditya Shantanu, we 
> plan to add reflink support on ZFS for illumos. We are doing this as a part 
> of a course at Carnegie Mellon University.
> 
> We are trying to build the illumos component to get started with testing but 
> we are unable to build the environment. We are following this link 
>  to build 
> illumos.
> 
> Even upon following all the steps, we are getting multiple instances of Error 
> code 127 and Error code 1.
> 
> I have put the mail_msg and the nightly.log files here 
> .
> 
> Any help would be appreciated.
> 
> 
> Regards,
> Kirtikar Kashyap
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> http://openindiana.org/mailman/listinfo/oi-dev



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] Hipster 2015.03.30 ISOs torrents

[Adam Števko]

Hi,

torrents for new hipster ISO images are published on 
http://dlc.openindiana.org/torrents http://dlc.openindiana.org/torrents.

Links:

http://dlc.openindiana.org/torrents/OI-hipster-gui-20150330.iso.torrent 
http://dlc.openindiana.org/torrents/OI-hipster-gui-20150330.iso.torrent
http://dlc.openindiana.org/torrents/OI-hipster-gui-20150330.usb.torrent 
http://dlc.openindiana.org/torrents/OI-hipster-gui-20150330.usb.torrent

http://dlc.openindiana.org/torrents/OI-hipster-text-20150330.iso.torrent 
http://dlc.openindiana.org/torrents/OI-hipster-text-20150330.iso.torrent
http://dlc.openindiana.org/torrents/OI-hipster-text-20150330.usb.torrent 
http://dlc.openindiana.org/torrents/OI-hipster-text-20150330.usb.torrent

I am seeding from single machine, so the initial download might take some time 
to start, but speeds should be reasonable.

Cheers,
Adam

—
PGP Fingerprint: 00EF 547B 63CC 8FB0 02F4 C654 6843 7E0C F3E7 FCC1



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] PostgreSQL 9.4 and marking 8.4 obsolete

[Adam Števko]

Nice! Thanks for your work.

Cheers,
Adam

 On Dec 19, 2014, at 9:06 PM, Alexander Pyhalov a...@rsu.ru wrote:
 
 Hello.
 I'd like to inform you that PostgreSQL 9.4 is available in OI Hipster package 
 repository.
 Also note, that currently we ship 3 PostgreSQL versions - 9.3, 9.4 and 8.4. 
 PostgreSQL 8.4 has reached its EOL at July. I'm going to mark this package 
 obsolete in a month. If you still have 8.4 installations (which is unlikely), 
 plan for updates on the holidays :).
 
 --
 System Administrator of Southern Federal University Computer Center
 
 ___
 oi-dev mailing list
 oi-dev@openindiana.org
 http://openindiana.org/mailman/listinfo/oi-dev



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] dmarc test (last)

[Adam Števko via oi-dev]

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

Re: [oi-dev] F*ck Yahoo,AOL get us back our mailing lists

[Adam Števko via oi-dev]

Hi guys,

the issue caused by Yahoo and AOL DMARC policy was solved. If there are any
other problems, just let me know either via email or IRC (xenol).

Cheers,
Adam


On Thu, May 22, 2014 at 5:18 PM, OpenIndiana Developer mailing list 
oi-dev@openindiana.org wrote:

 I don't f care about Yahoo and AOL mail settings,
 we now have mailing list where Noone can se who is posting what message!

 I got under impression, that thing got fixed back. But I see again new
 massages posted from Who knows who, because we dont'have FROM header
 anymore!
 This will KILL mailing lists and we must refuse this stupidity at least on
 our mailing lists.

 People at Yahoo and AOL, make new accounts and re-subscribe.
 Same goes also for me if Gmail goes that way,
 let's have our mailing lists back!

 Let's BOUNCE Yahoo and AOL and have mailing list for normal mail providers.


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

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

Re: [oi-dev] [developer] GSoC? Decision time....

[Adam Števko]

Hi,

another possible project for GSoC could be adding TRIM support in illumos. 
According to my information, only some sd driver modifications  are needed.
SSDs are becoming  more widespread and illumos is the only OS which does not 
have proper TRIM support I know about.

Is this a suitable task for GSoC? I suppose there are many engineers on the 
list with needed expertise, who could mentor a student.

Cheers,
Adam

On Feb 15, 2014, at 1:35 PM, ken mays maybird1...@yahoo.com wrote:

 Hello,
  
 Note: OI is nothing more than a 'server OS' distribution with additional 
 software. Leave it at that.
  
  
 OI surely can mentor students as there are 'students' that already work on 
 that project.
  
 As for illumos, I note that there 'should be' a general focus on projects 
 that a group of students can
  work on for the summer or accomplish in the 3-month span.
  
 Porting device drivers is such a task. Many 'experts' here on kernel and 
 device driver programming.
  
 I'd like to see students work on USB 3.1/Thunderbolt 2 drivers for illumos. A 
 few storage partners
 use illumos and supporting device drivers related to storage makes sense - 
 not so much graphic drivers. 
  
 That brings into focus the reality of how illumos is being used on the 
 'bigger scale' of things. The
 illumos kernel developers that can mentor students based on projects they may 
 work on internally
 and can hopefully lead that work into future jobs for the student or a great 
 job reference.
  
 As for OI GSoC, a project like 'Implement the 2013Q3 Intel Graphics Stack' is 
 a great project which involves
 upstream's Xnv implementation.
  
 Note: I'd donate high-end graphic cards/workstations to students 
 accomplishing those goals.
  
 Sincerely,
 Ken Mays
  
  
   
 
 
 On Friday, February 14, 2014 2:53 PM, Garrett D'Amore garr...@damore.org 
 wrote:
 Lets all agree that we don’t want any simple efforts to just package software 
 as part of GSoC, whether for any distribution.
 
 Let’s also agree that if some very compelling project (forward and innovative 
 thinking, not just making illumos try to compete with Linux on Linux’s terms) 
 for Desktop technology comes up, we can evaluate such a project on its 
 merits, and consider it as a candidate for GSoC slots.
 
 Let’s also agree that opinions of folks not actively volunteering to mentor 
 really don’t count for much here.   Its the time on the part of the mentors 
 and admin, and Google’s money at stake.  Unless a project poses a risk to the 
 “reputation” for illumos, it shouldn’t matter to other parties.
 
 Thanks.
 
 -- 
 Garrett D'Amore
 Sent with Airmail
 
 On February 14, 2014 at 9:19:35 AM, Keith Wesolowski 
 (keith.wesolow...@joyent.com) wrote:
 On Fri, Feb 14, 2014 at 04:20:43PM +, Alasdair Lumsden wrote: 
 
  However there are plenty of people who do want to run it on the desktop, 
  and who are you to tell them they should not do this? 
 
 I'm not telling people what to work on, since they're not employed by 
 me. I'm trying to make sure that the illumos community represents 
 itself favourably and accurately to the wider world, especially when 
 trying to recruit young engineers to work on our operating system. 
 
 
 --- 
 illumos-developer 
 Archives: https://www.listbox.com/member/archive/182179/=now 
 RSS Feed: 
 https://www.listbox.com/member/archive/rss/182179/21239177-3604570e 
 Modify Your Subscription: https://www.listbox.com/member/?; 
 Powered by Listbox: http://www.listbox.com
 
 
 illumos-developer | Archives  | Modify Your Subscription  
 
 
 ___
 oi-dev mailing list
 oi-dev@openindiana.org
 http://openindiana.org/mailman/listinfo/oi-dev



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] New hipster ISOs (bnx and bnxe incl.)

[Adam Števko]

Hi people,

I created new hipster ISOs. These ISOs contain new network drivers (bnx, bnxe) 
and their support should work out of the box.
Give them a test drive.

Links:

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

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

Checksums:

eb7b3be94f392c9f5fc72f523eaf25fd  OI-hipster-gui-20140214.iso
f104a18902d4f60cdeabc582729f80df  OI-hipster-gui-20140214.usb
f512c428972eb392f84934474b79fc97  OI-hipster-text-20140214.iso
1eee58b6ca5eaddbff28bc243de11560  OI-hipster-text-20140214.usb

If you have any problems, please let me know.

Cheers,
Adam

—
PGP Fingerprint: 00EF 547B 63CC 8FB0 02F4 C654 6843 7E0C F3E7 FCC1



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] IMPORTANT: dev01.uk.oi.o cleanup

[Adam Števko]

Hi folks,

I need to create new development zones on dev01 for people, but I have no space 
left. Therefore, I need to do some housekeeping.

The following zones will erased today (already agreed with their owners):

   - buffyg2.uk.openindiana.org configured /zones/buffyg2.uk.openindiana.org 
ipkg excl
   - aszeszo.uk.openindiana.org configured /zones/aszeszo.uk.openindiana.org 
ipkg excl
   - alasdair2.uk.openindiana.org configured 
/zones/alasdair2.uk.openindiana.org ipkg excl
   - buffyg.uk.openindiana.org configured /zones/buffyg.uk.openindiana.org ipkg 
excl  
   - pkgsrcbuild.uk.openindiana.org configured 
/zones/pkgsrcbuild.uk.openindiana.org ipkg excl  

I plan to delete these zones next week:
 - jeffpc.uk.openindiana.org configured /zones/jeffpc.uk.openindiana.org ipkg   
  excl  
 - cellis2.uk.openindiana.org configured /zones/cellis2.uk.openindiana.org ipkg 
excl 
 - saablover.uk.openindiana.org configured /zones/saablover.uk.openindiana.org 
ipkg excl  
 - drlou.uk.openindiana.org configured /zones/drlou.uk.openindiana.org ipkg 
excl  
 - gber.uk.openindiana.org configured /zones/gber.uk.openindiana.org ipkg 
excl  
 - samba.uk.openindiana.org installed  /zones/samba.uk.openindiana.org ipkg 
excl  
 - alasdair3.uk.openindiana.org configured /zones/alasdair3.uk.openindiana.org 
ipkg excl  
 - npx.uk.openindiana.org configured /zones/npx.uk.openindiana.org  ipkg 
excl  

If you happen to be an owner of one of those zones, please let me know by 
emailing me off list with the name of the zone and I will keep it.

Cheers,
Adam


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADS UP] Python 2.7 modules are also built by default

[Adam Števko]

Alexander,

well done and thanks for your efforts! Is python27 patched to support DTrace?

Cheers,
Adam

 On 24 Jan 2014, at 16:14, Alexander Pyhalov a...@rsu.ru wrote:
 
 Hello, people.
 
 On this week I've enabled building modules for Python 2.7 in oi-userland. The 
 one missing component is libxslt, it has too many external dependencies to 
 rebuild it now.
 So, we don't have library/python-2/libxsl-27 .
 
 Also, I've set PYTHON_VERSIONS to 2.6 2.7, in shared-macros.mk, which means 
 that now your components based on setup.py.mk are expected to provide both 
 Python 2.6 and Python 2.7 versions. Use PYVER manifests or provide  x-27.p5m 
 file (in addition to x-26.p5m and common x.p5m).
 -- 
 Best regards,
 Alexander Pyhalov,
 system administrator of Computer Center of Southern Federal University
 
 ___
 oi-dev mailing list
 oi-dev@openindiana.org
 http://openindiana.org/mailman/listinfo/oi-dev


smime.p7s
Description: S/MIME cryptographic signature
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] New pkg5 in the repo

[Adam Števko]

Hi,

On Dec 10, 2013, at 6:12 AM, Alexander Pyhalov a...@rsu.ru wrote:

 Guys, thank you for this work.
 It's really great. At least it should allow us to continue work on python 2.7.
 However, what about testing?
 
 Adam Števko писал 10.12.2013 05:08:
 Hi,
 thanks for finishing my work (busy till end of this week with my master’s).
 Alp and I didn’t want to push this yet into the main hipster repo,
 because we were afraid of breakage.
 I tried to update to the new IPS (not this version, but version I
 worked with) and I failed to boot. As I recall correctly there was a
 problem with inconsistent system repository (I don’t have any screen
 saved, so I am entirely sure, but it was something with system
 repository inconsistency).
 
 Was it fixed? Or did it just disappear?

I haven’t bothered with this yet as I wanted to start solving IPS issues once 
it is published in the test repository, as we agreed.

Adam




signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Bypassing check for inexistent python .pyc files in IPS manifests.

[Adam Števko]

HI guys,

I creaetd IPS packaging FAQ on the wiki and added this question. 

URL: http://wiki.openindiana.org/oi/IPS+Packaging+FAQ

I also encourage other people to add other questions and answers there. This 
way, we can build a comprehensive list over time and solving troubles will be 
easier for people/newcomers. 

Cheers,
Adam

On Nov 18, 2013, at 8:55 AM, Aurélien Larcher aurelien.larc...@gmail.com 
wrote:

 Hi Alexander,
 thank you for your quick answer !
 In this case indeed there should not be a .pyc file.
 Is there a place on the wiki where this kind of information could be added ?
 Best regards,
 
 Aurélien
 
 
 On Mon, Nov 18, 2013 at 8:46 AM, Alexander Pyhalov a...@rsu.ru wrote:
 Hello.
 
 
 On 11/18/2013 11:34, Aurélien Larcher wrote:
 
 After looking for a solution I came across the following solution to
 indicate not to seek a .pyc file:
 
 file path=usr/lib/Modules/$(COMPONENT_VERSION)/init/python.py
 pkg.tmp.autopyc=false
 
 Is it correct or is there a preferred way to achieve that ?
 Best regards,
 
 
 Yes, usually you have two options: make package generate *.pyc files or set 
 this option. Sometimes package just is not supposed to do it. In this case 
 autopyc=false is a solution.
 -- 
 Best regards,
 Alexander Pyhalov,
 system administrator of Computer Center of Southern Federal University
 
 
 
 -- 
 ---
 LARCHER Aurélien| KTH, School of Computer Science and 
 Communication
 Work: +46 (0) 8 790 71 42   | Lindstedtsvägen 5, Plan 5
 Mob.: +46 (0) 7 09 46 40 17 | 100 44 Stockholm, SWEDEN
 ---
 Praise the Caffeine embeddings ...
 ___
 oi-dev mailing list
 oi-dev@openindiana.org
 http://openindiana.org/mailman/listinfo/oi-dev



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Numpy and Scipy

[Adam Števko]

 directory 
 /afs/nada.kth.se/dept/na/ctl/pkg/@sys/fiat/0.3.4 contains the installed module
 
 /afs/nada.kth.se/dept/na/ctl/pkg/@sys/fiat/0.3.4/lib/python2.7/site-packages/FIAT/
 
 I could then provide modulefiles allowing to switch from one bundle (like 
 mpich2-gcc) to another.
 
 The main issue is: in which prefix shoud I put everything ? e.g is 
 /usr/lib/$(ARCH)/$(MPI)/$(COMPILER) suitable of not ? or should we have 
 /usr/mpich/$(COMPILER) and /usr/openmpi/$(COMPILER) prefixes ?
 
 Handling this is usually ugly even with Debian and FreeBSD.
 
 I also compiler Enlightenment 17 and have the same thought, what should be 
 the prefix for a Desktop Environment.
 Same question applies to JNI modules.
 
 I think Hipster would benefit from guidelines to specify install prefix for 
 different kinds of software.
 
 Thank you in advance.
 Best regards,
 
 Aurelien
 
 
 
 
 
 
 
 
 On Mon, Sep 16, 2013 at 12:21 PM, Adam Števko adam.ste...@gmail.com wrote:
 Hi Aurelien,
 
 how is it going? Do you need any help?
 
 Cheers,
 Adam
 
 Begin forwarded message:
 
 From: Aurélien Larcher aurelien.larc...@gmail.com
 Subject: [oi-dev] Numpy and Scipy
 Date: September 8, 2013 6:36:57 PM GMT+02:00
 To: OpenIndiana Developer mailing list oi-dev@openindiana.org
 Reply-To: OpenIndiana Developer mailing list oi-dev@openindiana.org
 
 Hi everyone,
 since the numpy python package available in hipster seems broken 
 (segfaults), I installed the latest stable 1.7.0 compiled with gcc, without 
 a linear algebra backend.
 So I intend to add latest numpy, scipy (and atlas for the backend) in 
 oi-userland if it is ok.
 
 How does it fit in the way python modules are packaged ? Should they be 
 added to the python folder ?
 Should 32 bit and 64 bits be both provided or only one of them ?
 
 What about gdb, is it possible to upgrade to 7.x to get python extensions or 
 are there any known showstoppers ? (I installed the latest gdb with the 
 'historical' patches).
 
 I have also a few numerical libraries pending that I converted from my SFE 
 specs. 
 Best regards,
 
 Aurelien
 
 -- 
 ---
 LARCHER Aurélien| KTH, School of Computer Science and 
 Communication
 Work: +46 (0) 8 790 71 42   | Lindstedtsvägen 5, Plan 4
 Mob.: +46 (0) 7 09 46 40 17 | 100 44 Stockholm, SWEDEN
 ---
 Praise the Caffeine embeddings ...
 ___
 oi-dev mailing list
 oi-dev@openindiana.org
 http://openindiana.org/mailman/listinfo/oi-dev
 
 
 
 
 -- 
 ---
 LARCHER Aurélien| KTH, School of Computer Science and 
 Communication
 Work: +46 (0) 8 790 71 42   | Lindstedtsvägen 5, Plan 5
 Mob.: +46 (0) 7 09 46 40 17 | 100 44 Stockholm, SWEDEN
 ---
 Praise the Caffeine embeddings ...



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Barman packaging

[Adam Števko]

We don't have root account, either. Root is created as a role if you create a 
regular user during the installation. If you don't that root is an account as 
obviously you need a way to log into the system.

 On 7 Nov 2013, at 09:03, Nikola M. minik...@gmail.com wrote:
 
 On 11/ 7/13 08:39 AM, Alexander Pyhalov wrote:
 
 The most interesting part is that barman has to run rsync with postgres euid 
 on remote site (to access DB files ) and with barman euid on local (to 
 access backup files). I think that converting postgres from role to user is 
 more straightforward than trying to create necessary RBAC policy.
 
 I think that local implementations and needs should not dictate what will be 
 changed in OS distribution itself.
 If people don't know how to use RBAC they should learn it (me included)
 if programs needed to run on OI don't support platform, they shoud be patched 
 to work right.
 
 I don't understand why I should loose PostgreSQL role on all systems I would 
 probably install in the future, because someone personally had a problem with 
 one program not made for the platform.
 And what it has to do with that particular implementation of external program
 and what rsync have to do with Solaris roles.
 
 It could be written on wiki how to do that, it could be written on package 
 description, it could be written on the program manual how to make it work
 but the OS should not be slave of the application and kill existing 
 functionality that people rely upon, just to be able to run one additional 
 program without patching it for the platform.
 
 Large installations usually have their own mirrors and changes that for some 
 reason some local admin thinks theya re needed for them, and not for the rest 
 of the world,
 can land on their internal mirror.
 
 Besides, we have 'zfs send' and using rsync for that is sort of stupid to me.
 Why that app should not be patched to use zfs snapshots?
 
 You could think this way: everything could be on roles in the future, like it 
 is in Solaris11.
 They killed root account completely. And we still have root account, and that 
 is maybe good thing,
 but that does not mean we should start killing roles because we find it 
 interesting at the moment to run some additional app.
 Let's think our way and not turn everything in Linux.
 
 So I think it is not such good idea to kill one large-known functionality, 
 just to satisfy random App without patching it.
 Are we actually suffering for not having established review and discussion 
 process before implementing changes?
 
 
 ___
 oi-dev mailing list
 oi-dev@openindiana.org
 http://openindiana.org/mailman/listinfo/oi-dev


smime.p7s
Description: S/MIME cryptographic signature
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] uid/gid policy

[Adam Števko]

Hi,

something like this already exists. At least it was created on first userland 
hackathion.

http://wiki.openindiana.org/oi/UIDs+and+GIDs

This should be the list. However, I think that not many are aware of it.

Cheers,
Adam

—
PGP Fingerprint: 00EF 547B 63CC 8FB0 02F4 C654 6843 7E0C F3E7 FCC1

On Nov 7, 2013, at 10:37 AM, Alexander Pyhalov a...@rsu.ru wrote:

 Hello.
 Do we have (or need) some policy for assigning gids and uids delivered by IPS 
 packages? What about at least creating a wiki page with known reserved uids 
 and gids?
 -- 
 Best regards,
 Alexander Pyhalov,
 system administrator of Computer Center of Southern Federal University
 
 ___
 oi-dev mailing list
 oi-dev@openindiana.org
 http://openindiana.org/mailman/listinfo/oi-dev



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] uid/gid policy

[Adam Števko]

Hi,

I added openvpn hid 62 (I forgot about) and it is up-to-date now. You can 
assign UIDs/GIDs from this table, but please don’t forget to update it like i 
did. 

I wanted to propose to raise user ids start from 1000, but I was stopped with 
existing installs. So we are stick to UIDs under 100, which is needed for 
backwards compatibility.

However, the available number of UIDs might seem to be low. Delivering RBAC 
role for every service sounds like a solution, but it most cases it’s tricky.

For example, openvpn can drop its privileges itself. It needs to be started as 
a root, so it can create/delete tun/tap interfaces. If I start it with openvpn 
role in SMF, it complains that it can’t manipulate with tun/tap interface.
There is a solution to this and to specify privileges, but I pretty that is 
something most people won’t do and it’s easier to deliver ordinary user 
accounts rather than roles.

IMHO, we should go the way of creating RBAC roles and specifying needed 
privileges. It’ adds some complexity, but on the other hand we are making a use 
of technology illumos provides, which I see as a benefit.

Any other thoughts on this?

Cheers,
Adam

On Nov 7, 2013, at 2:23 PM, Alexander Pyhalov a...@rsu.ru wrote:

 On 11/07/2013 17:12, Adam Števko wrote:
 Hi,
 
 something like this already exists. At least it was created on first 
 userland hackathion.
 
 http://wiki.openindiana.org/oi/UIDs+and+GIDs
 
 This should be the list. However, I think that not many are aware of it.
 
 Cheers,
 Adam
 
 
 Is this page is up to date (or a kind of)? What about assigning additional 
 uids? For, example, could I take the first unreserved (e.g., 91)? What will 
 we do when we run out of 100 lower uids?
 -- 
 Best regards,
 Alexander Pyhalov,
 system administrator of Computer Center of Southern Federal University



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Barman packaging

[Adam Števko]

Hi,

My idea is to convert postgres role to user (uid 90 afaik) and create a profile 
PostgreSQL Management, which can be used for barman needs once it is assigned 
to some user.

I am not sure if IPS can assign profiles to users, but doing that would be much 
easier for the user than to find all the pitfalls himself.

RBAC integration into userland is something we should generally agree on and 
try to write some best practices into wiki.

Are there any thoughts why the solution I propose is wrong? DB simply gets the 
user and pgsql mgmt profile will exists and it's up to user to assign it to an 
user account, which he wants.

Cheers,
Adam


 On Nov 6, 2013, at 3:26 PM, Alexander Pyhalov a...@rsu.ru wrote:
 
 Hello.
 Have a question on packaging Barman PostgreSQL backup manager.
 
 Usually when providing software we expect that it works at least in some way 
 with minimal manual configuration. However, it seems barman suggests 
 accessing PostgreSQL data directories using rsync+ssh.
 By default this attempt will fail (even if ssh is configured in a necessary 
 way), because postgres is a role, not a user (and to find out what's wrong 
 may be problematic, for example, for me it took about an hour to configure 
 minimal barman installation and find out what's wrong)
 So I have a question - what's better?
 Deliver just software (and perhaps a note in a wiki) and allow user to find 
 all pitfalls himself or at least change postgres to be a user (not a role) 
 with perhaps some incompatibility disadvantage and not so secure 
 configuration by default...
 -- 
 Best regards,
 Alexander Pyhalov,
 system administrator of Computer Center of Southern Federal University
 
 ___
 oi-dev mailing list
 oi-dev@openindiana.org
 http://openindiana.org/mailman/listinfo/oi-dev

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

Re: [oi-dev] Please update tuntap in SFE

[Adam Števko]

Hi,

an up-to-date tuntap with openvpn is available in hipster. Building it for /dev 
should not be hard component Makefiles can be reused.

Hope that helps. 

Cheers,
Adam

 On Nov 3, 2013, at 1:56 PM, Jim Klimov jimkli...@cos.ru wrote:
 
 On 2013-11-03 12:34, Jim Klimov wrote:
 Hello all, and probably primarily Milan :)
 
   The TUNTAP package in the SFE repository markets itself as version
 1.3.0, but the loaded module reports that it is 1.1.0. I've fetched
 the tuntap/src package, and apparently it includes an older tarball
 of the sources (Jul 2011, timeframe long before 1.3.x indeed) which
 does not have the TCP watermark fixes of 1.3.0 and later, that boost
 performance of the OpenVPN tunnels noticeably.
 
 Looking at the spec-file, I see where the old source may be coming from:
 
 %define src_name tuntap
 %define src_url http://www.whiteboard.ne.jp/~admin2/tuntap/source/%{src_name}
 
 This path does indeed contain a copy of the code, and of obsolete one
 at that (probably the one used to make the package as of now).
 
 The automatic tarball to current source is:
  https://github.com/kaizawa/tuntap/archive/master.tar.gz
 Which saves itself as tuntap-master.tar.gz
 
 //Jim
 
 
 ___
 oi-dev mailing list
 oi-dev@openindiana.org
 http://openindiana.org/mailman/listinfo/oi-dev

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

Re: [oi-dev] Wiki can't delete comment

[Adam Števko]

Hi,

I deleted the comment. i am looking into the issue with you guys not being able 
to delete the comments. I will see what I can do.

Cheers,
Adam

—
PGP Fingerprint: 00EF 547B 63CC 8FB0 02F4 C654 6843 7E0C F3E7 FCC1

On Oct 26, 2013, at 10:57 AM, Dave Koelmeyer 
dave.koelme...@davekoelmeyer.co.nz wrote:

 On 26/10/13 09:16 PM, Bryan N Iotti wrote:
 Hi all,
 
 There's a comment that can't be deleted from the wiki (at least, I can't do 
 it).
 
 It's the one from Anonymous here:
 http://wiki.openindiana.org/display/~trisk/Home?focusedCommentId=26543498#comment-26543498
 
 Hi Bryan,
 
 I encountered that too - I'm guessing it's a combination of whatever 
 permission we have and that it's been posted under a personal space.
 
 Cheers,
 
 -- 
 Dave Koelmeyer
 http://blog.davekoelmeyer.co.nz
 
 
 ___
 oi-dev mailing list
 oi-dev@openindiana.org
 http://openindiana.org/mailman/listinfo/oi-dev



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] PostgreSQL question

[Adam Števko]

Hi Alexander,

LGTM and nice job.

Cheers,
Adam

On Oct 22, 2013, at 4:44 PM, Alexander Pyhalov a...@rsu.ru wrote:

 On 10/21/2013 18:42, Alexander Pyhalov wrote:
 Hello.
 I have a question on PostgreSQL 8.4 packaging.
 Currently we have disabled runpath for PG and ship postgres-common
 package which contains libpq. But what if we ship several PG versions?
 Are we sure in binary compatibility of, let's say, 9.2 libpq  and  8.4
 clients?
 
 I just would like to estimate pros and cons of removing
 --disable-rpath switch.
 
 I'd like to remove it (so that each PostgreSQL binary has correct
 embedded rpath) , ship almost empty postgres-common package (containing
 only user and group definitions) and make /usr/postgres/{bin,lib},
 /usr/bin/psql, /usr/lib/libpq.so mediated links (or perhaps even avoid
 shipping /usr/lib/libpq.so by default). For example, currently mysql
 doesn't ship libraries in /usr/lib.
 
 What do you think?
 
 So, the first package version is available here:
 https://github.com/pyhalov/oi-userland/compare/postgresql84
 
 Please, review.
 
 Packages (besides postgresql itself) that can be affected (currently not in 
 oi-userland):
 pkg:/database/postgres/library/c++/libpqxx
 pkg:/database/postgres/pgtcl
 pkg:/library/perl-5/dbd-pgsql
 
 Packages that can be affected but are easy to rebuild:
 pkg:/library/apr-util/dbd-pgsql
 pkg:/web/php-54/extension/php-pgsql
 
 Distinctions from original package:
 1) RPATH is embedded in utilities and libraries
 2) /usr/lib/libpq* and /usr/lib/amd64/libpq* are links to 
 /usr/postgres/8.4/lib/ versions of libraries. Facet facet.compat.dev is set 
 on these links
 3) uids and gids definition are moved to postgres-common. It contains only 
 them and /usr/lib/*/libpq* links.
 4) sysconfdir changed from /etc/postgres/ to /etc/postgres/8.4. (I think, 
 there are not many people who use configs in /etc/postgres for PostgreSQL)
 5) pg_config adds rpath by default (pg_config --ldflags)
 
 Testing done:
 1) created db, played with it a bit
 2) checked php pgsql extension - seems to work
 3) checked libpqxx with Sun Studio CC - seems to work
 4) gmake check - timestamptz test fails (I've seen this before, it seems to 
 be expected on OI)
 
 As for earlier postgres versions, I think they be easily marked obsolete 
 after postgres 8.4 integration, however it's not a high priority task. I'd 
 better look at PG 9.3 / 9.2.
 -- 
 Best regards,
 Alexander Pyhalov,
 system administrator of Computer Center of Southern Federal University
 
 ___
 oi-dev mailing list
 oi-dev@openindiana.org
 http://openindiana.org/mailman/listinfo/oi-dev



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] pkcs library fix

[Adam Števko]

IPS update is being worked on. However, I found out that my build environment 
is messed in a mysterious way. I am sick, so everything I am working on has 
stalled (sorry, health first). IPS will be definitely updated as I want python 
2.7 in the tree and make it default at some point.

Speaking of creating ISO image, it's up to you then. However, I think that we 
should choose a deadline for changes to be integrated into oi-userland. If that 
deadline passes, we simply create ISO images. If we know that some integrated 
changes might break something seriously, we simply skip that until it's get 
fixed (this might satisfy people, who want stable hipster, which I consider 
nonsense at this stage).

What do you think?

Cheers,
Adam

On Oct 17, 2013, at 7:49 AM, Alexander Pyhalov a...@rsu.ru wrote:

 Good morning, Adam.
 
 Adam Števko писал 17.10.2013 08:58:
 Hi,
 let's push the fix and also recreate iso, something like Q3 ISO
 release of hipster.
 Anything against this idea?
 Adam
 
 I've thought about creating ISO a bit later - when PHP work and Net-SNMP 
 update is finished.
 To finish it I need 64bit libwrap (I sent a RTI yesterday) for php-tcpwrap 
 extension (currently missed in PHP 5.4)
 and real fix for this bug (I think the fix is coming soon).
 However, I would also like to have gcc-compiled PostgreSQL (8.4 and 9.3) and 
 so on and so on.
 I think I'll never stop to wish more (for example, I'm craving for IPS update 
 and python 2.7 :)).
 So, let's push the fix and recreate ISO.
 At least the latest ISO was released two months ago.
 Since then we have a rather good portion of new software and some critical 
 fixes in GCC toolchain.
 
 ---
 System Administrator of Southern Federal University Computer Center
 
 
 
 
 



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Update pinentry in hipster to 0.8.3

[Adam Števko]

Hi, 

please create a pull request for all components you are going to update.

Basic workflow:
- update all components and check if they work
- remove components from components.ignore file 
- commit to you forked repo
- create pull request

Adam

On Sep 11, 2013, at 2:28 AM, Colin Ellis panamaya...@gmail.com wrote:

 Updates are at https://github.com/cr-ellis/oi-userland/tree/pinentry
 
 Has been checked with the new gnupg in gnome and works for me.
 ___
 oi-dev mailing list
 oi-dev@openindiana.org
 http://openindiana.org/mailman/listinfo/oi-dev



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Numpy and Scipy

[Adam Števko]

Hi

On 8 Sep 2013, at 18:36, Aurélien Larcher aurelien.larc...@gmail.com wrote:

 Hi everyone,
 since the numpy python package available in hipster seems broken (segfaults), 
 I installed the latest stable 1.7.0 compiled with gcc, without a linear 
 algebra backend.
 So I intend to add latest numpy, scipy (and atlas for the backend) in 
 oi-userland if it is ok.

Just fork the repository, commit things and create a pull request. I will pick 
it up and merge.

 How does it fit in the way python modules are packaged ? Should they be added 
 to the python folder ?
 Should 32 bit and 64 bits be both provided or only one of them ?

At the moment, OI has only python 2.6, which sucks. Therefore, I am working on 
bringing new pkg, which is needed for publishing python 2.7. Once that gets 
published, plan is to make it the default version.

Speaking of packaging look at any python component. It should reside under 
python directory, There should be 2 p5m files (e.g numpy.p5m and numpy-26.p5m, 
numpy.p5m creating conditional dependency on a numpy-26. Just ignore -PYVER.p5m 
for now).

Bitness is something packager has to consider. If there is a point in 
delivering a 64 bit package, then do so. 

 
 What about gdb, is it possible to upgrade to 7.x to get python extensions or 
 are there any known showstoppers ? (I installed the latest gdb with the 
 'historical' patches).
I have looked at gdb yesterday and the component needs removing studio specific 
compile flags and make it builadble by gcc. Also test suite should pass all 
tests if possible to test package functionality.

 I have also a few numerical libraries pending that I converted from my SFE 
 specs. 

Great, if you mind sharing just create a pull request.

 Best regards,
 
 Aurelien

Cheers,
Adam
 
 -- 
 ---
 LARCHER Aurélien| KTH, School of Computer Science and 
 Communication
 Work: +46 (0) 8 790 71 42   | Lindstedtsvägen 5, Plan 4
 Mob.: +46 (0) 7 09 46 40 17 | 100 44 Stockholm, SWEDEN
 ---
 Praise the Caffeine embeddings ...
 ___
 oi-dev mailing list
 oi-dev@openindiana.org
 http://openindiana.org/mailman/listinfo/oi-dev


smime.p7s
Description: S/MIME cryptographic signature
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Planned e-hackathon this saturday

[Adam Števko]

Hi,

I guess for a few hour hacking outcome is great:

- vim/gvim updated to 7.4
- puppet updated to 3.2.2 (the massive puppet oracle did in userland is not 
included, alp has the details)
- stunnel enabled to 4.6.5
- libtecla is updated to latest 1.6.2, but disabled for now
- lua got updated to 5.2.2

I hope that more people get involved in these types of action in the future.

Cheers,
Adam

On Aug 22, 2013, at 9:54 PM, Adam Števko adam.ste...@gmail.com wrote:

 Hi folks,
 
 first of all, I am sorry that I am announcing this quite late. alp and I 
 decided to allocate some time and work on enabling all components in 
 oi-userland this saturday. We plan to meet in #oi-dev around 14:00 CEST 
 (16:00 for alp).
 If anyone has some nothing to do, feel free to join!
 
 Cheers,
 Adam



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] Planned e-hackathon this saturday

[Adam Števko]

Hi folks,

first of all, I am sorry that I am announcing this quite late. alp and I 
decided to allocate some time and work on enabling all components in 
oi-userland this saturday. We plan to meet in #oi-dev around 14:00 CEST (16:00 
for alp).
If anyone has some nothing to do, feel free to join!

Cheers,
Adam


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] build environment modifications

[Adam Števko]

Hi guys,

I would like to merge some changes to transforms and build environments, but I 
would like a review before I do:

https://github.com/xen0l/oi-userland/commit/b29ae5f07288eee6a5cc59cd7751770c7fb17cc9
https://github.com/xen0l/oi-userland/commit/cd9a16b7259c9dbca4d3ea45cc3c3d36d5d8f2f8
- removal of Oracle CDDL templates, import of illumos ones. This will change 
sample-manifest license header.

https://github.com/xen0l/oi-userland/commit/ef4e018188cf13e1535ee00109d03046705595ce
- some minor contact modifications in the README file

https://github.com/xen0l/oi-userland/commit/6842d7ffb4ed409a276f9e06a8e5310ad7d5764f
- Alasdair's issue (https://www.illumos.org/issues/2682), which brings in sane 
default for configuration environment. Many components already sets these in 
their Makefile and I don't see reasons, why we shouldn't make them default.
I commented out CONFIGURE_OPTIONS as I found them redundant. From my 
understanding, configure will set these to environment variables, so 
CONFIGURE_ENV should be sufficient. If there are any objections I will restore 
CONFIGURE_OPTIONS. I also ask for an opinion if there is a point in setting 
these value for other _ENV variables (COMPONENT_BUILD_ENV, 
COMPONENT_INSTALL_ENV, COMPONENT_TEST_ENV, COMMON_PERL_ENV, PYTHON_ENV).

https://github.com/xen0l/oi-userland/commit/db2ec7b9210fb8e1bc134830e22c1f0935121594
https://github.com/xen0l/oi-userland/commit/05394c0cd3765edc077327b28bc0116ec5537be5
- Alasdair's issue (https://www.illumos.org/issues/2683), which fixes setting 
correct LDFLAGS for components. There were problems mostly with 64-bit software 
and the build would fail because linker picked up wrong LDFLAGS. LINKER 
variable is taken from ec-userland and is used to set the correct LDFLAGS. In 
the second commit, the linker is switched to ccs instead of gcc.

My other change I wanted to integrate was adding -i to env, which will 
ignore user environment variables and use only the ones found in _ENV. However, 
when I tested this several components failed their build, so this needs more 
work/research. Any comments on this?

Cheers,
Adam

smime.p7s
Description: S/MIME cryptographic signature
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] default mysql version and provider

[Adam Števko]

Hi,

first of all, good job!

How many open source software are switching from mysql to mariadb? I am aware 
of some Linux distributions replacing mysql with mariadb and that is something, 
which will eventually happen over time. I would vote for moving to mariadb, 
however this WILL break compatibility. Are there any good reasons, why should 
we stick to mysql instead of mariadb/percona?

Cheers,
Adam

On Aug 5, 2013, at 4:07 PM, Alexander Pyhalov a...@rsu.ru wrote:

 Hello.
 I committed mariadb to /hipster repository. On Friday I added percona-server. 
 The question is - do we want to change default mysql dependencies for 
 packages and what should it be?
 
 The options are
 1) Preserve mysql 5.1 dependencies (like upstream).
 2) Create mysql 5.6 package and switch dependencies to it.
 3) Switch default dependencies to percona or mariadb (like Fedora or 
 OpenSUSE).
 
 The considerations are possible compatibility issues. We preserve mysql 5.1 
 libraries. But what will happen if independent software A depends on mysql 
 and library B which was switched to MariaDB dependency? It's just a 
 hypothetical example...
 
 Waiting for your opinions.
 -- 
 Best regards,
 Alexander Pyhalov,
 system administrator of Computer Center of Southern Federal University
 
 ___
 oi-dev mailing list
 oi-dev@openindiana.org
 http://openindiana.org/mailman/listinfo/oi-dev



smime.p7s
Description: S/MIME cryptographic signature
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] build environment modifications

[Adam Števko]

http://docs.oracle.com/cd/E26502_01/html/E21383/gentextid-3283.html#scrolltoc

It should also be somewhere in /usr.

On Aug 5, 2013, at 8:16 PM, Alexander Pyhalov a...@rsu.ru wrote:

 One more thought on the related topic.
 Is there some link with all available info.classifications ?
 If it exists, perhaps it should be inserted in manifest as a comment?
 If it doesn't, perhaps, it worths to do such a page on OI wiki?
 
 Adam Števko писал 05.08.2013 19:50:
 Hi guys,
 I would like to merge some changes to transforms and build
 environments, but I would like a review before I do:
 https://github.com/xen0l/oi-userland/commit/b29ae5f07288eee6a5cc59cd7751770c7fb17cc9
 https://github.com/xen0l/oi-userland/commit/cd9a16b7259c9dbca4d3ea45cc3c3d36d5d8f2f8
 - removal of Oracle CDDL templates, import of illumos ones. This will
 change sample-manifest license header.
 https://github.com/xen0l/oi-userland/commit/ef4e018188cf13e1535ee00109d03046705595ce
 - some minor contact modifications in the README file
 https://github.com/xen0l/oi-userland/commit/6842d7ffb4ed409a276f9e06a8e5310ad7d5764f
 - Alasdair's issue (https://www.illumos.org/issues/2682), which brings
 in sane default for configuration environment. Many components already
 sets these in their Makefile and I don't see reasons, why we shouldn't
 make them default.
 I commented out CONFIGURE_OPTIONS as I found them redundant. From my
 understanding, configure will set these to environment variables, so
 CONFIGURE_ENV should be sufficient. If there are any objections I will
 restore CONFIGURE_OPTIONS. I also ask for an opinion if there is a
 point in setting these value for other _ENV variables
 (COMPONENT_BUILD_ENV, COMPONENT_INSTALL_ENV, COMPONENT_TEST_ENV,
 COMMON_PERL_ENV, PYTHON_ENV).
 https://github.com/xen0l/oi-userland/commit/db2ec7b9210fb8e1bc134830e22c1f0935121594
 https://github.com/xen0l/oi-userland/commit/05394c0cd3765edc077327b28bc0116ec5537be5
 - Alasdair's issue (https://www.illumos.org/issues/2683), which fixes
 setting correct LDFLAGS for components. There were problems mostly
 with 64-bit software and the build would fail because linker picked up
 wrong LDFLAGS. LINKER variable is taken from ec-userland and is used
 to set the correct LDFLAGS. In the second commit, the linker is
 switched to ccs instead of gcc.
 My other change I wanted to integrate was adding -i to env, which
 will ignore user environment variables and use only the ones found in
 _ENV. However, when I tested this several components failed their
 build, so this needs more work/research. Any comments on this?
 ---
 System Administrator of Southern Federal University Computer Center
 
 
 ___
 oi-dev mailing list
 oi-dev@openindiana.org
 http://openindiana.org/mailman/listinfo/oi-dev



smime.p7s
Description: S/MIME cryptographic signature
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev