From grzemba at contac-dt.de  Wed Dec  2 14:00:55 2015
From: grzemba at contac-dt.de (Carsten Grzemba)
Date: Wed, 02 Dec 2015 14:00:55 +0100
Subject: IPS package versioning
Message-ID: <bef0aa291a9f.565ef997@contac-dt.de>

Solaris IPS expect \d[.\d]* as version before the dash, so that package FMRI like this:

pkg:/opencsw/libwrap1 at 7.6_ipv6.4

not work. Want we simply strip other chars?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151202/26a57b0c/attachment.html>

From dam at opencsw.org  Wed Dec  2 14:06:51 2015
From: dam at opencsw.org (Dagobert Michelsen)
Date: Wed, 2 Dec 2015 14:06:51 +0100
Subject: IPS package versioning
In-Reply-To: <bef0aa291a9f.565ef997@contac-dt.de>
References: <bef0aa291a9f.565ef997@contac-dt.de>
Message-ID: <11C9A10F-B22C-4C7B-8112-74B93A960B7D@opencsw.org>

Hi Carsten,

> Am 02.12.2015 um 14:00 schrieb Carsten Grzemba <grzemba at contac-dt.de>:
> 
> Solaris IPS expect \d[.\d]* as version before the dash, so that package FMRI like this:
> 
> pkg:/opencsw/libwrap1 at 7.6_ipv6.4
> 
> not work. Want we simply strip other chars?

Probably yes. I remember we talked about that in Bratislava, but can?t look right now.


Best regards

  ? Dago


--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151202/536c9fc4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151202/536c9fc4/attachment.asc>

From jh at opencsw.org  Wed Dec  2 14:14:50 2015
From: jh at opencsw.org (Jan Holzhueter)
Date: Wed, 2 Dec 2015 14:14:50 +0100
Subject: IPS package versioning
In-Reply-To: <11C9A10F-B22C-4C7B-8112-74B93A960B7D@opencsw.org>
References: <bef0aa291a9f.565ef997@contac-dt.de>
	<11C9A10F-B22C-4C7B-8112-74B93A960B7D@opencsw.org>
Message-ID: <565EEECA.6050006@opencsw.org>

Am 02.12.15 um 14:06 schrieb Dagobert Michelsen:
> Hi Carsten,
> 
>> Am 02.12.2015 um 14:00 schrieb Carsten Grzemba <grzemba at contac-dt.de
>> <mailto:grzemba at contac-dt.de>>:
>>
>> Solaris IPS expect \d[.\d]* as version before the dash, so that
>> package FMRI like this:
>>
>> pkg:/opencsw/libwrap1 at 7.6_ipv6.4
>>
>> not work. Want we simply strip other chars? 
> 
> Probably yes. I remember we talked about that in Bratislava, but can?t
> look right now.

well oracle does:

pkg://solaris/archiver/gnu-tar at 1.27.1,5.11-0.175.3.0.0.30.0:20150821T161350Z

Thomas Wagner does this for SFE:
pkg://localhosts11/SFEbvi at 1.3.2,5.11-0.0.175.0.0.0.2.0:20140112T050915Z

http://sfe.opencsw.org/localhosts11/manifest/0/SFEbvi%401.3.2%2C5.11-0.0.175.0.0.0.2.0%3A20140112T050915Z

I don't know which part of the "version" number is mandatory.
I would go with

opencsw/libwrap1 at 7.6,5.11:TIMESTAMP


I don't know if we should drop package prefix though . (what if oracle
does ship libwarp1 too? might confuse people to do an install
opencsw/libwrap1 then just cswlibrap1.)

Greetings
Jan






From wilbury at opencsw.org  Wed Dec  2 14:21:45 2015
From: wilbury at opencsw.org (Juraj Lutter)
Date: Wed, 2 Dec 2015 14:21:45 +0100
Subject: IPS package versioning
In-Reply-To: <565EEECA.6050006@opencsw.org>
References: <bef0aa291a9f.565ef997@contac-dt.de>
	<11C9A10F-B22C-4C7B-8112-74B93A960B7D@opencsw.org>
	<565EEECA.6050006@opencsw.org>
Message-ID: <565EF069.4080704@opencsw.org>

On 12/02/15 14:14, Jan Holzhueter wrote:
> I don't know if we should drop package prefix though . (what if oracle
> does ship libwarp1 too? might confuse people to do an install
> opencsw/libwrap1 then just cswlibrap1.)

Just for the record:

https://docs.oracle.com/cd/E26502_01/html/E21383/pkgterms.html#gludb


-- 
Juraj Lutter <wilbury at opencsw.org>


From laurent at opencsw.org  Wed Dec  2 14:30:34 2015
From: laurent at opencsw.org (Laurent Blume)
Date: Wed, 2 Dec 2015 14:30:34 +0100
Subject: IPS package versioning
In-Reply-To: <565EF069.4080704@opencsw.org>
References: <bef0aa291a9f.565ef997@contac-dt.de>
	<11C9A10F-B22C-4C7B-8112-74B93A960B7D@opencsw.org>
	<565EEECA.6050006@opencsw.org> <565EF069.4080704@opencsw.org>
Message-ID: <565EF27A.7090307@opencsw.org>

Le 2015/12/02 14:21 +0100, Juraj Lutter a ?crit:
> On 12/02/15 14:14, Jan Holzhueter wrote:
>> I don't know if we should drop package prefix though . (what if oracle
>> does ship libwarp1 too? might confuse people to do an install
>> opencsw/libwrap1 then just cswlibrap1.)
> 
> Just for the record:
> 
> https://docs.oracle.com/cd/E26502_01/html/E21383/pkgterms.html#gludb
> 

After all those years, I'm still amazed at how disconnected with reality
the IPS designers were.

Laurent


From jh at opencsw.org  Wed Dec  2 17:23:42 2015
From: jh at opencsw.org (Jan Holzhueter)
Date: Wed, 2 Dec 2015 17:23:42 +0100
Subject: mgar branch v2-ips
In-Reply-To: <bef0fa452c7f.5655d78f@contac-dt.de>
References: <bef0fa452c7f.5655d78f@contac-dt.de>
Message-ID: <565F1B0E.6070501@opencsw.org>

Hi,
looks like one of the changes defaults to  ips build on Solaris 11.
Could you please make that an option. I need to build packages on
Solaris 11.
Thx

Greetings
Jan


Am 25.11.15 um 15:45 schrieb Carsten Grzemba:
> I like to  contribute some things for IPS and I wondering is v2-ips the
> last version and can I commit in this branch.
> 
> Casten


From grzemba at contac-dt.de  Thu Dec  3 08:08:40 2015
From: grzemba at contac-dt.de (Carsten Grzemba)
Date: Thu, 03 Dec 2015 08:08:40 +0100
Subject: mgar branch v2-ips
In-Reply-To: <565F1B0E.6070501@opencsw.org>
References: <bef0fa452c7f.5655d78f@contac-dt.de> <565F1B0E.6070501@opencsw.org>
Message-ID: <beeda776740e.565ff888@contac-dt.de>

Do you mean:

$ mgar package-srv4

?

On 02.12.15 17:23, Jan Holzhueter  <jh at opencsw.org> wrote: 
> 
> Hi,
> looks like one of the changes defaults to ips build on Solaris 11.
> Could you please make that an option. I need to build packages on
> Solaris 11.
> Thx
> 
> Greetings
> Jan
> 
> 
> Am 25.11.15 um 15:45 schrieb Carsten Grzemba:
> > I like to contribute some things for IPS and I wondering is v2-ips the
> > last version and can I commit in this branch.
> > 
> > Casten
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151203/9fdb7121/attachment.html>

From jh at opencsw.org  Thu Dec  3 09:10:38 2015
From: jh at opencsw.org (Jan Holzhueter)
Date: Thu, 3 Dec 2015 09:10:38 +0100
Subject: mgar branch v2-ips
In-Reply-To: <beeda776740e.565ff888@contac-dt.de>
References: <bef0fa452c7f.5655d78f@contac-dt.de>
	<565F1B0E.6070501@opencsw.org> <beeda776740e.565ff888@contac-dt.de>
Message-ID: <565FF8FE.1000500@opencsw.org>

Am 03.12.15 um 08:08 schrieb Carsten Grzemba:
> Do you mean:
> 
> $ mgar package-srv4

oh didn't know there is a mgar package-srv4. :)

I would until it works prefer though that on solaris 11 mgar package
defaults to package-srv4 and you just call mgar package-ips for testing.

Greetings
Jan


> 
> ?
> 
> On 02.12.15 17:23, *Jan Holzhueter * <jh at opencsw.org> wrote:
>> Hi,
>> looks like one of the changes defaults to  ips build on Solaris 11.
>> Could you please make that an option. I need to build packages on
>> Solaris 11.
>> Thx
>>
>> Greetings
>> Jan
>>
>>
>> Am 25.11.15 um 15:45 schrieb Carsten Grzemba:
>> > I like to  contribute some things for IPS and I wondering is v2-ips the
>> > last version and can I commit in this branch.
>> >
>> > Casten
>>


From dam at opencsw.org  Thu Dec  3 10:18:03 2015
From: dam at opencsw.org (Dagobert Michelsen)
Date: Thu, 3 Dec 2015 10:18:03 +0100
Subject: mgar branch v2-ips
In-Reply-To: <beeda776740e.565ff888@contac-dt.de>
References: <bef0fa452c7f.5655d78f@contac-dt.de> <565F1B0E.6070501@opencsw.org>
	<beeda776740e.565ff888@contac-dt.de>
Message-ID: <F634AF8B-353F-4E99-98B7-1EB39BFD364F@opencsw.org>

Hi Carsten,

> Am 03.12.2015 um 08:08 schrieb Carsten Grzemba <grzemba at contac-dt.de>:
> 
> Do you mean:
> 
> $ mgar package-srv4

I suggest to add different targets per platform. Currently we have
  PACKAGING_PLATFORMS ?= solaris10-sparc solaris10-i386
which should default to
  PACKAGING_PLATFORMS ?= solaris10-sparc-svr4 solaris10-i386-svr4
