[oi-dev] Update pinentry in hipster to 0.8.3

[Colin Ellis]

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

Re: [oi-dev] Update gnupg and related libs in hipster

[Colin Ellis]

Here's the components.ignore change as requested:

https://github.com/cr-ellis/oi-userland/commit/4f6a4d3c7d404699d9edb6298887a643fb3fa1ca

I have installed gnupg and tested with graphical pinentry.  All works as
expected.


On Tue, Sep 3, 2013 at 12:41 AM, Alexander Pyhalov  wrote:

> Hello.
> Could you also remove gnupg from components.ignore for userland build to
> notice this component?
>
> I assume, you've checked that gnome likes this new gnupg...
>
>
> On 09/03/2013 06:56, Colin Ellis wrote:
>
>> Hi guys,
>>
>> I've updated gnupg and the related libs to their latest versions.  It
>> works
>> for me but would like to have it reviewed.
>>
>> Git commit is at:
>>
>> https://github.com/cr-ellis/**oi-userland/commit/**
>> 729d5962f744bc79e5d4053daf2b38**bfdad3f2c6<https://github.com/cr-ellis/oi-userland/commit/729d5962f744bc79e5d4053daf2b38bfdad3f2c6>
>>
>> Thanks,
>>
>> Colin
>>
>>
>>
>> __**_
>> oi-dev mailing list
>> oi-dev@openindiana.org
>> http://openindiana.org/**mailman/listinfo/oi-dev<http://openindiana.org/mailman/listinfo/oi-dev>
>>
>>
>
> --
> 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] Update gnupg and related libs in hipster

[Colin Ellis]

Hi guys,

I've updated gnupg and the related libs to their latest versions.  It works
for me but would like to have it reviewed.

Git commit is at:

https://github.com/cr-ellis/oi-userland/commit/729d5962f744bc79e5d4053daf2b38bfdad3f2c6

Thanks,

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

Re: [oi-dev] OI 'hipster' reboot effort

[Colin Ellis]

Hi Andrej,

is there a bug tracker for this branch and a list of required package
updates somewhere?  I'd like to prioritize my efforts in line with what
others need.

Also what compilers are used on this new hipster release?


On Fri, May 17, 2013 at 7:14 PM, Andrzej Szeszo  wrote:

> Hi All
>
> Seeing that the project is slowing down a bit, I have decided that I
> will try to help it get some momentum back.
>
> Firstly, if you rely on stable OI releases, Jon Tibble will carry on
> producing traditional releases and they will be made available in the
> /dev repo and as installable ISO/USB images. OI 151a8 should be out
> real soon now.
>
> /dev releases follow traditional Sun/Oracle releng process, which is
> very time consuming. Mainly for that reason it may take a very long
> time before any build system update will be reflected in the package
> repository.
>
> OI 'hipster' is trying to change the process by switching to a rolling
> release model.
>
> There is single top-level build repo on Github:
> https://github.com/OpenIndiana/oi-userland. If you want to change
> something or add new packages - simply send a pull request.
>
> Changes to the build repo are automatically picked up by Jenkins
> instance, packages are built and then published to the
> http://pkg.openindiana.org/hipster repo. It is all set up and working
> now.
>
> http://pkg.openindiana.org/hipster repo currently consists of /dev
> contents + JT's /dev-test OI 151a8 bits + Milan Jurik's JDS work +
> Jenkins built packages.
>
> The plan is to improve what's out there incrementally. Eventually it
> should be possible to build complete OS from the Github repo.
>
> To use /hipster repo, install OI 151a7 and run (as root):
>
> pkg set-publisher -O http://pkg.openindiana.org/hipster openindiana.org
> pkg update -v
>
> Few people started submitting changes already. Thanks for that! If you
> have something to be added or changed in the repo, simply send us pull
> request.
>
> Couple useful links:
> Jenkins dashboard: http://hipster.openindiana.org:8080/
> Component build logs: http://hipster.openindiana.org/i386/logs/
>
> Andrzej
>
> ___
> 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] [userland] illumos-userland hackathon May 22 in Amsterdam