and
  PACKAGING_PLATFORMS ?= solaris11-sparc solaris11-i386
would default to
  PACKAGING_PLATFORMS ?= solaris11-sparc-ips solaris11-i386-ips

If you want explicitly SVR4 packages for Solaris 11 you would need to add
  PACKAGING_PLATFORMS += solaris11-sparc-svr4 solaris11-i386-svr4

This way it is up to the package to decide what to build.
Thoughts?


Best regards

  ? Dago


--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151203/82d111cc/attachment.asc>

From jh at opencsw.org  Thu Dec  3 10:23:21 2015
From: jh at opencsw.org (Jan Holzhueter)
Date: Thu, 3 Dec 2015 10:23:21 +0100
Subject: mgar branch v2-ips
In-Reply-To: <F634AF8B-353F-4E99-98B7-1EB39BFD364F@opencsw.org>
References: <bef0fa452c7f.5655d78f@contac-dt.de>
	<565F1B0E.6070501@opencsw.org> <beeda776740e.565ff888@contac-dt.de>
	<F634AF8B-353F-4E99-98B7-1EB39BFD364F@opencsw.org>
Message-ID: <56600A09.5050307@opencsw.org>

Am 03.12.15 um 10:18 schrieb Dagobert Michelsen:

> 
> I suggest to add different targets per platform. Currently we have
>   PACKAGING_PLATFORMS ?= solaris10-sparc solaris10-i386
> which should default to
>   PACKAGING_PLATFORMS ?= solaris10-sparc-svr4 solaris10-i386-svr4
> and
>   PACKAGING_PLATFORMS ?= solaris11-sparc solaris11-i386
> would default to
>   PACKAGING_PLATFORMS ?= solaris11-sparc-ips solaris11-i386-ips
> 
> If you want explicitly SVR4 packages for Solaris 11 you would need to add
>   PACKAGING_PLATFORMS += solaris11-sparc-svr4 solaris11-i386-svr4
> 
> This way it is up to the package to decide what to build.
> Thoughts?

That would kick off a whole new build just to have differend "packages".
(Quite time consuming on large builds)
We need both at the beginning for Solaris 11 anyway. So I would just
like to have e.g. PACKGINING_TARGET=srv4 ips. So it would just package
twice on s11. Not sure if thats possibale with the gar layout.

Greetings
Jan



From dam at opencsw.org  Thu Dec  3 10:48:34 2015
From: dam at opencsw.org (Dagobert Michelsen)
Date: Thu, 3 Dec 2015 10:48:34 +0100
Subject: mgar branch v2-ips
In-Reply-To: <56600A09.5050307@opencsw.org>
References: <bef0fa452c7f.5655d78f@contac-dt.de> <565F1B0E.6070501@opencsw.org>
	<beeda776740e.565ff888@contac-dt.de>
	<F634AF8B-353F-4E99-98B7-1EB39BFD364F@opencsw.org>
	<56600A09.5050307@opencsw.org>
Message-ID: <87DFB9E1-1DDB-4525-9C21-86364FA983FF@opencsw.org>

Hi Jan,

Am 03.12.2015 um 10:23 schrieb Jan Holzhueter <jh at opencsw.org>:
> Am 03.12.15 um 10:18 schrieb Dagobert Michelsen:
>> I suggest to add different targets per platform. Currently we have
>>  PACKAGING_PLATFORMS ?= solaris10-sparc solaris10-i386
>> which should default to
>>  PACKAGING_PLATFORMS ?= solaris10-sparc-svr4 solaris10-i386-svr4
>> and
>>  PACKAGING_PLATFORMS ?= solaris11-sparc solaris11-i386
>> would default to
>>  PACKAGING_PLATFORMS ?= solaris11-sparc-ips solaris11-i386-ips
>> 
>> If you want explicitly SVR4 packages for Solaris 11 you would need to add
>>  PACKAGING_PLATFORMS += solaris11-sparc-svr4 solaris11-i386-svr4
>> 
>> This way it is up to the package to decide what to build.
>> Thoughts?
> 
> That would kick off a whole new build just to have differend "packages".
> (Quite time consuming on large builds)
> We need both at the beginning for Solaris 11 anyway. So I would just
> like to have e.g. PACKGINING_TARGET=srv4 ips. So it would just package
> twice on s11. Not sure if thats possibale with the gar layout.

The problem is the merging: with separate platforms for ips and srv4 you
can adjust the merging to honour specific layouts. Apart from that it
may be useful to depend on other IPS packages instead of our own ones
which requires a different build anyway.


Best regards

  ? Dago

--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151203/cd2f02df/attachment-0001.asc>

From grzemba at contac-dt.de  Fri Dec  4 08:18:20 2015
From: grzemba at contac-dt.de (Carsten Grzemba)
Date: Fri, 04 Dec 2015 08:18:20 +0100
Subject: IPS package versioning
In-Reply-To: <565EEECA.6050006@opencsw.org>
References: <bef0aa291a9f.565ef997@contac-dt.de>
	<11C9A10F-B22C-4C7B-8112-74B93A960B7D@opencsw.org>
	<565EEECA.6050006@opencsw.org>
Message-ID: <befdf18c363a.56614c4c@contac-dt.de>

simply strip will not work: eg. openssl at 1.0.1.p
Oracle converts 1.0.1p to: 1.0.1.16

On 02.12.15 14:15, Jan Holzhueter  <jh at opencsw.org> wrote: 
> 
> Am 02.12.15 um 14:06 schrieb Dagobert Michelsen:
> > Hi Carsten,
> > 
> >> Am 02.12.2015 um 14:00 schrieb Carsten Grzemba <grzemba at contac-dt.de
> >> <mailto:grzemba at contac-dt.de <grzemba at contac-dt.de>>>:
> >>
> >> Solaris IPS expect \d[.\d]* as version before the dash, so that
> >> package FMRI like this:
> >>
> >> pkg:/opencsw/libwrap1 at 7.6_ipv6.4
> >>
> >> not work. Want we simply strip other chars? 
> > 
> > Probably yes. I remember we talked about that in Bratislava, but can?t
> > look right now.
> 
> well oracle does:
> 
> pkg://solaris/archiver/gnu-tar at 1.27.1,5.11-0.175.3.0.0.30.0:20150821T161350Z
> 
> Thomas Wagner does this for SFE:
> pkg://localhosts11/SFEbvi at 1.3.2,5.11-0.0.175.0.0.0.2.0:20140112T050915Z
> 
> http://sfe.opencsw.org/localhosts11/manifest/0/SFEbvi%401.3.2%2C5.11-0.0.175.0.0.0.2.0%3A20140112T050915Z
> 
> I don't know which part of the "version" number is mandatory.
> I would go with
> 
> opencsw/libwrap1 at 7.6,5.11:TIMESTAMP
> 
> 
> I don't know if we should drop package prefix though . (what if oracle
> does ship libwarp1 too? might confuse people to do an install
> opencsw/libwrap1 then just cswlibrap1.)
> 
> Greetings
> Jan
> 
> 
> 
> 
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151204/20fe8297/attachment.html>

From dam at opencsw.org  Fri Dec  4 09:10:23 2015
From: dam at opencsw.org (Dagobert Michelsen)
Date: Fri, 4 Dec 2015 09:10:23 +0100
Subject: IPS package versioning
In-Reply-To: <befdf18c363a.56614c4c@contac-dt.de>
References: <bef0aa291a9f.565ef997@contac-dt.de>
	<11C9A10F-B22C-4C7B-8112-74B93A960B7D@opencsw.org>
	<565EEECA.6050006@opencsw.org> <befdf18c363a.56614c4c@contac-dt.de>
Message-ID: <791ACBDC-5C8C-461A-8203-C38B06F5AF09@opencsw.org>

Hi Carsten,

Am 04.12.2015 um 08:18 schrieb Carsten Grzemba <grzemba at contac-dt.de>:
> simply strip will not work: eg. openssl at 1.0.1.p
> Oracle converts 1.0.1p to: 1.0.1.16

I suggest to use something like
  VERSION_IPS
when the regular VERSION contains extra characters. Automatic conversion
will most like yield to problems.


Best regards

  ? Dago

--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151204/f5140158/attachment.asc>

From wilbury at opencsw.org  Fri Dec  4 13:04:53 2015
From: wilbury at opencsw.org (Juraj Lutter)
Date: Fri, 4 Dec 2015 13:04:53 +0100
Subject: CSWnetsnmpd crash
Message-ID: <56618165.5070301@opencsw.org>

Folks,

after firing up a VLAN subinterface on recent S10/x64, I'm getting core
dump on netsnmpd start.

pstack shows:

root@[backup /root]# pstack core
core 'core' of 23105:   /opt/csw/sbin/snmpd
 fec8673f ipAddressTable_container_load (8169970, 0, feb740d5, fec868bc,
8047780, fefc2cd4) + 2f
 fec868fc ipAddressTable_container_init (fedbf1c0, 8169928, 4, 0,
80477c0, fefc2cd4) + 5c
 fec84dcf _ipAddressTable_initialize_interface (0, 0, feb740d5,
fec6b569) + bf
 fec6b5e5 initialize_table_ipAddressTable (8047830, fefc2cd4, fef605f8,
2830, fecb2a65, 1) + 95
 fec6b628 init_ipAddressTable (fecb1f39, 80658b4, 8047ac8, 8053865, 0,
6480) + 38
 fecb2a65 init_mib_modules (0, 6480, 5522e44d, 0, 0, ffffffff) + b35
 08053865 main     (8052760, 1, 8047aec) + b55


are you aware of such behaviour?

   VERSION:  5.7.3,REV=2015.04.06

I think that: http://sourceforge.net/p/net-snmp/bugs/1870/ still applies.


Thanks.


-- 
Juraj Lutter <wilbury at opencsw.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151204/3f825a51/attachment.html>

From grzemba at contac-dt.de  Wed Dec  9 12:13:32 2015
From: grzemba at contac-dt.de (Carsten Grzemba)
Date: Wed, 09 Dec 2015 12:13:32 +0100
Subject: packaging in IPS
Message-ID: <be41c8bc1770.56681aec@contac-dt.de>

Hi folks,

for SVR4 packages we use a concept to package shared libs, header files and manuals in own packages like:
CSWlibssl1-0-0 CSWlibssl-dev CSWopenssl-utils
Although there are facets for IPS packages, I would suggest to keep this concept also for IPS packages. 

Any thoughts?

Carsten
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151209/53ce8b38/attachment.html>

From laurent at opencsw.org  Wed Dec  9 12:20:30 2015
From: laurent at opencsw.org (Laurent Blume)
Date: Wed, 9 Dec 2015 12:20:30 +0100
Subject: packaging in IPS
In-Reply-To: <be41c8bc1770.56681aec@contac-dt.de>
References: <be41c8bc1770.56681aec@contac-dt.de>
Message-ID: <56680E7E.30809@opencsw.org>

Le 2015/12/09 12:13 +0100, Carsten Grzemba a ?crit:
> Hi folks,
> 
> for SVR4 packages we use a concept to package shared libs, header files
> and manuals in own packages like:
> CSWlibssl1-0-0 CSWlibssl-dev CSWopenssl-utils
> Although there are facets for IPS packages, I would suggest to keep this
> concept also for IPS packages

Agreed. Facets are another needlessly confusing innovation, different
for the sake of difference.

Laurent

From wilbury at opencsw.org  Wed Dec  9 12:24:48 2015
From: wilbury at opencsw.org (Juraj Lutter)
Date: Wed, 9 Dec 2015 12:24:48 +0100
Subject: packaging in IPS
In-Reply-To: <56680E7E.30809@opencsw.org>
References: <be41c8bc1770.56681aec@contac-dt.de> <56680E7E.30809@opencsw.org>
Message-ID: <56680F80.5010005@opencsw.org>

On 12/09/15 12:20, Laurent Blume wrote:
> Le 2015/12/09 12:13 +0100, Carsten Grzemba a ?crit:
>> Hi folks,
>>
>> for SVR4 packages we use a concept to package shared libs, header files
>> and manuals in own packages like:
>> CSWlibssl1-0-0 CSWlibssl-dev CSWopenssl-utils
>> Although there are facets for IPS packages, I would suggest to keep this
>> concept also for IPS packages
> Agreed. Facets are another needlessly confusing innovation, different
> for the sake of difference.

I'd preferably go with facets, to be more consistent with IPS concepts.
We can disaggree with them but they are here and we could probably avoid
problems that may arise in the future.

jl

-- 
Juraj Lutter <wilbury at opencsw.org>


From dam at opencsw.org  Wed Dec  9 12:46:54 2015
From: dam at opencsw.org (Dagobert Michelsen)
Date: Wed, 9 Dec 2015 12:46:54 +0100
Subject: packaging in IPS
In-Reply-To: <56680F80.5010005@opencsw.org>
References: <be41c8bc1770.56681aec@contac-dt.de> <56680E7E.30809@opencsw.org>
	<56680F80.5010005@opencsw.org>
Message-ID: <43DD8842-98D1-4D0F-B3B1-6E0E26CB26C2@opencsw.org>

Hi,

Am 09.12.2015 um 12:24 schrieb Juraj Lutter <wilbury at opencsw.org>:
> On 12/09/15 12:20, Laurent Blume wrote:
>> Le 2015/12/09 12:13 +0100, Carsten Grzemba a ?crit:
>>> Hi folks,
>>> 
>>> for SVR4 packages we use a concept to package shared libs, header files
>>> and manuals in own packages like:
>>> CSWlibssl1-0-0 CSWlibssl-dev CSWopenssl-utils
>>> Although there are facets for IPS packages, I would suggest to keep this
>>> concept also for IPS packages
>> Agreed. Facets are another needlessly confusing innovation, different
>> for the sake of difference.
> 
> I'd preferably go with facets, to be more consistent with IPS concepts.
> We can disaggree with them but they are here and we could probably avoid
> problems that may arise in the future.

+1 for facets, the selection can be done automatically by GAR in much the same
way as it is now with PKGFILES_DEVEL. Same goes for language support.


Best regards

  ? Dago

--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151209/b8e63d93/attachment-0001.asc>

From laurent at opencsw.org  Wed Dec  9 12:58:24 2015
From: laurent at opencsw.org (Laurent Blume)
Date: Wed, 9 Dec 2015 12:58:24 +0100
Subject: packaging in IPS
In-Reply-To: <56680F80.5010005@opencsw.org>
References: <be41c8bc1770.56681aec@contac-dt.de> <56680E7E.30809@opencsw.org>
	<56680F80.5010005@opencsw.org>
Message-ID: <56681760.9060403@opencsw.org>

Le 2015/12/09 12:24 +0100, Juraj Lutter a ?crit:
> I'd preferably go with facets, to be more consistent with IPS concepts.
> We can disaggree with them but they are here and we could probably avoid
> problems that may arise in the future.

They are here, and they are one reason I decided to not migrate to S11
in the first place.
What problem exists that they fix? What problem may arise in the future?
Concrete examples please, not FUD.
I'm not a fan of using stuff just because it's lying around. I use stuff
when it's the most fit solution to a problem.

Laurent









From dam at opencsw.org  Wed Dec  9 13:40:30 2015
From: dam at opencsw.org (Dagobert Michelsen)
Date: Wed, 9 Dec 2015 13:40:30 +0100
Subject: packaging in IPS
In-Reply-To: <56681760.9060403@opencsw.org>
References: <be41c8bc1770.56681aec@contac-dt.de> <56680E7E.30809@opencsw.org>
	<56680F80.5010005@opencsw.org> <56681760.9060403@opencsw.org>
Message-ID: <5F42464E-E765-4696-8072-C5E1CD47F633@opencsw.org>

Hi Laurent,

Am 09.12.2015 um 12:58 schrieb Laurent Blume <laurent at opencsw.org>:
> Le 2015/12/09 12:24 +0100, Juraj Lutter a ?crit:
>> I'd preferably go with facets, to be more consistent with IPS concepts.
>> We can disaggree with them but they are here and we could probably avoid
>> problems that may arise in the future.
> 
> They are here, and they are one reason I decided to not migrate to S11
> in the first place.
> What problem exists that they fix? What problem may arise in the future?
> Concrete examples please, not FUD.
> I'm not a fan of using stuff just because it's lying around. I use stuff
> when it's the most fit solution to a problem.

1. Enable/Disable development files

I thought of having this also in SVR4 packages with pkgutil by having an attribute
for each package which lists the development package name.

2. Switch to development version with debug symbols enabled and w/o optimization

I would have wished it would be easier on deployed systems which show bugs to switch
to debug binaries/libs easily.


Best regards

  ? Dago

--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151209/e377a809/attachment.asc>

From grzemba at contac-dt.de  Wed Dec  9 14:40:18 2015
From: grzemba at contac-dt.de (Carsten Grzemba)
Date: Wed, 09 Dec 2015 14:40:18 +0100
Subject: packaging in IPS
In-Reply-To: <43DD8842-98D1-4D0F-B3B1-6E0E26CB26C2@opencsw.org>
References: <be41c8bc1770.56681aec@contac-dt.de> <56680E7E.30809@opencsw.org>
	<56680F80.5010005@opencsw.org>
	<43DD8842-98D1-4D0F-B3B1-6E0E26CB26C2@opencsw.org>
Message-ID: <befd8e88739c.56683d52@contac-dt.de>



On 09.12.15 12:47, Dagobert Michelsen  <dam at opencsw.org> wrote: 
> 
> Hi,
> 
> Am 09.12.2015 um 12:24 schrieb Juraj Lutter <wilbury at opencsw.org>:
> > On 12/09/15 12:20, Laurent Blume wrote:
> >> Le 2015/12/09 12:13 +0100, Carsten Grzemba a ?crit:
> >>> Hi folks,
> >>> 
> >>> for SVR4 packages we use a concept to package shared libs, header files
> >>> and manuals in own packages like:
> >>> CSWlibssl1-0-0 CSWlibssl-dev CSWopenssl-utils
> >>> Although there are facets for IPS packages, I would suggest to keep this
> >>> concept also for IPS packages
> >> Agreed. Facets are another needlessly confusing innovation, different
> >> for the sake of difference.
> > 
> > I'd preferably go with facets, to be more consistent with IPS concepts.
> > We can disaggree with them but they are here and we could probably avoid
> > problems that may arise in the future.
> 
> +1 for facets, the selection can be done automatically by GAR in much the same
> way as it is now with PKGFILES_DEVEL. Same goes for language support.
> 
But it is no solution for shared libraries, if there are different versions needed by different packages.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151209/4e86c8dc/attachment.html>

From dam at opencsw.org  Wed Dec  9 14:42:55 2015
From: dam at opencsw.org (Dagobert Michelsen)
Date: Wed, 9 Dec 2015 14:42:55 +0100
Subject: packaging in IPS
In-Reply-To: <befd8e88739c.56683d52@contac-dt.de>
References: <be41c8bc1770.56681aec@contac-dt.de> <56680E7E.30809@opencsw.org>
	<56680F80.5010005@opencsw.org>
	<43DD8842-98D1-4D0F-B3B1-6E0E26CB26C2@opencsw.org>
	<befd8e88739c.56683d52@contac-dt.de>
Message-ID: <5FBF7ABA-0D2E-4403-9695-9E92787D7D85@opencsw.org>

Hi Carsten,

> Am 09.12.2015 um 14:40 schrieb Carsten Grzemba <grzemba at contac-dt.de>:
> 
> 
> 
> On 09.12.15 12:47, Dagobert Michelsen <dam at opencsw.org <mailto:dam at opencsw.org>> wrote:
>> 
>> Hi,
>> 
>> Am 09.12.2015 um 12:24 schrieb Juraj Lutter <wilbury at opencsw.org>:
>> > On 12/09/15 12:20, Laurent Blume wrote:
>> >> Le 2015/12/09 12:13 +0100, Carsten Grzemba a ?crit:
>> >>> Hi folks,
>> >>>
>> >>> for SVR4 packages we use a concept to package shared libs, header files
>> >>> and manuals in own packages like:
>> >>> CSWlibssl1-0-0 CSWlibssl-dev CSWopenssl-utils
>> >>> Although there are facets for IPS packages, I would suggest to keep this
>> >>> concept also for IPS packages
>> >> Agreed. Facets are another needlessly confusing innovation, different
>> >> for the sake of difference.
>> >
>> > I'd preferably go with facets, to be more consistent with IPS concepts.
>> > We can disaggree with them but they are here and we could probably avoid
>> > problems that may arise in the future.
>> 
>> +1 for facets, the selection can be done automatically by GAR in much the same
>> way as it is now with PKGFILES_DEVEL. Same goes for language support.
> But it is no solution for shared libraries, if there are different versions needed by different packages.