[Colin Ellis]

Hi,

I really wanted to go to this but work commitments will need to take
priority on this occasion.  Hopefully I can be online and be cheerleading
or something...

Hope you all have fun.

On Thu, May 10, 2012 at 9:27 PM, Alasdair Lumsden wrote:

> On 10 May 2012, at 21:05, Damian Wojsław wrote:
> > http://www.meetup.com/illumos-User-Group/events/56953802/
> > http://www.openstoragesummit.org/
> >
> > THis is all I got. :)
>
> Ditto! So I have some info:
>
> 1. The hackathon is on the 23rd of May, all day
> 2. It will be in an apartment instead of the hotel
> 3. I'll be staying in the apartment, there may be room for others if you
> notify buffyg now now now
> 4. I'm arriving on 22nd May and leaving 25th May, so staying 3 nights.
>
> Hopefully see some of you there!
>
> Cheers,
>
> Alasdair
> ___
> 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] Feature #1738 add Asterisk package to oi-build

[Colin Ellis]

Cleanup is here.  Hopefully ready for triage now.

https://bitbucket.org/cellis_oidev/oi-build/changeset/35222c592a5f


On Sat, Nov 12, 2011 at 3:26 AM, Josef 'Jeff' Sipek
wrote:

> On Mon, Nov 07, 2011 at 04:50:32PM +, Colin Ellis wrote:
> > https://bitbucket.org/cellis_oidev/oi-build/changeset/755748bc74a3
>
> Did you get the Makefile from Oracle?  It has an oracle copyright.  If not,
> you should also use the Illumos version of the CDDL header.
>
> Speaking of which, is your name Random Developer? ;)  You might want to fix
> up the manifest.  Something tells me that all the files in /etc should get
> mangled to make sure pkg doesn't blow them away.  Perhaps something like
> what irssi has:
>
>  default preserve true>
>  default mode 0644>
>
> Jeff.
>
> --
> We have joy, we have fun, we have Linux on a Sun...
>
> ___
> 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] Feature #1744 add ruby 1.9.3 to oi-build

[Colin Ellis]

I'm tidying up the files as requested.  I've run a make test, which passes.
I haven't found any DTrace patches for the 1.9 series of ruby.  The SFE
build of 1.9.0 doesn't have any applied.
I'd suggest having two ruby packages in the repo: ruby19 with latest code
and ruby18 with dtrace.

Any thoughts?

On Sat, Nov 19, 2011 at 10:35 PM, Alasdair Lumsden wrote:

> Hi Colin,
>
> Great stuff! Only minor nitpicks:
>
> On the Makefile, you've got multiple configure options per
> CONFIGURE_OPTION, and the indentation of the macros is a bit iffy. But if
> you like I can tidy these up when we commit, saving you the bother.
>
> Did you have any luck finding out about the DTrace patches? Also did you
> give make test a go?
>
> Cheers,
>
> Alasdair
>
>
> On 11/19/11 09:54 PM, Colin Ellis wrote:
>
>> https://bitbucket.org/cellis_**oidev/oi-build/changeset/**4c13f4869651<https://bitbucket.org/cellis_oidev/oi-build/changeset/4c13f4869651>
>>
>> On Tue, Nov 15, 2011 at 9:32 AM, Guido Berhoerster > <mailto:g...@openindiana.org>> wrote:
>>
>>* Colin Ellis mailto:panamaya...@gmail.com>**>
>>
>>[2011-11-12 19:40]:
>> > Fixes are here:
>> >
>> > https://bitbucket.org/cellis_**oidev/oi-build/changeset/**
>> 5bb1edf68a1d<https://bitbucket.org/cellis_oidev/oi-build/changeset/5bb1edf68a1d>
>>
>>Have you looked through the ruby 1.8 patches and checked which
>>are still applicable? At least the DTrace changes should probably
>>be ported over.
>>Have you checked the built ruby interpeter? Running "make test"
>>on the source tree after building should be an easy way to catch
>>any issues.
>>--
>>Guido Berhoerster
>>
>>__**_
>>oi-dev mailing list
>>oi-dev@openindiana.org <mailto:oi-dev@openindiana.org**>
>>
>> http://openindiana.org/**mailman/listinfo/oi-dev<http://openindiana.org/mailman/listinfo/oi-dev>
>>
>>
>>
>>
>>
>> __**_
>> oi-dev mailing list
>> oi-dev@openindiana.org
>> http://openindiana.org/**mailman/listinfo/oi-dev<http://openindiana.org/mailman/listinfo/oi-dev>
>>
>
>
> __**_
> oi-dev mailing list
> oi-dev@openindiana.org
> http://openindiana.org/**mailman/listinfo/oi-dev<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] Feature 1768 - add dovecot to oi-build

[Colin Ellis]

hopefully this is everything
https://bitbucket.org/cellis_oidev/oi-build/changeset/856e6772091a


On Sat, Nov 19, 2011 at 10:36 PM, Alasdair Lumsden wrote:

> Forgot to mention, your .p5m files need the opensolaris package
> classifications being filled in. If you're not sure what to use, just shout
> and we can collectively think up an answer.
>
>
>
> On 11/19/11 10:00 PM, Colin Ellis wrote:
>
>> https://bitbucket.org/cellis_**oidev/oi-build/changeset/**d7b944645d37<https://bitbucket.org/cellis_oidev/oi-build/changeset/d7b944645d37>
>>
>> On Tue, Nov 15, 2011 at 12:43 AM, Josef 'Jeff' Sipek
>> mailto:jef...@josefsipek.net>**> wrote:
>>
>>On Sat, Nov 12, 2011 at 11:17:10PM +, Colin Ellis wrote:
>> > bitbucket here:
>> > https://bitbucket.org/cellis_**oidev/oi-build/changeset/**
>> d7c2addf18b7<https://bitbucket.org/cellis_oidev/oi-build/changeset/d7c2addf18b7>
>>
>>Awesome, this one was on my todo list.  Less work for me :)
>>
>>1) no need to set --prefix & --sbindir yourself
>>
>>2) $(ETCDIR) instead of /etc
>>
>>3) did the `gmake publish` not complain about the missing
>>   info.classification?
>>
>>4) Do we really need to ship all those .a and .la files?  Solaris likes
>>   shared libs a lot - and handles them pretty well too.
>>
>>5) Do the files in usr/share/doc have the doc facet?  (They should;
>>you can
>>   check the published manifest.)
>>
>>6) Is there an SMF manifest?
>>
>>Thanks!
>>
>>Jeff.
>>
>>--
>>All parts should go together without forcing.  You must remember
>>that the
>>parts you are reassembling were disassembled by you.  Therefore, if you
>>can’t get them together again, there must be a reason.  By all
>>means, do not
>>use a hammer.
>>— IBM Manual, 1925
>>
>>__**_
>>oi-dev mailing list
>>oi-dev@openindiana.org <mailto:oi-dev@openindiana.org**>
>>
>> http://openindiana.org/**mailman/listinfo/oi-dev<http://openindiana.org/mailman/listinfo/oi-dev>
>>
>>
>>
>>
>>
>> __**_
>> oi-dev mailing list
>> oi-dev@openindiana.org
>> http://openindiana.org/**mailman/listinfo/oi-dev<http://openindiana.org/mailman/listinfo/oi-dev>
>>
>
>
> __**_
> oi-dev mailing list
> oi-dev@openindiana.org
> http://openindiana.org/**mailman/listinfo/oi-dev<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] Feature 1768 - add dovecot to oi-build

[Colin Ellis]

https://bitbucket.org/cellis_oidev/oi-build/changeset/d7b944645d37

On Tue, Nov 15, 2011 at 12:43 AM, Josef 'Jeff' Sipek
wrote:

> On Sat, Nov 12, 2011 at 11:17:10PM +, Colin Ellis wrote:
> > bitbucket here:
> > https://bitbucket.org/cellis_oidev/oi-build/changeset/d7c2addf18b7
>
> Awesome, this one was on my todo list.  Less work for me :)
>
> 1) no need to set --prefix & --sbindir yourself
>
> 2) $(ETCDIR) instead of /etc
>
> 3) did the `gmake publish` not complain about the missing
>   info.classification?
>
> 4) Do we really need to ship all those .a and .la files?  Solaris likes
>   shared libs a lot - and handles them pretty well too.
>
> 5) Do the files in usr/share/doc have the doc facet?  (They should; you can
>   check the published manifest.)
>
> 6) Is there an SMF manifest?
>
> Thanks!
>
> Jeff.
>
> --
> All parts should go together without forcing.  You must remember that the
> parts you are reassembling were disassembled by you.  Therefore, if you
> can’t get them together again, there must be a reason.  By all means, do
> not
> use a hammer.
>— IBM Manual, 1925
>
> ___
> 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] Feature #1744 add ruby 1.9.3 to oi-build

[Colin Ellis]

https://bitbucket.org/cellis_oidev/oi-build/changeset/4c13f4869651

On Tue, Nov 15, 2011 at 9:32 AM, Guido Berhoerster wrote:

> * Colin Ellis  [2011-11-12 19:40]:
> > Fixes are here:
> >
> > https://bitbucket.org/cellis_oidev/oi-build/changeset/5bb1edf68a1d
>
> Have you looked through the ruby 1.8 patches and checked which
> are still applicable? At least the DTrace changes should probably
> be ported over.
> Have you checked the built ruby interpeter? Running "make test"
> on the source tree after building should be an easy way to catch
> any issues.
> --
> Guido Berhoerster
>
> ___
> 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

[oi-dev] Feature 1768 - add dovecot to oi-build

[Colin Ellis]

bitbucket here:
https://bitbucket.org/cellis_oidev/oi-build/changeset/d7c2addf18b7
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Feature #1744 add ruby 1.9.3 to oi-build

[Colin Ellis]

Fixes are here:

https://bitbucket.org/cellis_oidev/oi-build/changeset/5bb1edf68a1d

Not sure about hardcoded bit in the p5m file.  It got generated like that.

I believe this should be a single package but others might disagree.  I
wouldn't know where to start to split it apart though!



On Sat, Nov 12, 2011 at 3:42 AM, Josef 'Jeff' Sipek
wrote:

> On Mon, Nov 07, 2011 at 04:52:51PM +, Colin Ellis wrote:
> > bitbucket
> https://bitbucket.org/cellis_oidev/oi-build/changeset/3c3b8bb07540
>
> I know nothing about ruby, but here are a few things I noticed...
>
> - Oracle copyright/OSOL CDDL header.
> - hardcoded "GMAKE=gmake -j16"
> - GCC_ROOT hardcoded, is there an issue with gcc46?
> - again, you are not Random Developer - check you p5m
> - the .so have 'i386' hardcoded in the path (e.g.,
>  path=usr/lib/$(MACH64)/ruby/1.9.1/i386-solaris2.11/enc/iso_8859_14.so)
> - this is a lot of files; is this really one package? or should it be
>  several?
>
> Jeff.
>
>
> > ___
> > oi-dev mailing list
> > oi-dev@openindiana.org
> > http://openindiana.org/mailman/listinfo/oi-dev
>
>
> --
> What is the difference between Mechanical Engineers and Civil Engineers?
> Mechanical Engineers build weapons, Civil Engineers build targets.
>
> ___
> 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] Feature #1738 add Asterisk package to oi-build

[Colin Ellis]

Hopefully this fixes the install paths.

https://bitbucket.org/cellis_oidev/oi-build/changeset/b29e7dafbc76

Not sure about the file transform stuff.  Is there a good explanation of
that somewere?

On Sat, Nov 12, 2011 at 3:28 AM, Josef 'Jeff' Sipek
wrote:

> On Fri, Nov 11, 2011 at 10:26:56PM -0500, Josef 'Jeff' Sipek wrote:
> > On Mon, Nov 07, 2011 at 04:50:32PM +, Colin Ellis wrote:
> > > https://bitbucket.org/cellis_oidev/oi-build/changeset/755748bc74a3
> >
> > Did you get the Makefile from Oracle?  It has an oracle copyright.  If
> not,
> > you should also use the Illumos version of the CDDL header.
> >
> > Speaking of which, is your name Random Developer? ;)  You might want to
> fix
> > up the manifest.  Something tells me that all the files in /etc should
> get
> > mangled to make sure pkg doesn't blow them away.  Perhaps something like
> > what irssi has:
> >
> >  default preserve true>
> >  default mode 0644>
>
> Also, /include should be /usr/include at the very least.
>
> > Jeff.
> >
> > --
> > We have joy, we have fun, we have Linux on a Sun...
> >
> > ___
> > oi-dev mailing list
> > oi-dev@openindiana.org
> > http://openindiana.org/mailman/listinfo/oi-dev
>
> --
> Si hoc legere scis nimium eruditionis habes.
>
> ___
> 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] oi-build feature #1252 - GCC 4.6.2

[Colin Ellis]

Additional changeset to fix up copyright headers

https://bitbucket.org/cellis_oidev/oi-build/changeset/29819e8e803f

On Sat, Nov 12, 2011 at 3:23 AM, Josef 'Jeff' Sipek
wrote:

> On Mon, Nov 07, 2011 at 04:48:05PM +, Colin Ellis wrote:
> > https://bitbucket.org/cellis_oidev/oi-build/changeset/170076b03654
> >
> > use Makefile.bootstrap files for gcc3 :)
>
> Ooooh!  So, to build it the first time, I need to 'gmake -f
> Makefile.bootstrap' for the libs, then gcc.  Once I have them installed, I
> can ignore the bootstrap files?
>
> Why are there two packages - one for gcc and one for the runtime?  It seems
> to me that using facets would be the better way.
>
> Since we have a new enough pkg in /experimental, we can use mediated links
> to manage /usr/bin/gcc (as well as g++, etc.).  I think it'd be worth
> having
> them.
>
> Jeff.
>
> --
> Failure is not an option,
> It comes bundled with your Microsoft product.
>
> ___
> 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] build perl-512 failed on oi-build

[Colin Ellis]

This is a bug with sun studio...

export LANG=C;export LC_ALL=C will fix it.


On Tue, Nov 8, 2011 at 9:35 AM, Igor Kozhukhov  wrote:

> Hello,
>
> I have configured environment for oi-build from site:
> http://wiki.openindiana.org/oi/Building+with+oi-build
>
> I have problems with build perl512:
> $ cd oi-build/components/perl512
> $ gmake install
> .
> Extracting config.h (with variable substitutions)
> /usr/sbin/dtrace -h -s perldtrace.d -o perldtrace.h
> /bin/sh cflags.SH
> Extracting cflags (with variable substitutions)
> `sh  cflags "optimize='-xO4 '" miniperlmain.o` -KPIC miniperlmain.c
>   CCCMD =  cc -DPERL_CORE -c -DPTR_IS_LONG -D_LARGEFILE_SOURCE
> -D_FILE_OFFSET_BITS=64 -DPERL_USE_SAFE_PUTENV  -xO4
> `sh  cflags "optimize='-xO4 '" gv.o` -KPIC gv.c
>   CCCMD =  cc -DPERL_CORE -c -DPTR_IS_LONG -D_LARGEFILE_SOURCE
> -D_FILE_OFFSET_BITS=64 -DPERL_USE_SAFE_PUTENV  -xO4
> Assembler: gv.c
> "/tmp/ube.1320745603.21116.05.s", line 500 : Illegal character:
> <2f>
> "/tmp/ube.1320745603.21116.05.s", line 501 : Illegal character:
> <2f>
> "/tmp/ube.1320745603.21116.05.s", line 502 : Illegal character:
> <2f>
> "/tmp/ube.1320745603.21116.05.s", line 503 : Illegal character:
> <2f>
> "/tmp/ube.1320745603.21116.05.s", line 504 : Illegal character:
> <2f>
> "/tmp/ube.1320745603.21116.05.s", line 505 : Illegal character:
> <2f>
> "/tmp/ube.1320745603.21116.05.s", line 506 : Illegal character:
> <2f>
> "/tmp/ube.1320745603.21116.05.s", line 507 : Illegal character:
> <2f>
> "/tmp/ube.1320745603.21116.05.s", line 508 : Illegal character:
> <2f>
> "/tmp/ube.1320745603.21116.05.s", line 509 : Illegal character:
> <2f>
> "/tmp/ube.1320745603.21116.05.s", line 510 : Illegal character:
> <7b>
> "/tmp/ube.1320745603.21116.05.s", line 510 : Illegal character:
> <20>
> "/tmp/ube.1320745603.21116.05.s", line 510 : Illegal character:
> <7d>
> "/tmp/ube.1320745603.21116.05.s", line 510 : Illegal usage of '}'
> "/tmp/ube.1320745603.21116.05.s", line 510 : Syntax error
> Near line: "{ int[ 1]  45  }movl   %esp,%ebp
>  "
> "/tmp/ube.1320745603.21116.05.s", line 510 : Illegal character:
> <20>
> "/tmp/ube.1320745603.21116.05.s", line 510 : Illegal character:
> <20>
> "/tmp/ube.1320745603.21116.05.s", line 510 : Illegal character:
> <35>
> "/tmp/ube.1320745603.21116.05.s", line 510 : Illegal character:
> <34>
> "/tmp/ube.1320745603.21116.05.s", line 510 : Illegal character:
> <20>
> "/tmp/ube.1320745603.21116.05.s", line 510 : Illegal character:
> <20>
> "/tmp/ube.1320745603.21116.05.s", line 510 : Illegal character:
> <20>
> "/tmp/ube.1320745603.21116.05.s", line 510 : Illegal character:
> <20>
> "/tmp/ube.1320745603.21116.05.s", line 510 : Illegal character:
> <20>
> "/tmp/ube.1320745603.21116.05.s", line 510 : Illegal character:
> <20>
> "/tmp/ube.1320745603.21116.05.s", line 510 : Illegal character:
> <20>
> "/tmp/ube.1320745603.21116.05.s", line 510 : Illegal character:
> <20>
> "/tmp/ube.1320745603.21116.05.s", line 510 : Illegal character:
> <20>
> "/tmp/ube.1320745603.21116.05.s", line 510 : Illegal character:
> <20>
> "/tmp/ube.1320745603.21116.05.s", line 510 : Illegal character:
> <5d>
> "/tmp/ube.1320745603.21116.05.s", line 510 : Illegal character:
> <31>
> Too many errors - Goodbye
> cc: fbe failed for gv.c
> make[1]: *** [gv.o] Error 1
> .
>
> What the problem and how to fix it ?
>
> Could you please update instruction on WiKi if needed ?
>
> Best regards,
> Igor
>
>
> ___
> 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

[oi-dev] Feature #1744 add ruby 1.9.3 to oi-build

[Colin Ellis]

bitbucket https://bitbucket.org/cellis_oidev/oi-build/changeset/3c3b8bb07540
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] Feature #1738 add Asterisk package to oi-build

[Colin Ellis]

https://bitbucket.org/cellis_oidev/oi-build/changeset/755748bc74a3
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] oi-build feature #1252 - GCC 4.6.2

[Colin Ellis]

https://bitbucket.org/cellis_oidev/oi-build/changeset/170076b03654

use Makefile.bootstrap files for gcc3 :)
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] 1686 Bring Xmedcon to oi build, Ask for review

[Colin Ellis]

Cool,  well done!

Where can I get one?  I'm sure something is wrong...