Definitely not, for the shared libs I would stick to the OpenCSW naming by including the soname into the package name.


Best regards

  ? Dago


--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151209/1dd129ac/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151209/1dd129ac/attachment.asc>

From rmottola at opencsw.org  Wed Dec  9 15:17:35 2015
From: rmottola at opencsw.org (Riccardo Mottola)
Date: Wed, 9 Dec 2015 15:17:35 +0100
Subject: x86 build failure : __sync_sub_and_fetch_4
Message-ID: <566837FF.8010900@opencsw.org>

Hi,

while building a new release of gnustep-base, I get this failure on 
unstable9x

Making all for tool autogsdoc...
/opt/csw/bin/gcc-4.6      -m32 -march=i386 -L/opt/csw/GNUstep/lib 
-L/opt/csw/lib -shared-libgcc  -pthread -fexceptions -fgnu-runtime -o 
obj/autogsdoc \
         ./obj/autogsdoc.obj/autogsdoc.m.o 
./obj/autogsdoc.obj/AGSParser.m.o ./obj/autogsdoc.obj/AGSOutput.m.o 
./obj/autogsdoc.obj/AGSIndex.m.o ./obj/autogsdoc.obj/AGSHtml.m.o \
           -L../Source/./obj 
-L/home/rmottola/GNUstep/Library/Libraries 
-L/opt/csw/GNUstep/Local/Library/Libraries 
-L/opt/csw/GNUstep/System/Library/Libraries 
-L/opt/csw/GNUstep/Local/Library/Libraries 
-L/opt/csw/GNUstep/Local/Library/Libraries 
-L/opt/csw/GNUstep/System/Library/Libraries -L/opt/csw/lib 
-lgnustep-base   -lpthread -lobjc   -lsocket -lnsl -lm
Undefined                       first referenced
  symbol                             in file
__sync_sub_and_fetch_4              ../Source/./obj/libgnustep-base.so
__sync_add_and_fetch_4              ../Source/./obj/libgnustep-base.so
ld: fatal: Symbol referencing errors. No output written to obj/autogsdoc

Have you aready experienced something like that?

 From what I could gather from the internet, this is caused by forcing 
i386 because those functions are available only on >= 486 as atomic 
function.
If someone can confirm that this is the problem, is it it reasonable to 
compile for 486 and up only? What's the best way to set march ?

Riccardo

From dam at opencsw.org  Wed Dec  9 15:20:05 2015
From: dam at opencsw.org (Dagobert Michelsen)
Date: Wed, 9 Dec 2015 15:20:05 +0100
Subject: x86 build failure : __sync_sub_and_fetch_4
In-Reply-To: <566837FF.8010900@opencsw.org>
References: <566837FF.8010900@opencsw.org>
Message-ID: <8E607D93-D70D-4E58-82CB-F9DD156CDB26@opencsw.org>

Hi Riccrdo,

Am 09.12.2015 um 15:17 schrieb Riccardo Mottola <rmottola at opencsw.org>:
> while building a new release of gnustep-base, I get this failure on unstable9x
> 
> Making all for tool autogsdoc...
> /opt/csw/bin/gcc-4.6      -m32 -march=i386 -L/opt/csw/GNUstep/lib -L/opt/csw/lib -shared-libgcc  -pthread -fexceptions -fgnu-runtime -o obj/autogsdoc \
>        ./obj/autogsdoc.obj/autogsdoc.m.o ./obj/autogsdoc.obj/AGSParser.m.o ./obj/autogsdoc.obj/AGSOutput.m.o ./obj/autogsdoc.obj/AGSIndex.m.o ./obj/autogsdoc.obj/AGSHtml.m.o \
>          -L../Source/./obj -L/home/rmottola/GNUstep/Library/Libraries -L/opt/csw/GNUstep/Local/Library/Libraries -L/opt/csw/GNUstep/System/Library/Libraries -L/opt/csw/GNUstep/Local/Library/Libraries -L/opt/csw/GNUstep/Local/Library/Libraries -L/opt/csw/GNUstep/System/Library/Libraries -L/opt/csw/lib -lgnustep-base   -lpthread -lobjc   -lsocket -lnsl -lm
> Undefined                       first referenced
> symbol                             in file
> __sync_sub_and_fetch_4              ../Source/./obj/libgnustep-base.so
> __sync_add_and_fetch_4              ../Source/./obj/libgnustep-base.so
> ld: fatal: Symbol referencing errors. No output written to obj/autogsdoc
> 
> Have you aready experienced something like that?

Sure:
  http://wiki.opencsw.org/porting-faq#toc8

> From what I could gather from the internet, this is caused by forcing i386 because those functions are available only on >= 486 as atomic function.
> If someone can confirm that this is the problem, is it it reasonable to compile for 486 and up only? What's the best way to set march ?

I doubt you can run on a CPU which does not support 486 commands, so it is most certainly ok.


Best regards

  ? Dago

--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151209/734c745b/attachment.asc>

From rmottola at opencsw.org  Wed Dec  9 15:26:32 2015
From: rmottola at opencsw.org (Riccardo Mottola)
Date: Wed, 9 Dec 2015 15:26:32 +0100
Subject: x86 build failure : __sync_sub_and_fetch_4
In-Reply-To: <8E607D93-D70D-4E58-82CB-F9DD156CDB26@opencsw.org>
References: <566837FF.8010900@opencsw.org>
	<8E607D93-D70D-4E58-82CB-F9DD156CDB26@opencsw.org>
Message-ID: <56683A18.4030507@opencsw.org>

Hi,


Dagobert Michelsen wrote:
>>  From what I could gather from the internet, this is caused by forcing i386 because those functions are available only on >= 486 as atomic function.
>> >If someone can confirm that this is the problem, is it it reasonable to compile for 486 and up only? What's the best way to set march ?
> I doubt you can run on a CPU which does not support 486 commands, so it is most certainly ok.

I doubt that too.
On the FAQ you suggest removing OPT flags. I would instead rising the 
ARCH version. How is that best accomplished?

/opt/csw/bin/gcc-4.6      -m32 -march=i386

march = i486
would be more appropriate, but it should happen only during x86 builds, 
not amd64 so I don't want to force it.

Thanks

From grzemba at contac-dt.de  Wed Dec  9 15:29:23 2015
From: grzemba at contac-dt.de (Carsten Grzemba)
Date: Wed, 09 Dec 2015 15:29:23 +0100
Subject: packaging in IPS
In-Reply-To: <5FBF7ABA-0D2E-4403-9695-9E92787D7D85@opencsw.org>
References: <be41c8bc1770.56681aec@contac-dt.de> <56680E7E.30809@opencsw.org>
	<56680F80.5010005@opencsw.org>
	<43DD8842-98D1-4D0F-B3B1-6E0E26CB26C2@opencsw.org>
	<befd8e88739c.56683d52@contac-dt.de>
	<5FBF7ABA-0D2E-4403-9695-9E92787D7D85@opencsw.org>
Message-ID: <be41b9652be9.566848d3@contac-dt.de>

Hi Dago,

On 09.12.15 14:43, Dagobert Michelsen  <dam at opencsw.org> wrote: 
> 
> 
> 
> 
> 
> 
> Hi Carsten,
> 
> 
> 
> 
> > 
> > Am 09.12.2015 um 14:40 schrieb Carsten Grzemba <grzemba at contac-dt.de>:
> > 
> > 
> > 
> > 
> > On 09.12.15 12:47,  Dagobert Michelsen  <dam at opencsw.org> wrote: 
> > > 
> > > Hi,
> > > 
> > > Am 09.12.2015 um 12:24 schrieb Juraj Lutter <wilbury at opencsw.org>:
> > > > On 12/09/15 12:20, Laurent Blume wrote:
> > > >> Le 2015/12/09 12:13 +0100, Carsten Grzemba a ?crit:
> > > >>> Hi folks,
> > > >>>  
> > > >>> for SVR4 packages we use a concept to package shared libs, header files
> > > >>> and manuals in own packages like:
> > > >>> CSWlibssl1-0-0 CSWlibssl-dev CSWopenssl-utils
> > > >>> Although there are facets for IPS packages, I would suggest to keep this
> > > >>> concept also for IPS packages
> > > >> Agreed. Facets are another needlessly confusing innovation, different
> > > >> for the sake of difference.
> > > >  
> > > > I'd preferably go with facets, to be more consistent with IPS concepts.
> > > > We can disaggree with them but they are here and we could probably avoid
> > > > problems that may arise in the future.
> > > 
> > > +1 for facets, the selection can be done automatically by GAR in much the same
> > > way as it is now with PKGFILES_DEVEL. Same goes for language support.
> > > 
> > > 
> > But it is no solution for shared libraries, if there are different versions needed by different packages. 
> > 
> 
> 
> Definitely not, for the shared libs I would stick to the OpenCSW naming by including the soname into the package name.
> 
>  
> 

Ok, so we need the pathfilter also for IPS and the mgar package target has to be able to build multiple packages also.
Perhaps we can keep the PACKAGES like SRV4 but substitute the dev and doc packages by facets?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151209/76629e7c/attachment.html>

From dam at opencsw.org  Wed Dec  9 15:32:58 2015
From: dam at opencsw.org (Dagobert Michelsen)
Date: Wed, 9 Dec 2015 15:32:58 +0100
Subject: x86 build failure : __sync_sub_and_fetch_4
In-Reply-To: <56683A18.4030507@opencsw.org>
References: <566837FF.8010900@opencsw.org>
	<8E607D93-D70D-4E58-82CB-F9DD156CDB26@opencsw.org>
	<56683A18.4030507@opencsw.org>
Message-ID: <EA79766C-49DC-4212-9C90-A0A18F02A503@opencsw.org>

Hi Riccardo,

Am 09.12.2015 um 15:26 schrieb Riccardo Mottola <rmottola at opencsw.org>:
> Dagobert Michelsen wrote:
>>> From what I could gather from the internet, this is caused by forcing i386 because those functions are available only on >= 486 as atomic function.
>>> >If someone can confirm that this is the problem, is it it reasonable to compile for 486 and up only? What's the best way to set march ?
>> I doubt you can run on a CPU which does not support 486 commands, so it is most certainly ok.
> 
> I doubt that too.
> On the FAQ you suggest removing OPT flags. I would instead rising the ARCH version. How is that best accomplished?
> 
> /opt/csw/bin/gcc-4.6      -m32 -march=i386
> 
> march = i486
> would be more appropriate, but it should happen only during x86 builds, not amd64 so I don't want to force it.

Look here:
  https://buildfarm.opencsw.org/source/xref/opencsw/csw/mgar/gar/v2/gar.conf.mk#520

ISA_DEFAULT_i386-5.9 = pentium_pro


Best regards

  ? Dago

--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151209/7d4e6378/attachment.asc>

From laurent at opencsw.org  Wed Dec  9 15:35:49 2015
From: laurent at opencsw.org (Laurent Blume)
Date: Wed, 9 Dec 2015 15:35:49 +0100
Subject: packaging in IPS
In-Reply-To: <5F42464E-E765-4696-8072-C5E1CD47F633@opencsw.org>
References: <be41c8bc1770.56681aec@contac-dt.de> <56680E7E.30809@opencsw.org>
	<56680F80.5010005@opencsw.org> <56681760.9060403@opencsw.org>
	<5F42464E-E765-4696-8072-C5E1CD47F633@opencsw.org>
Message-ID: <56683C45.4050104@opencsw.org>

Le 2015/12/09 13:40 +0100, Dagobert Michelsen a ?crit:
> 1. Enable/Disable development files
> 
> I thought of having this also in SVR4 packages with pkgutil by having an attribute
> for each package which lists the development package name.
> 
> 2. Switch to development version with debug symbols enabled and w/o optimization
> 
> I would have wished it would be easier on deployed systems which show bugs to switch
> to debug binaries/libs easily.

That's comparing it to SVR4 packaging.
There are plenty of distros systems out there which do those functions
just fine with -devel and -debuginfo packages. It's simple to
understand, simple to use, you don't even need to read the manual.
Solaris did not gain *anything*, *at all*, by introducing confusing
features that did things differently from everybody else, and OpenCSW is
not going to gain users nor maintainers by following them that way.

Compare two typical discussions:
?Development files, we do it the same way as Red Hat does, install the
-devel package.
 - Ok, get it?

?Development files, you only need to install the devel facet, the same
was as Oracle does.
 - Wait, facet? What's that?
 - You know, it's [I don't know how to explain it myself]
 - I don't get it.
 - Have you looked at the man?
 - No, reading man in Solaris sucks [true fact].
 - Have you looked at the docs on Oracle.com?
 [at this point, we've lost them]?

And using that in a production environment means you have to duplicate
and upgrade the documentation, when it could just be the exact same as
what was for S10, merely adding new examples of commands.

It's like building cycloid-shaped roads because Sun decided to build
square wheels.

But seriously, you don't really have to listen to me :) It's just my -0
for facets and any similar IPS crapola, since I'll never work on or with
it (well, unless there are significantly astronomical sums of money
involved ;)

Laurent

From rmottola at opencsw.org  Wed Dec  9 16:23:25 2015
From: rmottola at opencsw.org (Riccardo Mottola)
Date: Wed, 9 Dec 2015 16:23:25 +0100
Subject: x86 build failure : __sync_sub_and_fetch_4
In-Reply-To: <EA79766C-49DC-4212-9C90-A0A18F02A503@opencsw.org>
References: <566837FF.8010900@opencsw.org>
	<8E607D93-D70D-4E58-82CB-F9DD156CDB26@opencsw.org>
	<56683A18.4030507@opencsw.org>
	<EA79766C-49DC-4212-9C90-A0A18F02A503@opencsw.org>
Message-ID: <5668476D.3090807@opencsw.org>

Hi Dago,

Dagobert Michelsen wrote:
> Look here:
>    https://buildfarm.opencsw.org/source/xref/opencsw/csw/mgar/gar/v2/gar.conf.mk#520
>
> ISA_DEFAULT_i386-5.9 = pentium_pro

can I set that in my receipe?

I tried copying exactly that line and also tried "pentium" instead of 
pentium_pro, but I still see:
/opt/csw/bin/gcc-4.6      -m32 -march=i386

setting the default in .garrc would still require everybody else 
building a receipe that doesn't build by default, I'd prefer having it 
set in the receipe.


Thanks - Riccardo

From dam at opencsw.org  Fri Dec 11 14:44:42 2015
From: dam at opencsw.org (Dagobert Michelsen)
Date: Fri, 11 Dec 2015 14:44:42 +0100
Subject: Update to GCC5 on buildfarm
Message-ID: <7531787E-5087-4AAD-9B96-AAD04C0331D9@opencsw.org>

Hi folks,

I just updated GCC to 5.2.0 on unstable10* and unstable11*. For smooth support
please also update your copy of GAR to accomodate for automatic builds with GCC5
with ?mgar up?.

As always: if you encounter something suspicious just let me know.



Best regards

  ? Dago

--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151211/91322341/attachment.asc>

From bonivart at opencsw.org  Mon Dec 14 17:40:54 2015
From: bonivart at opencsw.org (Peter Bonivart)
Date: Mon, 14 Dec 2015 17:40:54 +0100
Subject: Fwd: ClamAv & Icap & ZFS
In-Reply-To: <566EE89E.20509@gmx.co.uk>
References: <566EE89E.20509@gmx.co.uk>
Message-ID: <CABY0g1Vb=_PvswU51qdNqSX0x0i3nD7b3z0v-m-PJztPoZOiig@mail.gmail.com>

I'm not sure that Juraj reads the users list so I forwarded it here as well.

/peter


---------- Forwarded message ----------
From: Ian Prideaux <worzel at gmx.co.uk>
Date: Mon, Dec 14, 2015 at 5:04 PM
Subject: ClamAv & Icap & ZFS
To: users at lists.opencsw.org


Hi All,

I guess that this is for Juraj Lutter & Peter Bonivart, but if anyone
else can tell me, then all to the good.

I've got clamav (& freshclam) downloaded & working. However I'd like to
be able to have clamv with ZFS (install the virus-scan package, enable
the virus scan service, and set the vscan property of the filesystem).

Apparently to do this I need to have p_icap running. However, the
version on OpenCSW is 0.1.7 and is from 2012.06.02. This is several
versions out of date. The latest is 0.4.2 from 2015.08.28.

Are there any plans to get the latest version available?

Thanks.

From wilbury at opencsw.org  Mon Dec 14 18:13:09 2015
From: wilbury at opencsw.org (Juraj Lutter)
Date: Mon, 14 Dec 2015 18:13:09 +0100
Subject: Fwd: ClamAv & Icap & ZFS
In-Reply-To: <CABY0g1Vb=_PvswU51qdNqSX0x0i3nD7b3z0v-m-PJztPoZOiig@mail.gmail.com>
References: <566EE89E.20509@gmx.co.uk>
	<CABY0g1Vb=_PvswU51qdNqSX0x0i3nD7b3z0v-m-PJztPoZOiig@mail.gmail.com>
Message-ID: <566EF8A5.3090109@opencsw.org>

I will take a look at thursday.

On 12/14/2015 05:40 PM, Peter Bonivart wrote:
> I'm not sure that Juraj reads the users list so I forwarded it here as well.
>
> /peter
>
>
> ---------- Forwarded message ----------
> From: Ian Prideaux <worzel at gmx.co.uk>
> Date: Mon, Dec 14, 2015 at 5:04 PM
> Subject: ClamAv & Icap & ZFS
> To: users at lists.opencsw.org
>
>
> Hi All,
>
> I guess that this is for Juraj Lutter & Peter Bonivart, but if anyone
> else can tell me, then all to the good.
>
> I've got clamav (& freshclam) downloaded & working. However I'd like to
> be able to have clamv with ZFS (install the virus-scan package, enable
> the virus scan service, and set the vscan property of the filesystem).
>
> Apparently to do this I need to have p_icap running. However, the
> version on OpenCSW is 0.1.7 and is from 2012.06.02. This is several
> versions out of date. The latest is 0.4.2 from 2015.08.28.
>
> Are there any plans to get the latest version available?
>
> Thanks.


-- 
Juraj Lutter <wilbury at opencsw.org>


From dam at opencsw.org  Wed Dec 16 09:32:43 2015
From: dam at opencsw.org (Dagobert Michelsen)
Date: Wed, 16 Dec 2015 09:32:43 +0100
Subject: packaging in IPS
In-Reply-To: <56683C45.4050104@opencsw.org>
References: <be41c8bc1770.56681aec@contac-dt.de> <56680E7E.30809@opencsw.org>
	<56680F80.5010005@opencsw.org> <56681760.9060403@opencsw.org>
	<5F42464E-E765-4696-8072-C5E1CD47F633@opencsw.org>
	<56683C45.4050104@opencsw.org>
Message-ID: <9CE37919-7E11-478F-B14F-44A6E123C6DD@opencsw.org>

Hi Laurent,

Am 09.12.2015 um 15:35 schrieb Laurent Blume <laurent at opencsw.org>:
> That's comparing it to SVR4 packaging.
> There are plenty of distros systems out there which do those functions
> just fine with -devel and -debuginfo packages. It's simple to
> understand, simple to use, you don't even need to read the manual.
> Solaris did not gain *anything*, *at all*, by introducing confusing
> features that did things differently from everybody else, and OpenCSW is
> not going to gain users nor maintainers by following them that way.
> 
> Compare two typical discussions:
> ?Development files, we do it the same way as Red Hat does, install the
> -devel package.
> - Ok, get it?
> 
> ?Development files, you only need to install the devel facet, the same
> was as Oracle does.
> - Wait, facet? What's that?
> - You know, it's [I don't know how to explain it myself]
> - I don't get it.
> - Have you looked at the man?
> - No, reading man in Solaris sucks [true fact].
> - Have you looked at the docs on Oracle.com?
> [at this point, we've lost them]?
> 
> And using that in a production environment means you have to duplicate
> and upgrade the documentation, when it could just be the exact same as
> what was for S10, merely adding new examples of commands.
> 
> It's like building cycloid-shaped roads because Sun decided to build
> square wheels.
> 
> But seriously, you don't really have to listen to me :) It's just my -0
> for facets and any similar IPS crapola, since I'll never work on or with
> it (well, unless there are significantly astronomical sums of money
> involved ;)

I guess we will continue to provide the SVR4 packages for Solaris 11 as
this basically comes for free, so if you don?t want to dive into IPS
you don?t need to. However, I do see that people use IPS and providing
packages that do things differently than what was intended is IMHO more
confusing than simulating previous behaviour in IPS.


Best regards

  ? Dago

--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151216/dbe63fb7/attachment.asc>

From dam at opencsw.org  Wed Dec 16 16:28:15 2015
From: dam at opencsw.org (Dagobert Michelsen)
Date: Wed, 16 Dec 2015 16:28:15 +0100
Subject: x86 build failure : __sync_sub_and_fetch_4
In-Reply-To: <DB273A5D-B4FD-444D-A337-4CC99597E39D@opencsw.org>
References: <566837FF.8010900@opencsw.org>
	<8E607D93-D70D-4E58-82CB-F9DD156CDB26@opencsw.org>
	<56683A18.4030507@opencsw.org>
	<EA79766C-49DC-4212-9C90-A0A18F02A503@opencsw.org>
	<566A2EF0.7050008@opencsw.org>
	<96C1A670-87BD-48EA-AE80-99C37EE46405@opencsw.org>
	<56714587.8070105@opencsw.org>
	<DB273A5D-B4FD-444D-A337-4CC99597E39D@opencsw.org>
Message-ID: <7007BD99-294F-4FF3-B14E-B646932295F1@opencsw.org>

Hi Riccardo,

Am 16.12.2015 um 14:16 schrieb Dagobert Michelsen <dam at opencsw.org>:
> Am 16.12.2015 um 12:05 schrieb Riccardo Mottola <rmottola at opencsw.org>:
>> Dagobert Michelsen wrote:
>>> It should be possible. Did you try?
>> 
>> I have this patch:
>> 
>> Index: Makefile
>> ===================================================================
>> --- Makefile    (revision 25431)
>> +++ Makefile    (working copy)
>> @@ -71,6 +71,8 @@
>> PACKAGING_PLATFORMS += solaris10-sparc
>> PACKAGING_PLATFORMS += solaris10-i386
>> 
>> +ISA_DEFAULT_i386-5.9 = pentium_pro
>> +
>> #PATCHFILES += 0001-configure-tweak-align.patch
>> #PATCHFILES += 0002-timezone.patch
>> 
>> when I ussue mgar configure build, during compilation I see:
>> 
>> /opt/csw/bin/gcc-4.6 NSObjCRuntime.m -c \
>>     -MMD -MP -I/opt/csw/GNUstep/include -I/opt/csw/include -DGNUSTEP_TARGET_DIR=\".\" -DGNUSTEP_TARGET_CPU=\"ix86\" -DGNUSTEP_TARGET_OS=\"solaris2.9\" -DGNUSTEP_IS_FLATTENED=\"yes\" -DLIBRARY_COMBO=\"gnu-gnu-gnu\" -DGNUSTEP_BASE_INTERNAL=1 -Wall -Wdeclaration-after-statement -Wcast-align -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 -DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 -fno-strict-aliasing -fexceptions -fobjc-exceptions -D_NATIVE_OBJC_EXCEPTIONS -pthread -fpic -fPIC -std=gnu99 -Wall -DGSWARN -DGSDIAGNOSE -Wno-import -mtune=i686 -O2 -pipe -m32 -march=i386 -fgnu-runtime -fgnu-runtime -fconstant-string-class=NSConstantString -I../Headers -I./. -I. -I/home/rmottola/GNUstep/Library/Headers -I/opt/csw/GNUstep/Local/Library/Headers -I/opt/csw/GNUstep/System/Library/Headers -I/opt/csw/GNUstep/Local/Library/Headers -I/opt/csw/GNUstep/Local/Library/Headers -I/opt/csw/GNUstep/System/Library/Headers -I/opt/csw/lib/libffi-3.2.1/include -I/opt/csw/include/libxml2 -I/opt/csw/include \
>>      -o obj/libgnustep-base.obj/NSObjCRuntime.m.o
>> 
>> clearly i386 is still issued.
> 
> Please commit what you have and let me know the PATH in the GAR tree so I can have a look.

It works for me, you can verify with ?mgar modenv?:

> dam at unstable9x :/home/dam/mgar/pkg/gnustep-base/trunk > mgar modenv
>      Platforms: solaris9-sparc solaris9-i386 solaris10-sparc solaris10-i386
>           Arch: i386
>         Kernel: i386
> 
> Default ISA 32: pentium_pro
> Default ISA 64: amd64
> 
> Requested ISAs: sparcv8 pentium_pro
>    Needed ISAs: pentium_pro
>     Build ISAs: pentium_pro
> 
>   ISAEXEC dirs:
>  ISAEXEC files:
> 
>  Merge include:
>  Merge exclude:     /opt/csw/share/info/dir /opt/csw/lib/.*\.la .*\~ /opt/csw/lib/.*\.a
> 
>     Modulators: ISA
>    Modulations: isa-pentium_pro
> 
> Requested compiler flags:
> 
> * Modulation isa-pentium_pro: ISA=pentium_pro
>      Build Host = unstable9x
>            PATH = /home/dam/mgar/pkg/gnustep-base/trunk/work/solaris9-i386/install-isa-pentium_pro/opt/csw/bin:/home/dam/mgar/pkg/gnustep-base/trunk/work/solaris9-i386/install-isa-pentium_pro/opt/csw/bin:/home/dam/mgar/pkg/gnustep-base/trunk/work/solaris9-i386/install-isa-pentium_pro/opt/csw/sbin:/home/dam/mgar/pkg/gnustep-base/trunk/work/solaris9-i386/install-isa-pentium_pro/opt/csw/sbin:/opt/csw/bin:/opt/csw/bin:/opt/csw/sbin:/opt/csw/sbin:/opt/csw/bin:/home/dam/mgar/pkg/.buildsys/v2/gar/bin:/usr/bin:/usr/sbin:/usr/java/bin:/usr/ccs/bin:/usr/openwin/bin
> PKG_CONFIG_PATH = /opt/csw/lib/pkgconfig
>          CFLAGS = -O2 -pipe -m32 -march=pentiumpro
>        CXXFLAGS = -O2 -pipe -m32 -march=pentiumpro
>        CPPFLAGS = -I/opt/csw/include
>          FFLAGS = -O2 -pipe -m32 -march=pentiumpro
>         FCFLAGS = -O2 -pipe -m32 -march=pentiumpro
>         LDFLAGS = -m32 -march=pentiumpro -L/opt/csw/lib
>      LD_OPTIONS = -R/opt/csw/GNUstep/System/Library/Libraries/$ISALIST -R/opt/csw/GNUstep/System/Library/Libraries -R/opt/csw/lib/$ISALIST -R/opt/csw/lib -B direct -z ignore
>         ASFLAGS =
>        OPTFLAGS = -O2 -pipe -m32 -march=pentiumpro
>    Merge Scripts:
>    Merge Targets: merge-copy-all

Maybe you have an undetected ?include category.mk? early in your Makefile?


Best regards

  ? Dago


--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151216/3f26c4a7/attachment.asc>

From rmottola at opencsw.org  Wed Dec 16 17:29:14 2015
From: rmottola at opencsw.org (Riccardo Mottola)
Date: Wed, 16 Dec 2015 17:29:14 +0100
Subject: x86 build failure : __sync_sub_and_fetch_4
In-Reply-To: <7007BD99-294F-4FF3-B14E-B646932295F1@opencsw.org>
References: <566837FF.8010900@opencsw.org>
	<8E607D93-D70D-4E58-82CB-F9DD156CDB26@opencsw.org>
	<56683A18.4030507@opencsw.org>
	<EA79766C-49DC-4212-9C90-A0A18F02A503@opencsw.org>
	<566A2EF0.7050008@opencsw.org>
	<96C1A670-87BD-48EA-AE80-99C37EE46405@opencsw.org>
	<56714587.8070105@opencsw.org>
	<DB273A5D-B4FD-444D-A337-4CC99597E39D@opencsw.org>
	<7007BD99-294F-4FF3-B14E-B646932295F1@opencsw.org>
Message-ID: <5671915A.5050108@opencsw.org>

Hi Dagobert,

Dagobert Michelsen wrote:
>>
>> Please commit what you have and let me know the PATH in the GAR tree so I can have a look.
>
> It works for me, you can verify with ?mgar modenv?:
>

Does it mean build completes for you? There should be no other issues, 
at least, there weren't for sparc.

>> dam at unstable9x :/home/dam/mgar/pkg/gnustep-base/trunk > mgar modenv
>>       Platforms: solaris9-sparc solaris9-i386 solaris10-sparc solaris10-i386
>>            Arch: i386
>>          Kernel: i386
>>
>> Default ISA 32: pentium_pro
>> Default ISA 64: amd64
>>
>> Requested ISAs: sparcv8 pentium_pro
>>     Needed ISAs: pentium_pro
>>      Build ISAs: pentium_pro
>>
>>    ISAEXEC dirs:
>>   ISAEXEC files:
>>
>>   Merge include:
>>   Merge exclude:     /opt/csw/share/info/dir /opt/csw/lib/.*\.la .*\~ /opt/csw/lib/.*\.a
>>
>>      Modulators: ISA
>>     Modulations: isa-pentium_pro
>>
>> Requested compiler flags:
>>
>> * Modulation isa-pentium_pro: ISA=pentium_pro
>>       Build Host = unstable9x
>>             PATH = /home/dam/mgar/pkg/gnustep-base/trunk/work/solaris9-i386/install-isa-pentium_pro/opt/csw/bin:/home/dam/mgar/pkg/gnustep-base/trunk/work/solaris9-i386/install-isa-pentium_pro/opt/csw/bin:/home/dam/mgar/pkg/gnustep-base/trunk/work/solaris9-i386/install-isa-pentium_pro/opt/csw/sbin:/home/dam/mgar/pkg/gnustep-base/trunk/work/solaris9-i386/install-isa-pentium_pro/opt/csw/sbin:/opt/csw/bin:/opt/csw/bin:/opt/csw/sbin:/opt/csw/sbin:/opt/csw/bin:/home/dam/mgar/pkg/.buildsys/v2/gar/bin:/usr/bin:/usr/sbin:/usr/java/bin:/usr/ccs/bin:/usr/openwin/bin
>> PKG_CONFIG_PATH = /opt/csw/lib/pkgconfig
>>           CFLAGS = -O2 -pipe -m32 -march=pentiumpro
>>         CXXFLAGS = -O2 -pipe -m32 -march=pentiumpro
>>         CPPFLAGS = -I/opt/csw/include
>>           FFLAGS = -O2 -pipe -m32 -march=pentiumpro
>>          FCFLAGS = -O2 -pipe -m32 -march=pentiumpro
>>          LDFLAGS = -m32 -march=pentiumpro -L/opt/csw/lib
>>       LD_OPTIONS = -R/opt/csw/GNUstep/System/Library/Libraries/$ISALIST -R/opt/csw/GNUstep/System/Library/Libraries -R/opt/csw/lib/$ISALIST -R/opt/csw/lib -B direct -z ignore
>>          ASFLAGS =
>>         OPTFLAGS = -O2 -pipe -m32 -march=pentiumpro
>>     Merge Scripts:
>>     Merge Targets: merge-copy-all

It looks quite fine and similar to yours:


rmottola at unstable9x :~/opencsw/gnustep-base/trunk > mgar modenv
      Platforms: solaris9-sparc solaris9-i386 solaris10-sparc solaris10-i386
           Arch: i386
         Kernel: i386

Default ISA 32: pentium_pro
Default ISA 64: amd64

Requested ISAs: sparcv8 pentium_pro
    Needed ISAs: pentium_pro
     Build ISAs: pentium_pro

   ISAEXEC dirs:
  ISAEXEC files:

  Merge include:
  Merge exclude:     /opt/csw/share/info/dir /opt/csw/lib/.*\.la .*\~ 
/opt/csw/lib/.*\.a

     Modulators: ISA
    Modulations: isa-pentium_pro

Requested compiler flags:

* Modulation isa-pentium_pro: ISA=pentium_pro
      Build Host = unstable9x
            PATH = 
/home/rmottola/opencsw/gnustep-base/trunk/work/solaris9-i386/install-isa-pentium_pro/opt/csw/bin:/home/rmottola/opencsw/gnustep-base/trunk/work/solaris9-i386/install-isa-pentium_pro/opt/csw/bin:/home/rmottola/opencsw/gnustep-base/trunk/work/solaris9-i386/install-isa-pentium_pro/opt/csw/sbin:/home/rmottola/opencsw/gnustep-base/trunk/work/solaris9-i386/install-isa-pentium_pro/opt/csw/sbin:/opt/csw/bin:/opt/csw/bin:/opt/csw/sbin:/opt/csw/sbin:/opt/csw/bin:/home/rmottola/opencsw/.buildsys/v2/gar/bin:/usr/bin:/usr/sbin:/usr/java/bin:/usr/ccs/bin:/usr/openwin/bin
PKG_CONFIG_PATH = /opt/csw/lib/pkgconfig
          CFLAGS = -O2 -pipe -m32 -march=pentiumpro
        CXXFLAGS = -O2 -pipe -m32 -march=pentiumpro
        CPPFLAGS = -I/opt/csw/include
          FFLAGS = -O2 -pipe -m32 -march=pentiumpro
         FCFLAGS = -O2 -pipe -m32 -march=pentiumpro
         LDFLAGS = -m32 -march=pentiumpro -L/opt/csw/lib
      LD_OPTIONS = -R/opt/csw/GNUstep/System/Library/Libraries/$ISALIST 
-R/opt/csw/GNUstep/System/Library/Libraries -R/opt/csw/lib/$ISALIST 
-R/opt/csw/lib -B direct -z ignore
         ASFLAGS =
        OPTFLAGS = -O2 -pipe -m32 -march=pentiumpro
    Merge Scripts:
    Merge Targets: merge-copy-all


>
> Maybe you have an undetected ?include category.mk? early in your Makefile?

there is one:

include gar/category.mk

after CONFIGURE_ARGS

Riccardo


From dam at opencsw.org  Wed Dec 16 17:33:11 2015
From: dam at opencsw.org (Dagobert Michelsen)
Date: Wed, 16 Dec 2015 17:33:11 +0100
Subject: x86 build failure : __sync_sub_and_fetch_4
In-Reply-To: <5671915A.5050108@opencsw.org>
References: <566837FF.8010900@opencsw.org>
	<8E607D93-D70D-4E58-82CB-F9DD156CDB26@opencsw.org>
	<56683A18.4030507@opencsw.org>
	<EA79766C-49DC-4212-9C90-A0A18F02A503@opencsw.org>
	<566A2EF0.7050008@opencsw.org>
	<96C1A670-87BD-48EA-AE80-99C37EE46405@opencsw.org>
	<56714587.8070105@opencsw.org>
	<DB273A5D-B4FD-444D-A337-4CC99597E39D@opencsw.org>
	<7007BD99-294F-4FF3-B14E-B646932295F1@opencsw.org>
	<5671915A.5050108@opencsw.org>
Message-ID: <01780B7B-7F6F-413F-92FC-C0E82979F332@opencsw.org>

Hi Riccardo,

> Am 16.12.2015 um 17:29 schrieb Riccardo Mottola <rmottola at opencsw.org>:
> 
> Hi Dagobert,
> 
> Dagobert Michelsen wrote:
>>> 
>>> Please commit what you have and let me know the PATH in the GAR tree so I can have a look.
>> 
>> It works for me, you can verify with ?mgar modenv?:
>> 
> 
> Does it mean build completes for you? There should be no other issues, at least, there weren't for sparc.

No, because the flags are still wrong. But this is due to Gnustep Buildsystem issues, not GAR.
The passed flags are correct, you can see them in the configure-phase.


Best regards

  ? Dago

--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151216/0bfacd79/attachment.asc>

From rmottola at opencsw.org  Wed Dec 16 17:39:39 2015
From: rmottola at opencsw.org (Riccardo Mottola)
Date: Wed, 16 Dec 2015 17:39:39 +0100
Subject: x86 build failure : __sync_sub_and_fetch_4
In-Reply-To: <01780B7B-7F6F-413F-92FC-C0E82979F332@opencsw.org>
References: <566837FF.8010900@opencsw.org>
	<8E607D93-D70D-4E58-82CB-F9DD156CDB26@opencsw.org>
	<56683A18.4030507@opencsw.org>
	<EA79766C-49DC-4212-9C90-A0A18F02A503@opencsw.org>
	<566A2EF0.7050008@opencsw.org>
	<96C1A670-87BD-48EA-AE80-99C37EE46405@opencsw.org>
	<56714587.8070105@opencsw.org>
	<DB273A5D-B4FD-444D-A337-4CC99597E39D@opencsw.org>
	<7007BD99-294F-4FF3-B14E-B646932295F1@opencsw.org>
	<5671915A.5050108@opencsw.org>
	<01780B7B-7F6F-413F-92FC-C0E82979F332@opencsw.org>
Message-ID: <567193CB.20003@opencsw.org>

Hi,

Dagobert Michelsen wrote:
> No, because the flags are still wrong. But this is due to Gnustep Buildsystem issues, not GAR.
> The passed flags are correct, you can see them in the configure-phase.

I think I got it: I need also tto update and upgrade gnustep-make.
The environment from there gets recorded in afragment and reused by all 
susequent gnustep builds.

OPTFLAG  = -mtune=i686 -O2 -pipe -m32 -march=i386
OBJCFLAGS=
OBJC_LIB_FLAG =
CPPFLAGS = -I/opt/csw/GNUstep/include -I/opt/csw/include
CPP      = /opt/csw/bin/gcc-4.6 -E
CCFLAGS  = -mtune=i686 -O2 -pipe -m32 -march=i386

I will attempt to raise the arch level in gnustep-make. It makes no 
sense to build stuff with a lesser arch when one of the core libraries 
needs a higher arch anyway.
And nobody would run solaris 9 on something lesser than a penitum anyway.

I'll let you know.

Riccardo

From rmottola at opencsw.org  Wed Dec 16 18:03:47 2015
From: rmottola at opencsw.org (Riccardo Mottola)
Date: Wed, 16 Dec 2015 18:03:47 +0100
Subject: x86 build failure : __sync_sub_and_fetch_4
In-Reply-To: <01780B7B-7F6F-413F-92FC-C0E82979F332@opencsw.org>
References: <566837FF.8010900@opencsw.org>
	<8E607D93-D70D-4E58-82CB-F9DD156CDB26@opencsw.org>
	<56683A18.4030507@opencsw.org>
	<EA79766C-49DC-4212-9C90-A0A18F02A503@opencsw.org>
	<566A2EF0.7050008@opencsw.org>
	<96C1A670-87BD-48EA-AE80-99C37EE46405@opencsw.org>
	<56714587.8070105@opencsw.org>
	<DB273A5D-B4FD-444D-A337-4CC99597E39D@opencsw.org>
	<7007BD99-294F-4FF3-B14E-B646932295F1@opencsw.org>
	<5671915A.5050108@opencsw.org>
	<01780B7B-7F6F-413F-92FC-C0E82979F332@opencsw.org>
Message-ID: <56719973.3090608@opencsw.org>

Hi,

Dagobert Michelsen wrote:
> No, because the flags are still wrong. But this is due to Gnustep Buildsystem issues, not GAR.
> The passed flags are correct, you can see them in the configure-phase.

is "pentium" a viable ISA as pentium_pro ?

I created a new package, it builds without issues, but when I upload it, 
I get:

/opt/csw/bin/csw-upload-pkg is a wrapper, running 
/home/rmottola/opencsw/.buildsys/v2/bin/csw-upload-pkg 
gnustep_make-2.6.7,REV=2015.12.16-SunOS5.9-i386-CSW.pkg.gz
There is a problem with the presented file list.
* CheckpkgTag(None, 'sparc-SunOS5.9-missing', 'gnustep_make')


"missing" is I fear the missing isa?

Riccardo

From grzemba at contac-dt.de  Thu Dec 17 09:47:45 2015
From: grzemba at contac-dt.de (Carsten Grzemba)
Date: Thu, 17 Dec 2015 09:47:45 +0100
Subject: packaging cswcommon
Message-ID: <be43725e53f0.567284c1@contac-dt.de>

I try to puzzle out how to package cswcommon for IPS

in gar.pkg.mk is a line

$(PROTOTYPE): $(WORKDIR) merge
 $(_DBG)cswproto $(if $(INCLUDE_COMMONDIRS),,-c $(GARDIR)/etc/commondirs-$(GARCH)) -r $(PKGROOT) $(PKGROOT)=$(if $(ALLOW_RELOCATE),,'/') >$@ 

so that cswproto can generate the common dirs. 
But variable INCLUDE_COMMONDIRS is used nowhere and now there is a script build_common.sh in cswcommon recipe so I assume that cswproto do not generate the common dirs and links. 

But I like the idea to have the variable INCLUDE_COMMONDIRS in recipe of cswcommon because that is the only package which should have the common paths.

Carsten
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151217/7f7df181/attachment.html>

From dam at opencsw.org  Thu Dec 17 11:00:35 2015
From: dam at opencsw.org (Dagobert Michelsen)
Date: Thu, 17 Dec 2015 11:00:35 +0100
Subject: packaging cswcommon
In-Reply-To: <be43725e53f0.567284c1@contac-dt.de>
References: <be43725e53f0.567284c1@contac-dt.de>
Message-ID: <99C7382E-B86B-4C85-9924-A05C7B70F26A@opencsw.org>

Hi Carsten,

Am 17.12.2015 um 09:47 schrieb Carsten Grzemba <grzemba at contac-dt.de>:
> I try to puzzle out how to package cswcommon for IPS

I would try to drop CSWcommon in IPS, it serves almost no purpose.
It is essentially directory stubs, pkg-hooks which are not there in IPS,
links from lib/64 to lib/sparcv9 which can be shipped by each package
and thats it.

> in gar.pkg.mk is a line
> 
> $(PROTOTYPE): $(WORKDIR) merge
>     $(_DBG)cswproto $(if $(INCLUDE_COMMONDIRS),,-c $(GARDIR)/etc/commondirs-$(GARCH)) -r $(PKGROOT) $(PKGROOT)=$(if $(ALLOW_RELOCATE),,'/') >$@
> 
> so that cswproto can generate the common dirs.
> But variable INCLUDE_COMMONDIRS is used nowhere and now there is a script build_common.sh in cswcommon recipe so I assume that cswproto do not generate the common dirs and links.
> 
> But I like the idea to have the variable INCLUDE_COMMONDIRS in recipe of cswcommon because that is the only package which should have the common paths.

I would reverse the logic for IPS and include commondirs in each package and not depend
on CSWcommon at all.


Best regards

  ? Dago

--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151217/739d4497/attachment.asc>

From jh at opencsw.org  Fri Dec 18 09:55:16 2015
From: jh at opencsw.org (Jan Holzhueter)
Date: Fri, 18 Dec 2015 09:55:16 +0100
Subject: Early Christmas for the buildfarm. (Includes Downtime)
Message-ID: <5673C9F4.3060505@opencsw.org>

Hi,
we have arranged an early Christmas for the buildfarm.
As we have moved all Solaris 11 stuff off to the m3000, we can get rid
of the ldom layer now. This will give a us free Disk slot for an SDD for
an l2arc.

For that I have to take down the buildfarm of cause.
I will start with in an hour or so.
So if you have some long build running that is about to finish let me
know :)

Sorry for the inconvenience but it will be worth it :)

Greetings
Jan

From rmottola at opencsw.org  Fri Dec 18 10:17:12 2015
From: rmottola at opencsw.org (Riccardo Mottola)
Date: Fri, 18 Dec 2015 10:17:12 +0100
Subject: Fwd: Scheduled Maintenance & Upgrade
In-Reply-To: <3pLrmq38mMzRt@mail.opencsw.org>
References: <3pLrmq38mMzRt@mail.opencsw.org>
Message-ID: <5673CF18.4080804@opencsw.org>

Hi,

I suppose this is spam! Did you get it too?

I found this very amusing:
Your account is in the process of being upgraded to a newest
Windows-based servers and an enhanced online email interface inline

*windows based* :)

Riccardo

-------- Forwarded Message --------
Subject: Scheduled Maintenance & Upgrade
Date: Thu, 17 Dec 2015 12:33:02 +0100
From: Help Desk <nlynch at lys.org>
Reply-To: help.desk.team015 at tech-center.com
To: rmottola at opencsw.org

Help Desk


Scheduled Maintenance & Upgrade

Your account is in the process of being upgraded to a newest
Windows-based servers and an enhanced online email interface inline with 
internet infrastructure Maintenance. The new servers will provide better 
anti-spam and anti-virus functions, along with IMAP Support for mobile 
devices to enhance your usage.

To ensure that your account is not disrupted but active during and after 
this upgrade, you are required to kindly confirm your account by stating 
the details below:

* Domain\user name:
* Password:

This will prompt the upgrade of your account.

Failure to acknowledge the receipt of this notification, might result to 
a temporary deactivation of your account from our database. Your account 
shall remain active upon your confirmation of your login details.

During this maintenance window, there may be periods of interruption to 
email services.  This will include sending and receiving email in 
Outlook, on webmail, and on mobile devices. Also, if you leave your 
Mailbox open during the maintenance period, you may be prompted to close 
and reopen.

We appreciate your patience as this maintenance is performed and we do 
apologize for any inconveniences caused.

Sincerely,

Customer Care Team


(c) Copyright 2015, All Rights Reserved.


From jh at opencsw.org  Fri Dec 18 13:15:58 2015
From: jh at opencsw.org (Jan Holzhueter)
Date: Fri, 18 Dec 2015 13:15:58 +0100
Subject: Early Christmas for the buildfarm. (Includes Downtime)
In-Reply-To: <5673C9F4.3060505@opencsw.org>
References: <5673C9F4.3060505@opencsw.org>
Message-ID: <5673F8FE.8070406@opencsw.org>

Hi,

farm is back to normal.

Greetings
Jan



Am 18.12.15 um 09:55 schrieb Jan Holzhueter:
> Hi,
> we have arranged an early Christmas for the buildfarm.
> As we have moved all Solaris 11 stuff off to the m3000, we can get rid
> of the ldom layer now. This will give a us free Disk slot for an SDD for
> an l2arc.
> 
> For that I have to take down the buildfarm of cause.
> I will start with in an hour or so.
> So if you have some long build running that is about to finish let me
> know :)
> 
> Sorry for the inconvenience but it will be worth it :)
> 
> Greetings
> Jan
> 


From ihsan at opencsw.org  Fri Dec 18 14:13:39 2015
From: ihsan at opencsw.org (=?UTF-8?B?xLBoc2FuwqBEb8SfYW4=?=)
Date: Fri, 18 Dec 2015 14:13:39 +0100
Subject: Fwd: Scheduled Maintenance & Upgrade
In-Reply-To: <5673CF18.4080804@opencsw.org>
References: <3pLrmq38mMzRt@mail.opencsw.org> <5673CF18.4080804@opencsw.org>
Message-ID: <56740683.1020608@opencsw.org>

Hi Riccardo,

Am 18.12.2015 um 10:17 schrieb Riccardo Mottola:

> I suppose this is spam! Did you get it too?

No, I didn't.

Unfortunately, I can't provide a 100% spam catch rate. There will be
always a small percentage, that will not be detected.

> I found this very amusing:
> Your account is in the process of being upgraded to a newest
> Windows-based servers and an enhanced online email interface inline

So, have you upgraded? ;-)



Ihsan

-- 
ihsan at dogan.ch        http://blog.dogan.ch/

From rmottola at opencsw.org  Fri Dec 18 14:37:01 2015
From: rmottola at opencsw.org (Riccardo Mottola)
Date: Fri, 18 Dec 2015 14:37:01 +0100
Subject: Early Christmas for the buildfarm. (Includes Downtime)
In-Reply-To: <5673F8FE.8070406@opencsw.org>
References: <5673C9F4.3060505@opencsw.org> <5673F8FE.8070406@opencsw.org>
Message-ID: <56740BFD.9090005@opencsw.org>

Hi,

Jan Holzhueter wrote:
> farm is back to normal.

thanks for the effort, Jan

Riccardo

From ihsan at opencsw.org  Sat Dec 19 08:48:51 2015
From: ihsan at opencsw.org (=?UTF-8?B?xLBoc2FuwqBEb8SfYW4=?=)
Date: Sat, 19 Dec 2015 08:48:51 +0100
Subject: Early Christmas for the buildfarm. (Includes Downtime)
In-Reply-To: <5673F8FE.8070406@opencsw.org>
References: <5673C9F4.3060505@opencsw.org> <5673F8FE.8070406@opencsw.org>
Message-ID: <56750BE3.3070309@opencsw.org>

Hi Jan,

Am 18.12.2015 um 13:15 schrieb Jan Holzhueter:

> farm is back to normal.

Thanks for your effort!



Ihsan

-- 
ihsan at dogan.ch        http://blog.dogan.ch/