On Tue, Oct 25, 2011 at 5:41 PM, Paolo Marcheschi
wrote:

> Hi
>
> This is my first contribution I'm asking for a review,
>
> Xmedcon  is a medical imaging software that helps for conversion of medical
> images expecially Brain MRI images.
> I pushed to :
>
> https://bitbucket.org/paolo_**marcheschi/oi-build
>
>
>
> changeset:   446:face9c7090fc
> tag: tip
> user:paolo_marcheschi
> date:Tue Oct 25 16:12:41 2011 +
> summary: First release on Openindiana of Xmedcon
>
>
>
> Thank you
>
> Paolo Marcheschi
>
>
> __**_
> 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] Git as a version control system for new OI projects

[Colin Ellis]

Damn.  I still think in 'cvs' commands

On Thu, Jun 23, 2011 at 11:14 AM, Guido Berhoerster wrote:

> Hello,
>
> * Andrzej Szeszo  [2011-06-23 02:06]:
> > Latest upstream ips/pkg5 tools need more and more changes to make
> > them work with OI and illumos. I have asked the version control
> > system question because I wanted to create a repository for pkg5
> > with the changes.
> >
> > I wanted to avoid mercurial + mq patch queue solution and started
> > experimenting with git as I've heard good things about its rebase
> > feature.
> >
> > With some help from hg-git I was able to prepare git repository with
> > untouched branch which is tracking upstream pkg-gate + branches with
> > local modifications. I was then able to pull in upstream changes and
> > rebase customized branches without too much effort.
> >
> > Nice rebase functionality, cheap non-permanent branches, ability to
> > use hg frontend with hg-git extension and also availability of very
> > good 'Successful Git branching model' document [1] makes Git worth
> > considering on the backend in my opinion.
> >
> > Also, I think model descibed at [1] is worth adopting in terms on
> > how to organize the repository/branches. It would save us time on
> > re-inveting repository layout and documenting it for starters. Also,
> > apparently it proved to be successful for many people. People at
> > Joyent use this model - they can't be wrong ;) [2]
> >
> > By the way - I quite like mercurial. If someone can demonstrate how
> > to do rebase but using mercurial I'd be willing to try it out.
> > Thanks in advance!
>
> if I understand it right you want
> a) lightweight feature branches which are easily removed after
>   merging them into the master branch
> b) maintain a permanent branch with OI-specific changes and
>   rebase it on top of Oracles upstream branch
>
> For a) mercurial offers completely anonymous branches, ie. when
> you just commit on top of any changeset (this is not really
> viable with git) or you use the bookmarks extension which allows
> you to actually label such a branch. Bookmarks can be completely
> removed after merging a such a branch and thus resemble the
> behavior of gits branches [1].
>
> For b) mercurial offers the rebase extension which provides
> equivalent functionality as gits rebase. The question is why we
> should actually do this for a long-lived named branch rather than
> explicit merges.
>
> Anyway, both workflows (whether they are adequate for our
> purposes or not) are easily possible with mercurial.
>
>
> [1] There are two caveats with bookmarks, first you always want
> to ser "track.current = True" so that only the currently active
> bookmark and not all bookmarks pointing to a changeset get moved
> forward when you commit on top of it (this brain-dmaged default
> is gone from mercurial 1.8) and you need mercurial 1.6 to
> push/pull bookmarks between repos.
> --
> Guido Berhoerster
>
> ___
> 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] Distribution build system

[Colin Ellis]

Great idea, worth the pain!

On Wed, Mar 16, 2011 at 11:35 AM, Andrzej Szeszo  wrote:

> Hi All
>
> The project is moving forward very slowly. I my opinion one of the main
> reasons behind it is lack of unified distribution build system.
>
> Previous releases were put together manually. Probably one or two core
> contributors would be be able to repeat the whole process at this point
> without investing significant amount of time into learning how things fit
> together. We need distribution release and publishing process to be
> automated and repeatable.
>
> There is a significant amount of bug reports in OpenIndiana bug tracker.
> Many of bugs require very simple changes to get fixed. URL updates or
> branding updates for example. Many contributors are more than capable of
> fixing such bugs. Because it is not clear what goes where, and also how to
> build and then test things many contributors simply don't bother looking at
> bugs at all.
>
> I am proposing creating a unified distribution build system. A system that
> would build the whole distribution after issuing a single "make publish" or
> similar command.
>
> Having such system will let us to release early, release often. It should
> improve the development progress in general. Bugfixes and security updates
> would get integrated in no time. New users would have an easy start. We
> could point new contributors at the build system and simply ask them to
> start hacking. Having all consolidations referenced from a single build
> system would make it clear to them where things go. Base system changes,
> etc. - core consolidations, new software - add-on consolidation directory,
> and so on.
>
> Continuous build system could be implemented using the same tools on the
> OpenIndiana build machines, including the SPARC ones.
>
> Many people will say that this is not possible and that even Oracle is not
> doing it. I say such system is possible but will require significant amount
> of work and significant amount of time to prepare. It will be worth the
> effort if done right. All major open source OS distributions have the
> release process automated in one way or another. I think this is the key to
> our success. Splitting the build and release engineering process between
> consolidation maintainers/owners based on Oracle model proved to not to work
> well for us.
>
> I would like to start a dialog between the core contributors about such
> build system. Discuss whether it is needed or not. And if the decision is
> made that it is needed - discuss requirements, technical details and then
> actually implement it!
>
> Andrzej
>
> ___
> 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] Security Work

[Colin Ellis]

Sure, I can help fill in the missing info if you want.

/Colin

On Mon, Jan 24, 2011 at 5:09 PM, Guido Berhoerster wrote:

> * Alasdair Lumsden  [2011-01-24 14:05]:
> > On the wiki page I still need to fill in their version and
> > consolidation, and update the security issues page for them - if
> > anyone else would like to help me do that, let me know (I'd
> > appreciate it).
>
> The list looks ok, please keep leaf packages and dependencies in
> separate tables, that'll make it easier to extend/reduce the list
> in the future.
>
> > At the moment our staffing numbers to maintain this are quite low
> > and as such it's a lot of work. But as the saying goes, "many hands
> > make light work".
> >
> > So I'd like to ask if anyone would object to me posting to
> > OpenIndiana-Discuss asking for security volunteers? We'll need to
> > ensure we get trustworthy people capable of helping rather than
> > hindering.
> >
> > I'm thinking volunteers would be best served by having a mentor, and
> > that we should group the software together by consolidation.
> >
> > We may want to write a job spec and split it into two parts - one
> > "Monitoring and Alerting", for less technical people, and the other
> > "Patching and building" for those who can learn to build
> > consolidations.
> >
> > I'd appreciate feedback.
>
> I would agree that we take contributions but have them reviewed
> by one or two "core developers", after a certain amount of time
> and good quality contributions people can become themselves
> reviewers.
>
> --
> Guido Berhoerster
>
> ___
> 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

[oi-dev] Proposal: OpenIndiana Stable Branch - A package list

[Colin Ellis]

Hi all,

I've compiled a package list incorporating the ones from Alasdairrr's email
with some of the ones I feel are must-haves in order to serve anything
internet-related.  I've taken the time to list the latest stable source code
release version along with latest package versions for Fedora 14, debian
Lenny, OI 148, and where possible the latest in SFW upstream from Oracle.

My feeling is that we can do better than oracle in some of these packages
without too much work.  It will make us more marketable if we were up to
date at least with apache, mysql, php, bind9 and sendmail.  If we don't want
to release them as stable then i'd be happy to look after another
consolidation of these updated packages.

Ubuntu created a great following very quickly by being more up to date than
debian (not difficult!).  I believe that we can do the same and be better
for some applications than solaris 11.

Please comment and add your own must-have packages.

/Colin


package_monitor_list.ods
Description: application/vnd.oasis.opendocument.spreadsheet
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev