From dam at opencsw.org  Wed Apr  2 15:17:19 2014
From: dam at opencsw.org (Dagobert Michelsen)
Date: Wed, 2 Apr 2014 15:17:19 +0200
Subject: Our PHP 5.x package is getting old
In-Reply-To: <53393866.90704@opencsw.org>
References: <CALtRa-6fge1x+tMc_tmLA4pYRbnZ_L-w9X-bLMbFo+NO44ESWw@mail.gmail.com>	<5333D4C9.6040509@opencsw.org>
	<C2CE62D6-74C6-44E9-91BB-BE5773E7A47F@opencsw.org>
	<53393866.90704@opencsw.org>
Message-ID: <09824F1D-2035-4E0B-B522-B81CFF214B06@opencsw.org>

Hi James,

Am 31.03.2014 um 11:41 schrieb James Lee <james at opencsw.org>:
> On 27/03/2014 08:59, Dagobert Michelsen wrote:
>> 
>>> dam at unstable10s [unstable10s]:/home/dam/mgar/pkg/php5/branches/php-5.5.x/work/solaris10-sparc/build-isa-sparcv8plus-sapi-cgi/php-5.5.10 > pstack core
>>> core 'core' of 16636:   /home/dam/mgar/pkg/php5/branches/php-5.5.x/work/solaris10-sparc/build-
>>>  000a6500 compare_opcodes (c1d7ad, 0, ffbfe5b8, ffbfd3d8, c1d789, c1d7ad) + 1178
>>>  000a6944 auto_possessify (c1d767, 0, ffbfe5b8, 64, ffbfd3d8, 661eb4) + 284
>>>  000b0114 php_pcre_compile2 (b9, 0, 20000, 0, c1d6c0, 96372c) + d90
>>>  000d4138 pcre_get_compiled_regex_cache (a5e4ac, 2f, 2f, 2f, 0, 961064) + 444
>>>  000d4680 php_do_pcre_match (3, dde418, ffbfe770, 961064, ffbfe774, 0) + 7c
>>>  005acaa0 zend_do_fcall_common_helper_SPEC (9ee560, 100, 100, 961064, d646cc, 9e4798) + 320
>>>  005ac448 execute_ex (9ee560, 9e45f0, 1, 961064, 8358c, 0) + 3c
>>>  00533ce4 zend_execute_scripts (8, 0, ffbff3c8, 1, 9e4714, ffbfe8ac) + 678
>>>  0043eb94 php_execute_script (9e4f30, ffbff3c8, 9e4f30, 961064, 1, 83c00) + 32c
>>>  005ff608 do_cli   (961064, 8, 0, 83c00, 961064, 83c00) + d3c
>>>  00600684 main     (10, ffbff674, ffbff6b8, 963000, 96be44, 96be44) + 660
>>>  0004d9c0 _start   (0, 0, 0, 0, 0, 0) + 108
>> Everything is committed, if you have a great idea let me know.
> 
> PHP build adds -xmemalign=8s to the compile options.  The 's' says throws a bus error if a memory misalignment is detected. The 'i' xmemalign option say to me it will work but might be slower.
> 
> The misalignment is in compare_opcodes which is part of prce 8.34 and the misalignment is right after the comment "Compare 4 bytes to improve speed".  What it's doing is:
> 
> function(char *cp)
> {
>    int *ip;
>    ip = (int *) cp;
>    ... *ip ...;  // handle in 4 byte chucks
> 
> which is not 8 byte aligned when "cp % 8 !=  0". On the Sparc and Intel chips I've tested it doesn't seem to make a difference but it must depends on the chip design and perhaps there are some where the speed difference is greater.
> 
> Workaround: remove or change to 'i' xmemalign from PHP's configure:
>  sparc*)
>    if test "$SUNCC" = "yes"; then
>      CFLAGS="$CFLAGS -xmemalign=8s"
>    fi
> 
> 
> Fix:
> http://bugs.exim.org/show_bug.cgi?id=1427

Thanks a lot for the detailed analysis! The install now passes after patching configure,
I can proceed now to the packaging issues.


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: smime.p7s
Type: application/pkcs7-signature
Size: 2418 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140402/25f6332a/attachment.p7s>

From dam at opencsw.org  Thu Apr  3 10:24:22 2014
From: dam at opencsw.org (Dagobert Michelsen)
Date: Thu, 3 Apr 2014 10:24:22 +0200
Subject: The new package database and the rest interface
Message-ID: <0BFB1F3E-5740-4BAC-BD1F-7C118AAE3464@opencsw.org>

Hi Maciej,

I am fiddling with the autobuilds again and have two questions:

1. There used to be package listings by error tag at
      http://buildfarm.opencsw.org/pkgdb/error-tags/
   All these are empty now, probably because of the new database. Can the data
   be provided also with the new database?

2. I need to find out the repository URL for each package in a catalog. In the past I used
     http://buildfarm.opencsw.org/pkgdb/rest/catalogs/unstable/sparc/SunOS5.10/
   but that doesn?t contain ?repository_url? any more, even with quick=false. Is there another
   URL I can use?


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: smime.p7s
Type: application/pkcs7-signature
Size: 2418 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140403/fa7c2251/attachment.p7s>

From maciej at opencsw.org  Thu Apr  3 10:41:09 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Thu, 3 Apr 2014 09:41:09 +0100
Subject: Solaris 9 support to be removed from GCC upstream
Message-ID: <CALtRa-7zzkOwbn90tTxstnzWGFstf_d-J8mRd7HqhNOpx6BTpQ@mail.gmail.com>

I tried building GCC from Subversion on Solaris 9 last night, here's what I saw:

checking whether ldgetname is declared... no
checking whether times is declared... yes
checking whether sigaltstack is declared... yes
checking whether madvise is declared... yes
checking for struct tms... yes
checking for clock_t... yes
checking for F_SETLKW... yes
checking if mkdir takes one argument... no
*** Configuration sparc-sun-solaris2.9 is obsolete.
*** Specify --enable-obsolete to build it anyway.
*** Support will be REMOVED in the next major release of GCC,
*** unless a maintainer comes forward.
gmake[2]: *** [configure-stage1-gcc] Error 1
gmake[2]: Leaving directory `/home/maciej/src/gcc-objdir-svn-sparc-5.9'
gmake[1]: *** [stage1-bubble] Error 2
gmake[1]: Leaving directory `/home/maciej/src/gcc-objdir-svn-sparc-5.9'
gmake: *** [all] Error 2
maciej at unstable9s :~/src >

We haven't built GCC for Solaris 9 in a long while, the version we've
got in the 5.9 repo is 4.6. I was looking if we can refresh it, and I
wanted to report potential compilation errors, but I guess I won't.

Maciej

From maciej at opencsw.org  Sun Apr  6 14:36:28 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sun, 6 Apr 2014 13:36:28 +0100
Subject: Stale packages report is available
Message-ID: <CALtRa-4Zmx_2hEb3fzpsaUEbX0-FgTDSGia0oecp3TBRkEfJSA@mail.gmail.com>

Hello maintainers,

During yesterday's hacking session I wrote a quick and dirty report of
stale packages.

http://buildfarm.opencsw.org/obsolete-pkgs/stale-packages.html

Packages are grouped by maintainer, so you can look up your user name
and see of there are any stale packages that you maintain (or made the
mistake of uploading it once ;-) ).

This report is refreshed a few times a day.

On the report there is also information about inactive maintainers and
their stale packages. If you notice anything that you care about, feel
free to grab that package, rebuild and upload.

Maciej

From pfelecan at opencsw.org  Sun Apr  6 19:13:49 2014
From: pfelecan at opencsw.org (Peter FELECAN)
Date: Sun, 06 Apr 2014 19:13:49 +0200
Subject: Stale packages report is available
In-Reply-To: <CALtRa-4Zmx_2hEb3fzpsaUEbX0-FgTDSGia0oecp3TBRkEfJSA@mail.gmail.com>
	("Maciej (Matchek) =?utf-8?Q?Blizi=C5=84ski=22's?= message of "Sun,
	6 Apr 2014 13:36:28 +0100")
References: <CALtRa-4Zmx_2hEb3fzpsaUEbX0-FgTDSGia0oecp3TBRkEfJSA@mail.gmail.com>
Message-ID: <x6a9bycrea.fsf@opencsw.org>

"Maciej (Matchek) Blizi?ski" <maciej at opencsw.org> writes:

> Hello maintainers,
>
> During yesterday's hacking session I wrote a quick and dirty report of
> stale packages.
>
> http://buildfarm.opencsw.org/obsolete-pkgs/stale-packages.html

Nice. Thus, I see that I have a package which get old and besides it's
not needed anymore as another one provides its features. Can you remind
me how to remove a package from the catalog or point me toward a
documentation reference?

TIA
-- 
Peter

From maciej at opencsw.org  Sun Apr  6 19:24:25 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sun, 6 Apr 2014 18:24:25 +0100
Subject: Stale packages report is available
In-Reply-To: <x6a9bycrea.fsf@opencsw.org>
References: <CALtRa-4Zmx_2hEb3fzpsaUEbX0-FgTDSGia0oecp3TBRkEfJSA@mail.gmail.com>
	<x6a9bycrea.fsf@opencsw.org>
Message-ID: <CALtRa-5yH6udPQZA2xYcAX40r36VNd2z2wGVB7C3hGK+S-=tsg@mail.gmail.com>

2014-04-06 18:13 GMT+01:00 Peter FELECAN <pfelecan at opencsw.org>:
> "Maciej (Matchek) Blizi?ski" <maciej at opencsw.org> writes:
>
>> Hello maintainers,
>>
>> During yesterday's hacking session I wrote a quick and dirty report of
>> stale packages.
>>
>> http://buildfarm.opencsw.org/obsolete-pkgs/stale-packages.html
>
> Nice. Thus, I see that I have a package which get old and besides it's
> not needed anymore as another one provides its features. Can you remind
> me how to remove a package from the catalog or point me toward a
> documentation reference?

There are some examples at the bottom of the report, the general usage
is as follows:

# setup
cd /path/to/gar/v2
export PYTHONPATH=$PWD
# work
./lib/python/safe_remove_package.py \
--os-releases=SunOS5.9,SunOS5.10,SunOS5.11 -c <catalogname>

The script will only remove a package when it has no reverse dependencies.

Maciej

From maciej at opencsw.org  Mon Apr  7 13:47:37 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Mon, 7 Apr 2014 12:47:37 +0100
Subject: Migrating documentation to the manual
Message-ID: <CALtRa-6CztUZS_uROLt=KFXo18wPPhpb+AbFtL=ai40LXUrnjA@mail.gmail.com>

We have this page: http://www.opencsw.org/use-it/

It's linked off the big "Documentation" link on the green bar, and
it's not very well maintained.

We have our manual at http://www.opencsw.org/manual/ which looks like
a better place for this information. The code is here:

http://sourceforge.net/p/gar/code/HEAD/tree/csw/mgar/pkg/opencsw-manual/trunk/

Would anyone like to volunteer to move the content from the old
"use-it" page to the manual?

Maciej

From aironskin at opencsw.org  Mon Apr  7 16:04:56 2014
From: aironskin at opencsw.org (Stefan Schnyder)
Date: Mon, 07 Apr 2014 16:04:56 +0200
Subject: Migrating documentation to the manual
In-Reply-To: <CALtRa-6CztUZS_uROLt=KFXo18wPPhpb+AbFtL=ai40LXUrnjA@mail.gmail.com>
References: <CALtRa-6CztUZS_uROLt=KFXo18wPPhpb+AbFtL=ai40LXUrnjA@mail.gmail.com>
Message-ID: <5342B088.7070407@opencsw.org>

Hey Maciej

I'd be willing to take that up.

However, I'd like to present some suggestions on how to consolidate the 
- still relevant - information that is on the 
website/manual/wiki/community/trac until the end of the week. And if 
people support a new setup, I'd like to put more effort into that 
instead of the current one.

Cheers,
Stefan

On 04/07/2014 01:47 PM, Maciej (Matchek) Blizi?ski wrote:
> We have this page: http://www.opencsw.org/use-it/
>
> It's linked off the big "Documentation" link on the green bar, and
> it's not very well maintained.
>
> We have our manual at http://www.opencsw.org/manual/ which looks like
> a better place for this information. The code is here:
>
> http://sourceforge.net/p/gar/code/HEAD/tree/csw/mgar/pkg/opencsw-manual/trunk/
>
> Would anyone like to volunteer to move the content from the old
> "use-it" page to the manual?
>
> Maciej
>


From maciej at opencsw.org  Mon Apr  7 23:22:46 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Mon, 7 Apr 2014 22:22:46 +0100
Subject: Migrating documentation to the manual
In-Reply-To: <5342B088.7070407@opencsw.org>
References: <CALtRa-6CztUZS_uROLt=KFXo18wPPhpb+AbFtL=ai40LXUrnjA@mail.gmail.com>
	<5342B088.7070407@opencsw.org>
Message-ID: <CALtRa-5y9=WngpCiWq_ZRPjhH426t1PHs-7YHgLXBNs1Mt6nvw@mail.gmail.com>

2014-04-07 15:04 GMT+01:00 Stefan Schnyder <aironskin at opencsw.org>:
> However, I'd like to present some suggestions on how to consolidate the -
> still relevant - information that is on the
> website/manual/wiki/community/trac until the end of the week. And if people
> support a new setup, I'd like to put more effort into that instead of the
> current one.

Yes, consolidation with a plan is definitely something we need and
want. It has been on my mind for a few years:

http://lists.opencsw.org/pipermail/maintainers/2009-March/007260.html
http://lists.opencsw.org/pipermail/maintainers/2010-November/013224.html
http://lists.opencsw.org/pipermail/maintainers/2013-April/017968.html
http://lists.opencsw.org/pipermail/maintainers/2013-September/018607.html

Looking forward to your plan! (But ad-hoc changes in the right
direction are welcome too!)

Maciej

From grzemba at contac-dt.de  Tue Apr  8 10:25:42 2014
From: grzemba at contac-dt.de (Carsten Grzemba)
Date: Tue, 08 Apr 2014 10:25:42 +0200
Subject: links in CSWcommon
In-Reply-To: <bbaf503f318e.5343b23d@contac-dt.de>
References: <bbaf4f0e1a94.5343ae6a@contac-dt.de>
	<bbaf6aed2d93.5343aea6@contac-dt.de>
	<bbaf02c55950.5343aee2@contac-dt.de>
	<bbaf0b092923.5343af5d@contac-dt.de>
	<bbaf232037ba.5343af99@contac-dt.de>
	<bbaf59b9762b.5343afd8@contac-dt.de>
	<bbaf66377f0.5343b014@contac-dt.de>
	<bbaf26a51dfd.5343b051@contac-dt.de>
	<bbaf3ce7ac5.5343b08d@contac-dt.de>
	<bbaf33d652f1.5343b108@contac-dt.de>
	<bbaf6ebb2c60.5343b147@contac-dt.de>
	<bbaf13bc4e5d.5343b1c2@contac-dt.de>
	<bbaf0a6b67d1.5343b201@contac-dt.de>
	<bbaf503f318e.5343b23d@contac-dt.de>
Message-ID: <bbaf0b976fc8.5343cea6@contac-dt.de>

after some fiddle around why a non autotools package will find 32bit-libs and 64bit-libs not I saw that CSWcommon has a link
/opt/csw/lib/sparcv8 -> .
but it has no link
/opt/csw/lib/sparcv9/sparcv9 -> .

Should we have this link or have we solve this with an explicit listed search path for the base: '-R/opt/csw/lib/64/$ISALIST -R/opt/csw/lib/64'

Btw.: we have a recipe in gar for CSWcommon but it is not listed as 'package source' on http://www.opencsw.org/packages/CSWcommon/ (because it is called cswcommon?).

Carsten
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140408/19c86db0/attachment.html>

From grzemba at contac-dt.de  Tue Apr  8 10:30:14 2014
From: grzemba at contac-dt.de (Carsten Grzemba)
Date: Tue, 08 Apr 2014 10:30:14 +0200
Subject: links in CSWcommon
In-Reply-To: <bbaf77006168.5343b391@contac-dt.de>
References: <bbaf4f0e1a94.5343ae6a@contac-dt.de>
	<bbaf6aed2d93.5343aea6@contac-dt.de>
	<bbaf02c55950.5343aee2@contac-dt.de>
	<bbaf0b092923.5343af5d@contac-dt.de>
	<bbaf232037ba.5343af99@contac-dt.de>
	<bbaf59b9762b.5343afd8@contac-dt.de>
	<bbaf66377f0.5343b014@contac-dt.de>
	<bbaf26a51dfd.5343b051@contac-dt.de>
	<bbaf3ce7ac5.5343b08d@contac-dt.de>
	<bbaf33d652f1.5343b108@contac-dt.de>
	<bbaf6ebb2c60.5343b147@contac-dt.de>
	<bbaf13bc4e5d.5343b1c2@contac-dt.de>
	<bbaf0a6b67d1.5343b201@contac-dt.de>
	<bbaf503f318e.5343b23d@contac-dt.de>
	<bbaf0b976fc8.5343cea6@contac-dt.de>
	<bbaf56d64459.5343b319@contac-dt.de>
	<bbaf77006168.5343b391@contac-dt.de>
Message-ID: <bbaf0029527c.5343cfb6@contac-dt.de>



Am 08.04.14 schrieb Carsten Grzemba  <grzemba at contac-dt.de>:
> after some fiddle around why a non autotools package will find 32bit-libs and 64bit-libs not I saw that CSWcommon has a link
> /opt/csw/lib/sparcv8 -> .
> but it has no link
> /opt/csw/lib/sparcv9/sparcv9 -> .
> 
> Should we have this link or have we solve this with an explicit listed search path for the base: '-R/opt/csw/lib/64/$ISALIST -R/opt/csw/lib/64'
> 
> Btw.: we have a recipe in gar for CSWcommon but it is not listed as 'package source' on http://www.opencsw.org/packages/CSWcommon/ (because it is called cswcommon?).
> 
> Carsten 
> 
Interesting: binutils creates an empty dir /opt/csw/lib/sparcv9/sparcv9

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

From Joerg.Schilling at fokus.fraunhofer.de  Tue Apr  8 12:38:13 2014
From: Joerg.Schilling at fokus.fraunhofer.de (Joerg Schilling)
Date: Tue, 8 Apr 2014 12:38:13 +0200
Subject: links in CSWcommon
In-Reply-To: <bbaf0b976fc8.5343cea6@contac-dt.de>
References: <bbaf4f0e1a94.5343ae6a@contac-dt.de>
	<bbaf6aed2d93.5343aea6@contac-dt.de>
	<bbaf02c55950.5343aee2@contac-dt.de>
	<bbaf0b092923.5343af5d@contac-dt.de>
	<bbaf232037ba.5343af99@contac-dt.de>
	<bbaf59b9762b.5343afd8@contac-dt.de>
	<bbaf66377f0.5343b014@contac-dt.de>
	<bbaf26a51dfd.5343b051@contac-dt.de>
	<bbaf3ce7ac5.5343b08d@contac-dt.de>
	<bbaf33d652f1.5343b108@contac-dt.de>
	<bbaf6ebb2c60.5343b147@contac-dt.de>
	<bbaf13bc4e5d.5343b1c2@contac-dt.de>
	<bbaf0a6b67d1.5343b201@contac-dt.de>
	<bbaf503f318e.5343b23d@contac-dt.de>
	<bbaf0b976fc8.5343cea6@contac-dt.de>
Message-ID: <5343d195.1aMC1HUl2ffH6uUT%Joerg.Schilling@fokus.fraunhofer.de>

Carsten Grzemba <grzemba at contac-dt.de> wrote:

> after some fiddle around why a non autotools package will find 32bit-libs and 64bit-libs not I saw that CSWcommon has a link
> /opt/csw/lib/sparcv8 -> .
> but it has no link
> /opt/csw/lib/sparcv9/sparcv9 -> .
>
> Should we have this link or have we solve this with an explicit listed search path for the base: '-R/opt/csw/lib/64/$ISALIST -R/opt/csw/lib/64'

The runpath option -R/opt/csw/lib/64/$ISALIST is wrong.

The link /opt/csw/lib/sparcv8 -> . esists because the 32 bit libs are not 
located in a directory parallel to /opt/csw/lib/64/ (which would be 
/opt/csw/lib/32/) but in /opt/csw/lib/.

Correct would be -R/opt/csw/lib/$ISALIST

J?rg

-- 
 EMail:joerg at schily.isdn.cs.tu-berlin.de (home) J?rg Schilling D-13353 Berlin
       js at cs.tu-berlin.de                (uni)  
       joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily

From dam at opencsw.org  Wed Apr  9 04:59:27 2014
From: dam at opencsw.org (Dagobert Michelsen)
Date: Tue, 8 Apr 2014 19:59:27 -0700
Subject: Migrating documentation to the manual
In-Reply-To: <CALtRa-5y9=WngpCiWq_ZRPjhH426t1PHs-7YHgLXBNs1Mt6nvw@mail.gmail.com>
References: <CALtRa-6CztUZS_uROLt=KFXo18wPPhpb+AbFtL=ai40LXUrnjA@mail.gmail.com>
	<5342B088.7070407@opencsw.org>
	<CALtRa-5y9=WngpCiWq_ZRPjhH426t1PHs-7YHgLXBNs1Mt6nvw@mail.gmail.com>
Message-ID: <5E3A6DEA-1C7D-43AD-953A-91F38524516F@opencsw.org>

Hi Stefan,

Am 07.04.2014 um 14:22 schrieb Maciej (Matchek) Blizi?ski <maciej at opencsw.org>:
> 2014-04-07 15:04 GMT+01:00 Stefan Schnyder <aironskin at opencsw.org>:
>> However, I'd like to present some suggestions on how to consolidate the -
>> still relevant - information that is on the
>> website/manual/wiki/community/trac until the end of the week. And if people
>> support a new setup, I'd like to put more effort into that instead of the
>> current one.
> 
> Yes, consolidation with a plan is definitely something we need and
> want. It has been on my mind for a few years:
> 
> http://lists.opencsw.org/pipermail/maintainers/2009-March/007260.html
> http://lists.opencsw.org/pipermail/maintainers/2010-November/013224.html
> http://lists.opencsw.org/pipermail/maintainers/2013-April/017968.html
> http://lists.opencsw.org/pipermail/maintainers/2013-September/018607.html
> 
> Looking forward to your plan! (But ad-hoc changes in the right
> direction are welcome too!)

Stefan, please don?t get demotivated by the long period this task has been going!
If you need anything please 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: smime.p7s
Type: application/pkcs7-signature
Size: 2418 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140408/7ae3a3dd/attachment.p7s>

From dam at opencsw.org  Wed Apr  9 05:11:26 2014
From: dam at opencsw.org (Dagobert Michelsen)
Date: Tue, 8 Apr 2014 20:11:26 -0700
Subject: links in CSWcommon
In-Reply-To: <5343d195.1aMC1HUl2ffH6uUT%Joerg.Schilling@fokus.fraunhofer.de>
References: <bbaf4f0e1a94.5343ae6a@contac-dt.de>
	<bbaf6aed2d93.5343aea6@contac-dt.de>
	<bbaf02c55950.5343aee2@contac-dt.de>
	<bbaf0b092923.5343af5d@contac-dt.de>
	<bbaf232037ba.5343af99@contac-dt.de>
	<bbaf59b9762b.5343afd8@contac-dt.de>
	<bbaf66377f0.5343b014@contac-dt.de>
	<bbaf26a51dfd.5343b051@contac-dt.de>
	<bbaf3ce7ac5.5343b08d@contac-dt.de>
	<bbaf33d652f1.5343b108@contac-dt.de>
	<bbaf6ebb2c60.5343b147@contac-dt.de>
	<bbaf13bc4e5d.5343b1c2@contac-dt.de>
	<bbaf0a6b67d1.5343b201@contac-dt.de>
	<bbaf503f318e.5343b23d@contac-dt.de>
	<bbaf0b976fc8.5343cea6@contac-dt.de>
	<5343d195.1aMC1HUl2ffH6uUT%Joerg.Schilling@fokus.fraunhofer.de>
Message-ID: <DBB9F944-ADFA-4A2E-8020-886CAD98D11A@opencsw.org>

Hi Carsten,

Am 08.04.2014 um 03:38 schrieb Joerg Schilling <Joerg.Schilling at fokus.fraunhofer.de>:
> Carsten Grzemba <grzemba at contac-dt.de> wrote:
>> after some fiddle around why a non autotools package will find 32bit-libs and 64bit-libs not I saw that CSWcommon has a link
>> /opt/csw/lib/sparcv8 -> .
>> but it has no link
>> /opt/csw/lib/sparcv9/sparcv9 -> .

That link would have been wrong.

>> Should we have this link or have we solve this with an explicit listed search path for the base: '-R/opt/csw/lib/64/$ISALIST -R/opt/csw/lib/64'
> 
> The runpath option -R/opt/csw/lib/64/$ISALIST is wrong.
> 
> The link /opt/csw/lib/sparcv8 -> . esists because the 32 bit libs are not 
> located in a directory parallel to /opt/csw/lib/64/ (which would be 
> /opt/csw/lib/32/) but in /opt/csw/lib/.
> 
> Correct would be -R/opt/csw/lib/$ISALIST

Exactly, the build system of the software you are using seems have its own ideas
on path construction, you probable need to patch/reconfigure it.


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: smime.p7s
Type: application/pkcs7-signature
Size: 2418 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140408/592aa147/attachment.p7s>

From dam at opencsw.org  Wed Apr  9 06:49:06 2014
From: dam at opencsw.org (Dagobert Michelsen)
Date: Tue, 8 Apr 2014 21:49:06 -0700
Subject: Propagate OpenSSL to all releases
Message-ID: <8E339FBD-E4CA-4290-B933-33875E3D5C69@opencsw.org>

Hi Maciej,

can you please propagate the fixed OpenSSL package to all named releases?
I have made an announcement on the website, please update as you see fit.


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: smime.p7s
Type: application/pkcs7-signature
Size: 2418 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140408/ea557d38/attachment.p7s>

From aironskin at opencsw.org  Wed Apr  9 09:22:42 2014
From: aironskin at opencsw.org (Stefan Schnyder)
Date: Wed, 09 Apr 2014 09:22:42 +0200
Subject: Migrating documentation to the manual
In-Reply-To: <5E3A6DEA-1C7D-43AD-953A-91F38524516F@opencsw.org>
References: <CALtRa-6CztUZS_uROLt=KFXo18wPPhpb+AbFtL=ai40LXUrnjA@mail.gmail.com>	<5342B088.7070407@opencsw.org>	<CALtRa-5y9=WngpCiWq_ZRPjhH426t1PHs-7YHgLXBNs1Mt6nvw@mail.gmail.com>
	<5E3A6DEA-1C7D-43AD-953A-91F38524516F@opencsw.org>
Message-ID: <5344F542.4060808@opencsw.org>

Not at all. I like this kind of work. :)
I'd be great if you could boot up that VM you were talking about. I'd 
prefer to test stuff away from the production environment :)

Cheers,
Stefan

On 04/09/2014 04:59 AM, Dagobert Michelsen wrote:
> Hi Stefan,
>
> Am 07.04.2014 um 14:22 schrieb Maciej (Matchek) Blizi?ski <maciej at opencsw.org>:
>> 2014-04-07 15:04 GMT+01:00 Stefan Schnyder <aironskin at opencsw.org>:
>>> However, I'd like to present some suggestions on how to consolidate the -
>>> still relevant - information that is on the
>>> website/manual/wiki/community/trac until the end of the week. And if people
>>> support a new setup, I'd like to put more effort into that instead of the
>>> current one.
>> Yes, consolidation with a plan is definitely something we need and
>> want. It has been on my mind for a few years:
>>
>> http://lists.opencsw.org/pipermail/maintainers/2009-March/007260.html
>> http://lists.opencsw.org/pipermail/maintainers/2010-November/013224.html
>> http://lists.opencsw.org/pipermail/maintainers/2013-April/017968.html
>> http://lists.opencsw.org/pipermail/maintainers/2013-September/018607.html
>>
>> Looking forward to your plan! (But ad-hoc changes in the right
>> direction are welcome too!)
> Stefan, please don?t get demotivated by the long period this task has been going!
> If you need anything please let me know.
>
>
> Best regards
>
>    ? Dago
>
>


From maciej at opencsw.org  Wed Apr  9 09:59:47 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Wed, 9 Apr 2014 08:59:47 +0100
Subject: Propagate OpenSSL to all releases
In-Reply-To: <8E339FBD-E4CA-4290-B933-33875E3D5C69@opencsw.org>
References: <8E339FBD-E4CA-4290-B933-33875E3D5C69@opencsw.org>
Message-ID: <CALtRa-51Sz9CmmxokvBVP7pDYeqLT7NZkoRThQ7R+ro+-nLs0w@mail.gmail.com>

Go to http://quinoa.blizinski.pl/~maciej/opencsw/test.html
Input libssl1_0_0
Press enter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140409/49dcdbb2/attachment-0001.html>

From dam at opencsw.org  Wed Apr  9 13:23:52 2014
From: dam at opencsw.org (Dagobert Michelsen)
Date: Wed, 9 Apr 2014 04:23:52 -0700
Subject: Migrating documentation to the manual
In-Reply-To: <5344F542.4060808@opencsw.org>
References: <CALtRa-6CztUZS_uROLt=KFXo18wPPhpb+AbFtL=ai40LXUrnjA@mail.gmail.com>	<5342B088.7070407@opencsw.org>	<CALtRa-5y9=WngpCiWq_ZRPjhH426t1PHs-7YHgLXBNs1Mt6nvw@mail.gmail.com>
	<5E3A6DEA-1C7D-43AD-953A-91F38524516F@opencsw.org>
	<5344F542.4060808@opencsw.org>
Message-ID: <A7680228-B76F-40FF-A9D5-F5ACF81D6339@opencsw.org>

Hi Stefan,

Am 09.04.2014 um 00:22 schrieb Stefan Schnyder <aironskin at opencsw.org>:
> Not at all. I like this kind of work. :)
> I'd be great if you could boot up that VM you were talking about. I'd prefer to test stuff away from the production environment :)

That was a JIRA installation for the potential migration of the bug tracker.
I guess you want to fiddle more with Confluence? I can set up a new VM with
that for you, but it may a couple of days as I?m away.


Best regards

  ? Dago

> 
> Cheers,
> Stefan
> 
> On 04/09/2014 04:59 AM, Dagobert Michelsen wrote:
>> Hi Stefan,
>> 
>> Am 07.04.2014 um 14:22 schrieb Maciej (Matchek) Blizi?ski <maciej at opencsw.org>:
>>> 2014-04-07 15:04 GMT+01:00 Stefan Schnyder <aironskin at opencsw.org>:
>>>> However, I'd like to present some suggestions on how to consolidate the -
>>>> still relevant - information that is on the
>>>> website/manual/wiki/community/trac until the end of the week. And if people
>>>> support a new setup, I'd like to put more effort into that instead of the
>>>> current one.
>>> Yes, consolidation with a plan is definitely something we need and
>>> want. It has been on my mind for a few years:
>>> 
>>> http://lists.opencsw.org/pipermail/maintainers/2009-March/007260.html
>>> http://lists.opencsw.org/pipermail/maintainers/2010-November/013224.html
>>> http://lists.opencsw.org/pipermail/maintainers/2013-April/017968.html
>>> http://lists.opencsw.org/pipermail/maintainers/2013-September/018607.html
>>> 
>>> Looking forward to your plan! (But ad-hoc changes in the right
>>> direction are welcome too!)
>> Stefan, please don?t get demotivated by the long period this task has been going!
>> If you need anything please 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: smime.p7s
Type: application/pkcs7-signature
Size: 2418 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140409/8c0b9814/attachment.p7s>

From aironskin at opencsw.org  Wed Apr  9 17:36:21 2014
From: aironskin at opencsw.org (Stefan Schnyder)
Date: Wed, 09 Apr 2014 17:36:21 +0200
Subject: Migrating documentation to the manual
In-Reply-To: <A7680228-B76F-40FF-A9D5-F5ACF81D6339@opencsw.org>
References: <CALtRa-6CztUZS_uROLt=KFXo18wPPhpb+AbFtL=ai40LXUrnjA@mail.gmail.com>	<5342B088.7070407@opencsw.org>	<CALtRa-5y9=WngpCiWq_ZRPjhH426t1PHs-7YHgLXBNs1Mt6nvw@mail.gmail.com>	<5E3A6DEA-1C7D-43AD-953A-91F38524516F@opencsw.org>	<5344F542.4060808@opencsw.org>
	<A7680228-B76F-40FF-A9D5-F5ACF81D6339@opencsw.org>
Message-ID: <534568F5.20909@opencsw.org>

I don't need a dedicated VM for testing. I think Confluence and Jira 
might well work besides each other, right?
I'll start with the one that you booted up for me and see if I need 
anything more...

Thanks :)
Stefan

On 04/09/2014 01:23 PM, Dagobert Michelsen wrote:
> Hi Stefan,
>
> Am 09.04.2014 um 00:22 schrieb Stefan Schnyder <aironskin at opencsw.org>:
>> Not at all. I like this kind of work. :)
>> I'd be great if you could boot up that VM you were talking about. I'd prefer to test stuff away from the production environment :)
> That was a JIRA installation for the potential migration of the bug tracker.
> I guess you want to fiddle more with Confluence? I can set up a new VM with
> that for you, but it may a couple of days as I?m away.
>
>
> Best regards
>
>    ? Dago
>
>> Cheers,
>> Stefan
>>
>> On 04/09/2014 04:59 AM, Dagobert Michelsen wrote:
>>> Hi Stefan,
>>>
>>> Am 07.04.2014 um 14:22 schrieb Maciej (Matchek) Blizi?ski <maciej at opencsw.org>:
>>>> 2014-04-07 15:04 GMT+01:00 Stefan Schnyder <aironskin at opencsw.org>:
>>>>> However, I'd like to present some suggestions on how to consolidate the -
>>>>> still relevant - information that is on the
>>>>> website/manual/wiki/community/trac until the end of the week. And if people
>>>>> support a new setup, I'd like to put more effort into that instead of the
>>>>> current one.
>>>> Yes, consolidation with a plan is definitely something we need and
>>>> want. It has been on my mind for a few years:
>>>>
>>>> http://lists.opencsw.org/pipermail/maintainers/2009-March/007260.html
>>>> http://lists.opencsw.org/pipermail/maintainers/2010-November/013224.html
>>>> http://lists.opencsw.org/pipermail/maintainers/2013-April/017968.html
>>>> http://lists.opencsw.org/pipermail/maintainers/2013-September/018607.html
>>>>
>>>> Looking forward to your plan! (But ad-hoc changes in the right
>>>> direction are welcome too!)
>>> Stefan, please don?t get demotivated by the long period this task has been going!
>>> If you need anything please let me know.
>>>
>>>
>>> Best regards
>>>
>>>    ? Dago
>>>
>>>


From pfelecan at opencsw.org  Wed Apr  9 19:40:53 2014
From: pfelecan at opencsw.org (Peter FELECAN)
Date: Wed, 09 Apr 2014 19:40:53 +0200
Subject: Migrating documentation to the manual
In-Reply-To: <A7680228-B76F-40FF-A9D5-F5ACF81D6339@opencsw.org> (Dagobert
	Michelsen's message of "Wed, 9 Apr 2014 04:23:52 -0700")
References: <CALtRa-6CztUZS_uROLt=KFXo18wPPhpb+AbFtL=ai40LXUrnjA@mail.gmail.com>
	<5342B088.7070407@opencsw.org>
	<CALtRa-5y9=WngpCiWq_ZRPjhH426t1PHs-7YHgLXBNs1Mt6nvw@mail.gmail.com>
	<5E3A6DEA-1C7D-43AD-953A-91F38524516F@opencsw.org>
	<5344F542.4060808@opencsw.org>
	<A7680228-B76F-40FF-A9D5-F5ACF81D6339@opencsw.org>
Message-ID: <x6k3aybdui.fsf@opencsw.org>

Dagobert Michelsen <dam at opencsw.org> writes:

> I guess you want to fiddle more with Confluence?

Confluence you said? I'm using it for my current contract --- imposed by
the customer --- what a mess! Well, anything can be rendered a mess with
enough good will.
-- 
Peter

From aironskin at opencsw.org  Wed Apr  9 20:41:57 2014
From: aironskin at opencsw.org (Stefan Schnyder)
Date: Wed, 09 Apr 2014 20:41:57 +0200
Subject: Migrating documentation to the manual
In-Reply-To: <x6k3aybdui.fsf@opencsw.org>
References: <CALtRa-6CztUZS_uROLt=KFXo18wPPhpb+AbFtL=ai40LXUrnjA@mail.gmail.com>	<5342B088.7070407@opencsw.org>	<CALtRa-5y9=WngpCiWq_ZRPjhH426t1PHs-7YHgLXBNs1Mt6nvw@mail.gmail.com>	<5E3A6DEA-1C7D-43AD-953A-91F38524516F@opencsw.org>	<5344F542.4060808@opencsw.org>	<A7680228-B76F-40FF-A9D5-F5ACF81D6339@opencsw.org>
	<x6k3aybdui.fsf@opencsw.org>
Message-ID: <53459475.2080804@opencsw.org>

Peter,

A mess how? Would you be able to be more specific?
I've never set it up, but work with a few products who either use 
Confluence or Jira... and I've liked both products a lot so far.

I'd love to hear about your experiences.

Cheers,
Stefan

On 04/09/2014 07:40 PM, Peter FELECAN wrote:
> Dagobert Michelsen <dam at opencsw.org> writes:
>
>> I guess you want to fiddle more with Confluence?
> Confluence you said? I'm using it for my current contract --- imposed by
> the customer --- what a mess! Well, anything can be rendered a mess with
> enough good will.


From aironskin at opencsw.org  Wed Apr  9 23:49:54 2014
From: aironskin at opencsw.org (Stefan Schnyder)
Date: Wed, 09 Apr 2014 23:49:54 +0200
Subject: Announcements on www.opencsw.org
Message-ID: <5345C082.2000103@opencsw.org>

Hello maintainers,

As some of you (may) have noticed, the announcements on the frontpage of 
www.opencsw.org didn't really look nice the last few days.
It would take (me) quite some time to have the announcements display the 
same on the frontpage as they do when the entry is displayed fully 
without breaking the rest of the site.
That's why I switched back to summaries - for now.

What's your opinion, do you want the posts to be fully displayed or 
shall we leave it like they are now?

Cheers,
Stefan

From maciej at opencsw.org  Thu Apr 10 00:19:42 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Wed, 9 Apr 2014 23:19:42 +0100
Subject: Announcements on www.opencsw.org
In-Reply-To: <5345C082.2000103@opencsw.org>
References: <5345C082.2000103@opencsw.org>
Message-ID: <CALtRa-6u_LDAzfeE+_thw=6tBkBSzeOUEswvEJTmPiLepYwqKg@mail.gmail.com>

2014-04-09 22:49 GMT+01:00 Stefan Schnyder <aironskin at opencsw.org>:
> What's your opinion, do you want the posts to be fully displayed or shall we leave it like they are now?

I would strongly prefer full posts, even for the price of reverting to
a choisen generic wordpress template and adapting it lightly by
setting colors and adding our logo.

Maciej

From dam at opencsw.org  Thu Apr 10 15:38:40 2014
From: dam at opencsw.org (Dagobert Michelsen)
Date: Thu, 10 Apr 2014 06:38:40 -0700
Subject: Permissions on www for the manual
Message-ID: <3EF1F7BC-5BAC-499F-95AF-0B0BBDF31D14@opencsw.org>

Hi folks,

the ownership for the cswmanual was wrong the second time in a few days:

# ls -l;ls -l log
total 20
-rw-r--r--   1 cswmanual csw          405 Jan 27  2013 README
drwxr-xr-x   2 cswmanual csw            3 Jan 16  2013 bin
drwxr-xr-x   2 cswmanual csw            3 Jan 27  2013 log
drwxr-xr-x   7 wwwadmin csw           13 Apr 10 11:15 manual-html
drwxr-xr-x   6 cswmanual csw            7 Jan 16  2013 opencsw-manual
drwxr-xr-x   2 cswmanual csw            2 Dec  2 08:09 tmp
drwxr-xr-x   3 cswmanual csw            3 Dec  2 08:15 web
total 8
-rw-r--r--   1 wwwadmin csw         1637 Apr 10 11:15 buildlog

Is it possible that someone got wwwadmin and regenerated the manual?


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: smime.p7s
Type: application/pkcs7-signature
Size: 2418 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140410/a077f628/attachment-0001.p7s>

From aironskin at opencsw.org  Thu Apr 10 15:56:17 2014
From: aironskin at opencsw.org (Stefan Schnyder)
Date: Thu, 10 Apr 2014 15:56:17 +0200
Subject: Permissions on www for the manual
In-Reply-To: <3EF1F7BC-5BAC-499F-95AF-0B0BBDF31D14@opencsw.org>
References: <3EF1F7BC-5BAC-499F-95AF-0B0BBDF31D14@opencsw.org>
Message-ID: <5346A301.3000301@opencsw.org>

I guess that happend with the Wordpress update. The files come with 
ownership of nobody, which I had to set to wwwadmin:csw.
I wasn't aware that the manual used other permissions. Sorry about that.

Stefan

On 04/10/2014 03:38 PM, Dagobert Michelsen wrote:
> Hi folks,
>
> the ownership for the cswmanual was wrong the second time in a few days:
>
> # ls -l;ls -l log
> total 20
> -rw-r--r--   1 cswmanual csw          405 Jan 27  2013 README
> drwxr-xr-x   2 cswmanual csw            3 Jan 16  2013 bin
> drwxr-xr-x   2 cswmanual csw            3 Jan 27  2013 log
> drwxr-xr-x   7 wwwadmin csw           13 Apr 10 11:15 manual-html
> drwxr-xr-x   6 cswmanual csw            7 Jan 16  2013 opencsw-manual
> drwxr-xr-x   2 cswmanual csw            2 Dec  2 08:09 tmp
> drwxr-xr-x   3 cswmanual csw            3 Dec  2 08:15 web
> total 8
> -rw-r--r--   1 wwwadmin csw         1637 Apr 10 11:15 buildlog
>
> Is it possible that someone got wwwadmin and regenerated the manual?
>
>
> Best regards
>
>    ? Dago
>


From aironskin at opencsw.org  Thu Apr 10 16:34:10 2014
From: aironskin at opencsw.org (Stefan Schnyder)
Date: Thu, 10 Apr 2014 16:34:10 +0200
Subject: Announcements on www.opencsw.org
In-Reply-To: <CALtRa-6u_LDAzfeE+_thw=6tBkBSzeOUEswvEJTmPiLepYwqKg@mail.gmail.com>
References: <5345C082.2000103@opencsw.org>
	<CALtRa-6u_LDAzfeE+_thw=6tBkBSzeOUEswvEJTmPiLepYwqKg@mail.gmail.com>
Message-ID: <5346ABE2.1090806@opencsw.org>

Ok, the current frontpage looks nice (my opinion), displays dates ;D, 
and you can directly go to older entries (like on other blog sites)
I've edited a few posts to make them look nicer (added a few breaks).

Do we want YouTube videos embedded or linked? We changed some of them 
from embedded to links at the camp because it looked crappy with the 
design then.
Personally I don't like embedded videos much, but it would go well with 
the current design. Let me know what I should do.

Cheers,
Stefan

On 04/10/2014 12:19 AM, Maciej (Matchek) Blizi?ski wrote:
> 2014-04-09 22:49 GMT+01:00 Stefan Schnyder <aironskin at opencsw.org>:
>> What's your opinion, do you want the posts to be fully displayed or shall we leave it like they are now?
> I would strongly prefer full posts, even for the price of reverting to
> a choisen generic wordpress template and adapting it lightly by
> setting colors and adding our logo.
>
> Maciej
>


From dam at opencsw.org  Thu Apr 10 16:45:52 2014
From: dam at opencsw.org (Dagobert Michelsen)
Date: Thu, 10 Apr 2014 07:45:52 -0700
Subject: Announcements on www.opencsw.org
In-Reply-To: <5346ABE2.1090806@opencsw.org>
References: <5345C082.2000103@opencsw.org>
	<CALtRa-6u_LDAzfeE+_thw=6tBkBSzeOUEswvEJTmPiLepYwqKg@mail.gmail.com>
	<5346ABE2.1090806@opencsw.org>
Message-ID: <6A374E74-8F74-4EE6-A8D6-BB8BDA57D6DE@opencsw.org>

Hi Stefan,

Am 10.04.2014 um 07:34 schrieb Stefan Schnyder <aironskin at opencsw.org>:
> Ok, the current frontpage looks nice (my opinion), displays dates ;D, and you can directly go to older entries (like on other blog sites)
> I've edited a few posts to make them look nicer (added a few breaks).
> 
> Do we want YouTube videos embedded or linked? We changed some of them from embedded to links at the camp because it looked crappy with the design then.
> Personally I don't like embedded videos much, but it would go well with the current design. Let me know what I should do.

This looks excellent! Regarding the videos I think it is good as it is.
I found it a bit disturbing previosuly to find the embedded video with
the startpicture being me looking down at the keyboard ;-)


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: smime.p7s
Type: application/pkcs7-signature
Size: 2418 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140410/ca6c77ab/attachment.p7s>

From pfelecan at opencsw.org  Fri Apr 11 20:09:15 2014
From: pfelecan at opencsw.org (Peter FELECAN)
Date: Fri, 11 Apr 2014 20:09:15 +0200
Subject: Migrating documentation to the manual
In-Reply-To: <53459475.2080804@opencsw.org> (Stefan Schnyder's message of
	"Wed, 09 Apr 2014 20:41:57 +0200")
References: <CALtRa-6CztUZS_uROLt=KFXo18wPPhpb+AbFtL=ai40LXUrnjA@mail.gmail.com>
	<5342B088.7070407@opencsw.org>
	<CALtRa-5y9=WngpCiWq_ZRPjhH426t1PHs-7YHgLXBNs1Mt6nvw@mail.gmail.com>
	<5E3A6DEA-1C7D-43AD-953A-91F38524516F@opencsw.org>
	<5344F542.4060808@opencsw.org>
	<A7680228-B76F-40FF-A9D5-F5ACF81D6339@opencsw.org>
	<x6k3aybdui.fsf@opencsw.org> <53459475.2080804@opencsw.org>
Message-ID: <x64n1zbuwk.fsf@opencsw.org>

Stefan Schnyder <aironskin at opencsw.org> writes:

> A mess how? Would you be able to be more specific?

1. Wihtout a coherent document plan any system can be messy and this is
   tool agnostic.

2. The WYSIWG nature of Confluence editor is, IMHO, inferior to Trac or
   other wiki systems, but this is the opinion of a computer literate;
   even the system used for the manual is better than this.

3. The "social" features of Confluence are annoying warts; really, who
   needs "like" buttons?

4. Everything is inferior in terms of result to LaTeX.

Anyhow, all of the above are subjective and I'll agree with the choice
of those who are working to make things better; if they are.
-- 
Peter

From maciej at opencsw.org  Fri Apr 11 20:35:10 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Fri, 11 Apr 2014 19:35:10 +0100
Subject: Migrating documentation to the manual
In-Reply-To: <A7680228-B76F-40FF-A9D5-F5ACF81D6339@opencsw.org>
References: <CALtRa-6CztUZS_uROLt=KFXo18wPPhpb+AbFtL=ai40LXUrnjA@mail.gmail.com>
	<5342B088.7070407@opencsw.org>
	<CALtRa-5y9=WngpCiWq_ZRPjhH426t1PHs-7YHgLXBNs1Mt6nvw@mail.gmail.com>
	<5E3A6DEA-1C7D-43AD-953A-91F38524516F@opencsw.org>
	<5344F542.4060808@opencsw.org>
	<A7680228-B76F-40FF-A9D5-F5ACF81D6339@opencsw.org>
Message-ID: <CALtRa-4CYztaBayh8CCevJPFd_nvBgnYRwsDVaVQgAmNn96=Kw@mail.gmail.com>

2014-04-09 12:23 GMT+01:00 Dagobert Michelsen <dam at opencsw.org>:
> That was a JIRA installation for the potential migration of the bug tracker.
> I guess you want to fiddle more with Confluence? I can set up a new VM with
> that for you, but it may a couple of days as I?m away.

I didn't realize this was about bug tracking as well.

Bug tracking is an especially hard problem for us, because most bug
trackers aren't designed to efficiently handle 4000+ projects.

I think we should keep documentation and bugtracking in separate
places. This will give us more flexibility in both.

In this particular thread I wanted to focus on moving this one
specific page to the manual. I guess that shouldn't clash with your
plans, unless you're thinking of migrating the manual[1] to a different place

Maciej

[1] http://www.opencsw.org/manual/

From dam at opencsw.org  Sat Apr 12 03:25:53 2014
From: dam at opencsw.org (Dagobert Michelsen)
Date: Fri, 11 Apr 2014 18:25:53 -0700
Subject: Migrating documentation to the manual
In-Reply-To: <CALtRa-4CYztaBayh8CCevJPFd_nvBgnYRwsDVaVQgAmNn96=Kw@mail.gmail.com>
References: <CALtRa-6CztUZS_uROLt=KFXo18wPPhpb+AbFtL=ai40LXUrnjA@mail.gmail.com>
	<5342B088.7070407@opencsw.org>
	<CALtRa-5y9=WngpCiWq_ZRPjhH426t1PHs-7YHgLXBNs1Mt6nvw@mail.gmail.com>
	<5E3A6DEA-1C7D-43AD-953A-91F38524516F@opencsw.org>
	<5344F542.4060808@opencsw.org>
	<A7680228-B76F-40FF-A9D5-F5ACF81D6339@opencsw.org>
	<CALtRa-4CYztaBayh8CCevJPFd_nvBgnYRwsDVaVQgAmNn96=Kw@mail.gmail.com>
Message-ID: <5D3817A4-778F-4255-B729-EE0A17D77A12@opencsw.org>

Hi Maciej,

Am 11.04.2014 um 11:35 schrieb Maciej (Matchek) Blizi?ski <maciej at opencsw.org>:
> 2014-04-09 12:23 GMT+01:00 Dagobert Michelsen <dam at opencsw.org>:
>> That was a JIRA installation for the potential migration of the bug tracker.
>> I guess you want to fiddle more with Confluence? I can set up a new VM with
>> that for you, but it may a couple of days as I?m away.
> 
> I didn't realize this was about bug tracking as well.

No, it wasn?t :-) I just had this perfectly configured VM at hand with
already one experimental atlassian product on it, so I guessed I could
just repurpose it.

> Bug tracking is an especially hard problem for us, because most bug
> trackers aren't designed to efficiently handle 4000+ projects.
> 
> I think we should keep documentation and bugtracking in separate
> places. This will give us more flexibility in both.

Yes. Definitely. The long-term idea was more like confluence for wiki and
jira as bugtracker.

> In this particular thread I wanted to focus on moving this one
> specific page to the manual. I guess that shouldn't clash with your
> plans, unless you're thinking of migrating the manual[1] to a different place

This is definitely a good idea.


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: smime.p7s
Type: application/pkcs7-signature
Size: 2418 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140411/09484f9b/attachment-0001.p7s>

From maciej at opencsw.org  Sat Apr 12 13:07:40 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sat, 12 Apr 2014 12:07:40 +0100
Subject: Killing newpkgs and pkgsubmissions lists
Message-ID: <CALtRa-7KWvT805aci8Luq=gqjBU2KhaNpgyvQwPbojMnE5sEXQ@mail.gmail.com>

Hi Ihsan,

I propose we kill the newpkgs and pkgsubmissions mailing lists and remove
them from the listinfo page[1]. They aren't used any more.

Maciej

[1] https://lists.opencsw.org/mailman/listinfo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140412/8c610f09/attachment.html>

From bwalton at opencsw.org  Sun Apr 13 09:00:50 2014
From: bwalton at opencsw.org (Ben Walton)
Date: Sun, 13 Apr 2014 03:00:50 -0400
Subject: Board Election
In-Reply-To: <CAP30j16qFFrP-NQx5QXoEpJ1f4QfytPgo0Wf43BOg2K5Yv=3XQ@mail.gmail.com>
References: <CAP30j16kGORp7oBtGbZGvsvfxsVveL_Mi7D+vSjPdUn7K10mZw@mail.gmail.com>
	<CAP30j16qFFrP-NQx5QXoEpJ1f4QfytPgo0Wf43BOg2K5Yv=3XQ@mail.gmail.com>
Message-ID: <CAP30j17bbfRzKi-jTcV74uyJHwgJZrFG6hxrQPssHSkJTFHEmQ@mail.gmail.com>

Hi All,

We have three nominees for the board and there are three available
positions. Unless there are objections, I'd simply declare this
election completed and let the new board be formed. (Objections should
be in the form of self nomination, I think. :) )

Objections/nominations? If I've not heard anything in a few days, I'll
let the new board know that they should delegate positions and we'll
then coordinate any required handover of duties.

Thanks
-Ben


On Sat, Feb 22, 2014 at 4:58 AM, Ben Walton <bwalton at opencsw.org> wrote:
> Hi Folks,
>
> We have two nominees for the new board, but have three positions to fill. Is
> anyone else interested in running? There are many active maintainers that
> I'd love to see step up...
>
> Thanks
> -Ben
>
> On Feb 8, 2014 10:41 AM, "Ben Walton" <bwalton at opencsw.org> wrote:
>>
>> Hi All,
>>
>> It's time to elect a new board. We're a little behind schedule, but
>> not as much as in previous years! :)
>>
>> I've created a blank nomination page in the wiki here:
>> http://wiki.opencsw.org/boardelection2014
>>
>> All that is required to run is current membership status. I'd
>> encourage anyone interested to step forward.
>>
>> I'll leave the nominations open for two weeks at which point we'll
>> evaluate the roster to see whether an election is necessary. I'd be
>> really happy to see lots of names there!
>>
>> Thanks
>> -Ben

From rupert at opencsw.org  Sun Apr 13 11:06:52 2014
From: rupert at opencsw.org (rupert THURNER)
Date: Sun, 13 Apr 2014 11:06:52 +0200
Subject: Board Election
In-Reply-To: <CAP30j17bbfRzKi-jTcV74uyJHwgJZrFG6hxrQPssHSkJTFHEmQ@mail.gmail.com>
References: <CAP30j16kGORp7oBtGbZGvsvfxsVveL_Mi7D+vSjPdUn7K10mZw@mail.gmail.com>
	<CAP30j16qFFrP-NQx5QXoEpJ1f4QfytPgo0Wf43BOg2K5Yv=3XQ@mail.gmail.com>
	<CAP30j17bbfRzKi-jTcV74uyJHwgJZrFG6hxrQPssHSkJTFHEmQ@mail.gmail.com>
Message-ID: <CAJs9aZ9z+k6ToKcQBBp2e+w+LgWCZObZe1ka0DJM2k-NwaxKDQ@mail.gmail.com>

good to me.

rupert


On Sun, Apr 13, 2014 at 9:00 AM, Ben Walton <bwalton at opencsw.org> wrote:
> Hi All,
>
> We have three nominees for the board and there are three available
> positions. Unless there are objections, I'd simply declare this
> election completed and let the new board be formed. (Objections should
> be in the form of self nomination, I think. :) )
>
> Objections/nominations? If I've not heard anything in a few days, I'll
> let the new board know that they should delegate positions and we'll
> then coordinate any required handover of duties.
>
> Thanks
> -Ben
>
>
> On Sat, Feb 22, 2014 at 4:58 AM, Ben Walton <bwalton at opencsw.org> wrote:
>> Hi Folks,
>>
>> We have two nominees for the new board, but have three positions to fill. Is
>> anyone else interested in running? There are many active maintainers that
>> I'd love to see step up...
>>
>> Thanks
>> -Ben
>>
>> On Feb 8, 2014 10:41 AM, "Ben Walton" <bwalton at opencsw.org> wrote:
>>>
>>> Hi All,
>>>
>>> It's time to elect a new board. We're a little behind schedule, but
>>> not as much as in previous years! :)
>>>
>>> I've created a blank nomination page in the wiki here:
>>> http://wiki.opencsw.org/boardelection2014
>>>
>>> All that is required to run is current membership status. I'd
>>> encourage anyone interested to step forward.
>>>
>>> I'll leave the nominations open for two weeks at which point we'll
>>> evaluate the roster to see whether an election is necessary. I'd be
>>> really happy to see lots of names there!
>>>
>>> Thanks
>>> -Ben

From raos at opencsw.org  Sun Apr 13 11:12:27 2014
From: raos at opencsw.org (Rafael Ostertag)
Date: Sun, 13 Apr 2014 11:12:27 +0200
Subject: csw-upload-pkg on login
Message-ID: <20140413091227.GG18049@bender.opencsw.org>

Hi guys

I'm trying to upload package on login. csw-upload-pkg dies with

 -bash: /opt/csw/bin/csw-upload-pkg: /opt/csw/bin/bash: bad interpreter: No such file or directory

Is there something I missed?

cheers
rafi

From maciej at opencsw.org  Sun Apr 13 11:44:01 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sun, 13 Apr 2014 10:44:01 +0100
Subject: csw-upload-pkg on login
In-Reply-To: <20140413091227.GG18049@bender.opencsw.org>
References: <20140413091227.GG18049@bender.opencsw.org>
Message-ID: <CALtRa-75v6zdLuWuSzS8KHUUSeyQ7YB_BegaVeGvjJTGCeMBMA@mail.gmail.com>

2014-04-13 10:12 GMT+01:00 Rafael Ostertag <raos at opencsw.org>:

> I'm trying to upload package on login. csw-upload-pkg dies with
>
>  -bash: /opt/csw/bin/csw-upload-pkg: /opt/csw/bin/bash: bad interpreter:
> No such file or directory
>
> Is there something I missed?
>

At least you could log in. I can't.

$ ssh maciej at login.opencsw.org
Password:

We probably need to wait for Dago or Jan to show up and fix it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140413/afe68fbf/attachment.html>

From raos at opencsw.org  Sun Apr 13 11:46:29 2014
From: raos at opencsw.org (Rafael Ostertag)
Date: Sun, 13 Apr 2014 11:46:29 +0200
Subject: csw-upload-pkg on login
In-Reply-To: <CALtRa-75v6zdLuWuSzS8KHUUSeyQ7YB_BegaVeGvjJTGCeMBMA@mail.gmail.com>
References: <20140413091227.GG18049@bender.opencsw.org>
	<CALtRa-75v6zdLuWuSzS8KHUUSeyQ7YB_BegaVeGvjJTGCeMBMA@mail.gmail.com>
Message-ID: <20140413094629.GH18049@bender.opencsw.org>

Hi Maciej

On Sun, Apr 13, 2014 at 10:44:01AM +0100, Maciej (Matchek) Blizi??ski wrote:
> 2014-04-13 10:12 GMT+01:00 Rafael Ostertag <raos at opencsw.org>:
> 
> > I'm trying to upload package on login. csw-upload-pkg dies with
> >
> >  -bash: /opt/csw/bin/csw-upload-pkg: /opt/csw/bin/bash: bad interpreter:
> > No such file or directory
> >
> > Is there something I missed?
> >
> 
> At least you could log in. I can't.

I opened the session yesterday or so :)

> 
> $ ssh maciej at login.opencsw.org
> Password:
> 
> We probably need to wait for Dago or Jan to show up and fix it.
Ok.

so long
rafi

From jh at opencsw.org  Sun Apr 13 11:55:42 2014
From: jh at opencsw.org (=?ISO-8859-1?Q?Jan_Holzh=FCter?=)
Date: Sun, 13 Apr 2014 11:55:42 +0200
Subject: csw-upload-pkg on login
In-Reply-To: <20140413094629.GH18049@bender.opencsw.org>
References: <20140413091227.GG18049@bender.opencsw.org>	<CALtRa-75v6zdLuWuSzS8KHUUSeyQ7YB_BegaVeGvjJTGCeMBMA@mail.gmail.com>
	<20140413094629.GH18049@bender.opencsw.org>
Message-ID: <534A5F1E.90405@opencsw.org>

Hi,

Am 13.04.14 11:46, schrieb Rafael Ostertag:
> Hi Maciej
> 
> On Sun, Apr 13, 2014 at 10:44:01AM +0100, Maciej (Matchek) Blizi??ski wrote:
>> 2014-04-13 10:12 GMT+01:00 Rafael Ostertag <raos at opencsw.org>:
>>
>>> I'm trying to upload package on login. csw-upload-pkg dies with
>>>
>>>  -bash: /opt/csw/bin/csw-upload-pkg: /opt/csw/bin/bash: bad interpreter:
>>> No such file or directory

bash was missing. However that happened :)
fixed now

Greeting Jan

From raos at opencsw.org  Sun Apr 13 12:03:36 2014
From: raos at opencsw.org (Rafael Ostertag)
Date: Sun, 13 Apr 2014 12:03:36 +0200
Subject: csw-upload-pkg on login
In-Reply-To: <534A5F1E.90405@opencsw.org>
References: <20140413091227.GG18049@bender.opencsw.org>
	<CALtRa-75v6zdLuWuSzS8KHUUSeyQ7YB_BegaVeGvjJTGCeMBMA@mail.gmail.com>
	<20140413094629.GH18049@bender.opencsw.org>
	<534A5F1E.90405@opencsw.org>
Message-ID: <20140413100336.GI18049@bender.opencsw.org>

Hi Jan

On Sun, Apr 13, 2014 at 11:55:42AM +0200, Jan Holzh?ter wrote:
> >>>  -bash: /opt/csw/bin/csw-upload-pkg: /opt/csw/bin/bash: bad interpreter:
> >>> No such file or directory
> 
> bash was missing. However that happened :)
> fixed now
sweet. Thx.

cheers
rafi

From raos at opencsw.org  Sun Apr 13 12:09:11 2014
From: raos at opencsw.org (Rafael Ostertag)
Date: Sun, 13 Apr 2014 12:09:11 +0200
Subject: csw-upload-pkg on login
In-Reply-To: <534A5F1E.90405@opencsw.org>
References: <20140413091227.GG18049@bender.opencsw.org>
	<CALtRa-75v6zdLuWuSzS8KHUUSeyQ7YB_BegaVeGvjJTGCeMBMA@mail.gmail.com>
	<20140413094629.GH18049@bender.opencsw.org>
	<534A5F1E.90405@opencsw.org>
Message-ID: <20140413100911.GJ18049@bender.opencsw.org>

On Sun, Apr 13, 2014 at 11:55:42AM +0200, Jan Holzh?ter wrote:
> Hi,
> bash was missing. However that happened :)
> fixed now

Ok, bash is there, but now csw_upload_pkg complains about pycurl not found:

login$ csw-upload-pkg *8.4.21*
/opt/csw/bin/csw-upload-pkg is a wrapper, running /home/raos/opencsw/.buildsys/v2/bin/csw-upload-pkg libecpg6-8.4.21,REV=2014.04.12-SunOS5.10-i386-CSW.pkg.gz ...
Traceback (most recent call last):
  File "/home/raos/opencsw/.buildsys/v2/bin/../lib/python/csw_upload_pkg.py", line 16, in <module>
    import pycurl
ImportError: No module named pycurl

cheers
rafi

From jh at opencsw.org  Sun Apr 13 12:24:24 2014
From: jh at opencsw.org (=?ISO-8859-1?Q?Jan_Holzh=FCter?=)
Date: Sun, 13 Apr 2014 12:24:24 +0200
Subject: csw-upload-pkg on login
In-Reply-To: <20140413100911.GJ18049@bender.opencsw.org>
References: <20140413091227.GG18049@bender.opencsw.org>	<CALtRa-75v6zdLuWuSzS8KHUUSeyQ7YB_BegaVeGvjJTGCeMBMA@mail.gmail.com>	<20140413094629.GH18049@bender.opencsw.org>	<534A5F1E.90405@opencsw.org>
	<20140413100911.GJ18049@bender.opencsw.org>
Message-ID: <534A65D8.1070206@opencsw.org>

Hi

Am 13.04.14 12:09, schrieb Rafael Ostertag:
> On Sun, Apr 13, 2014 at 11:55:42AM +0200, Jan Holzh?ter wrote:
>> Hi,
>> bash was missing. However that happened :)
>> fixed now
> 
> Ok, bash is there, but now csw_upload_pkg complains about pycurl not found:
> 
> login$ csw-upload-pkg *8.4.21*
> /opt/csw/bin/csw-upload-pkg is a wrapper, running /home/raos/opencsw/.buildsys/v2/bin/csw-upload-pkg libecpg6-8.4.21,REV=2014.04.12-SunOS5.10-i386-CSW.pkg.gz ...
> Traceback (most recent call last):
>   File "/home/raos/opencsw/.buildsys/v2/bin/../lib/python/csw_upload_pkg.py", line 16, in <module>
>     import pycurl
> ImportError: No module named pycurl


installed too
now :)




From raos at opencsw.org  Sun Apr 13 16:18:29 2014
From: raos at opencsw.org (Rafael Ostertag)
Date: Sun, 13 Apr 2014 16:18:29 +0200
Subject: csw-upload-pkg on login
In-Reply-To: <534A65D8.1070206@opencsw.org>
References: <20140413091227.GG18049@bender.opencsw.org>
	<CALtRa-75v6zdLuWuSzS8KHUUSeyQ7YB_BegaVeGvjJTGCeMBMA@mail.gmail.com>
	<20140413094629.GH18049@bender.opencsw.org>
	<534A5F1E.90405@opencsw.org>
	<20140413100911.GJ18049@bender.opencsw.org>
	<534A65D8.1070206@opencsw.org>
Message-ID: <20140413141829.GK18049@bender.opencsw.org>

On Sun, Apr 13, 2014 at 12:24:24PM +0200, Jan Holzh?ter wrote:
> Hi
> 
> Am 13.04.14 12:09, schrieb Rafael Ostertag:
> > On Sun, Apr 13, 2014 at 11:55:42AM +0200, Jan Holzh?ter wrote:
> >> Hi,
> >> bash was missing. However that happened :)
> >> fixed now
> > 
> > Ok, bash is there, but now csw_upload_pkg complains about pycurl not found:
> > 
> > login$ csw-upload-pkg *8.4.21*
> > /opt/csw/bin/csw-upload-pkg is a wrapper, running /home/raos/opencsw/.buildsys/v2/bin/csw-upload-pkg libecpg6-8.4.21,REV=2014.04.12-SunOS5.10-i386-CSW.pkg.gz ...
> > Traceback (most recent call last):
> >   File "/home/raos/opencsw/.buildsys/v2/bin/../lib/python/csw_upload_pkg.py", line 16, in <module>
> >     import pycurl
> > ImportError: No module named pycurl
> 
> 
> installed too
> now :)
Great. Worked.

But now, opencsw ssh is missing:

ssh unstable10s
-bash: /opt/csw/bin/ssh: No such file or directory

cheers
rafi

From jh at opencsw.org  Sun Apr 13 16:24:58 2014
From: jh at opencsw.org (=?ISO-8859-1?Q?Jan_Holzh=FCter?=)
Date: Sun, 13 Apr 2014 16:24:58 +0200
Subject: csw-upload-pkg on login
In-Reply-To: <20140413141829.GK18049@bender.opencsw.org>
References: <20140413091227.GG18049@bender.opencsw.org>	<CALtRa-75v6zdLuWuSzS8KHUUSeyQ7YB_BegaVeGvjJTGCeMBMA@mail.gmail.com>	<20140413094629.GH18049@bender.opencsw.org>	<534A5F1E.90405@opencsw.org>	<20140413100911.GJ18049@bender.opencsw.org>	<534A65D8.1070206@opencsw.org>
	<20140413141829.GK18049@bender.opencsw.org>
Message-ID: <534A9E3A.2050501@opencsw.org>

Hi,

Am 13.04.14 16:18, schrieb Rafael Ostertag:
> On Sun, Apr 13, 2014 at 12:24:24PM +0200, Jan Holzh?ter wrote:
>> Hi
>>
>> Am 13.04.14 12:09, schrieb Rafael Ostertag:
>>> On Sun, Apr 13, 2014 at 11:55:42AM +0200, Jan Holzh?ter wrote:
>>>> Hi,
>>>> bash was missing. However that happened :)
>>>> fixed now
>>>
>>> Ok, bash is there, but now csw_upload_pkg complains about pycurl not found:
>>>
>>> login$ csw-upload-pkg *8.4.21*
>>> /opt/csw/bin/csw-upload-pkg is a wrapper, running /home/raos/opencsw/.buildsys/v2/bin/csw-upload-pkg libecpg6-8.4.21,REV=2014.04.12-SunOS5.10-i386-CSW.pkg.gz ...
>>> Traceback (most recent call last):
>>>   File "/home/raos/opencsw/.buildsys/v2/bin/../lib/python/csw_upload_pkg.py", line 16, in <module>
>>>     import pycurl
>>> ImportError: No module named pycurl
>>
>>
>> installed too
>> now :)
> Great. Worked.
> 
> But now, opencsw ssh is missing:
> 
> ssh unstable10s
> -bash: /opt/csw/bin/ssh: No such file or directory

gee there is probably even more broken.
There seems be a a pkgutil -U -u run went wrong. :)


Greetings
Jan


From raos at opencsw.org  Sun Apr 13 16:34:39 2014
From: raos at opencsw.org (Rafael Ostertag)
Date: Sun, 13 Apr 2014 16:34:39 +0200
Subject: csw-upload-pkg on login
In-Reply-To: <534A9E3A.2050501@opencsw.org>
References: <20140413091227.GG18049@bender.opencsw.org>
	<CALtRa-75v6zdLuWuSzS8KHUUSeyQ7YB_BegaVeGvjJTGCeMBMA@mail.gmail.com>
	<20140413094629.GH18049@bender.opencsw.org>
	<534A5F1E.90405@opencsw.org>
	<20140413100911.GJ18049@bender.opencsw.org>
	<534A65D8.1070206@opencsw.org>
	<20140413141829.GK18049@bender.opencsw.org>
	<534A9E3A.2050501@opencsw.org>
Message-ID: <20140413143439.GM18049@bender.opencsw.org>

On Sun, Apr 13, 2014 at 04:24:58PM +0200, Jan Holzh?ter wrote:
> Hi,
> 
> Am 13.04.14 16:18, schrieb Rafael Ostertag:
> > On Sun, Apr 13, 2014 at 12:24:24PM +0200, Jan Holzh?ter wrote:
> >> Hi
> >>
> >> Am 13.04.14 12:09, schrieb Rafael Ostertag:
> >>> On Sun, Apr 13, 2014 at 11:55:42AM +0200, Jan Holzh?ter wrote:
> >>>> Hi,
> >>>> bash was missing. However that happened :)
> >>>> fixed now
> >>>
> >>> Ok, bash is there, but now csw_upload_pkg complains about pycurl not found:
> >>>
> >>> login$ csw-upload-pkg *8.4.21*
> >>> /opt/csw/bin/csw-upload-pkg is a wrapper, running /home/raos/opencsw/.buildsys/v2/bin/csw-upload-pkg libecpg6-8.4.21,REV=2014.04.12-SunOS5.10-i386-CSW.pkg.gz ...
> >>> Traceback (most recent call last):
> >>>   File "/home/raos/opencsw/.buildsys/v2/bin/../lib/python/csw_upload_pkg.py", line 16, in <module>
> >>>     import pycurl
> >>> ImportError: No module named pycurl
> >>
> >>
> >> installed too
> >> now :)
> > Great. Worked.
> > 
> > But now, opencsw ssh is missing:
> > 
> > ssh unstable10s
> > -bash: /opt/csw/bin/ssh: No such file or directory
> 
> gee there is probably even more broken.
> There seems be a a pkgutil -U -u run went wrong. :)

No worries. I'll report as I go along... ;)

cheers
rafi
> 
> 
> Greetings
> Jan
> 

From dam at opencsw.org  Sun Apr 13 16:56:20 2014
From: dam at opencsw.org (Dagobert Michelsen)
Date: Sun, 13 Apr 2014 07:56:20 -0700
Subject: Broken login
Message-ID: <808B48D7-8EEB-4751-8622-6821779286BF@opencsw.org>

Hi folks,

I was updating ?login? yesterday to the latest release and then went on with other stuff
as the update ran for quite a while. As it seems the update got stuck during updating
fontcache (I need to look into that). Regardless from that when I noticed the error the
pkgutil run aborted due to an error during installation in the fontconfig package.
The difficult problem is that pkgutil removes all packages and exits on error without
being able to continue or leaving a trace what is left to be done. It would be very useful
to have some ?what is yet to do? statusfile/script somewhere to pick up at that exact
location and finish the work.


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: smime.p7s
Type: application/pkcs7-signature
Size: 2418 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140413/23ec31f6/attachment.p7s>

From maciej at opencsw.org  Sun Apr 13 17:07:56 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sun, 13 Apr 2014 16:07:56 +0100
Subject: Migrating documentation to the manual
In-Reply-To: <5D3817A4-778F-4255-B729-EE0A17D77A12@opencsw.org>
References: <CALtRa-6CztUZS_uROLt=KFXo18wPPhpb+AbFtL=ai40LXUrnjA@mail.gmail.com>
	<5342B088.7070407@opencsw.org>
	<CALtRa-5y9=WngpCiWq_ZRPjhH426t1PHs-7YHgLXBNs1Mt6nvw@mail.gmail.com>
	<5E3A6DEA-1C7D-43AD-953A-91F38524516F@opencsw.org>
	<5344F542.4060808@opencsw.org>
	<A7680228-B76F-40FF-A9D5-F5ACF81D6339@opencsw.org>
	<CALtRa-4CYztaBayh8CCevJPFd_nvBgnYRwsDVaVQgAmNn96=Kw@mail.gmail.com>
	<5D3817A4-778F-4255-B729-EE0A17D77A12@opencsw.org>
Message-ID: <CALtRa-6RRt8KEbbM3W1DtXf7tFUEP2i3NipMY1ZdeHov1x3A+g@mail.gmail.com>

2014-04-12 2:25 GMT+01:00 Dagobert Michelsen <dam at opencsw.org>:
>
> This is definitely a good idea.

Cool. I've spent some time yesterday migrating content from wordpress
to the manual. Apart from migrating the content, I restructured the
manual a bit. If anyone is interested in the changes, you can see the
newest version here:

http://www.opencsw.org/manual/for-administrators/

Maciej

From maciej at opencsw.org  Sun Apr 13 22:42:26 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sun, 13 Apr 2014 21:42:26 +0100
Subject: Migrating documentation to the manual
In-Reply-To: <CALtRa-6RRt8KEbbM3W1DtXf7tFUEP2i3NipMY1ZdeHov1x3A+g@mail.gmail.com>
References: <CALtRa-6CztUZS_uROLt=KFXo18wPPhpb+AbFtL=ai40LXUrnjA@mail.gmail.com>
	<5342B088.7070407@opencsw.org>
	<CALtRa-5y9=WngpCiWq_ZRPjhH426t1PHs-7YHgLXBNs1Mt6nvw@mail.gmail.com>
	<5E3A6DEA-1C7D-43AD-953A-91F38524516F@opencsw.org>
	<5344F542.4060808@opencsw.org>
	<A7680228-B76F-40FF-A9D5-F5ACF81D6339@opencsw.org>
	<CALtRa-4CYztaBayh8CCevJPFd_nvBgnYRwsDVaVQgAmNn96=Kw@mail.gmail.com>
	<5D3817A4-778F-4255-B729-EE0A17D77A12@opencsw.org>
	<CALtRa-6RRt8KEbbM3W1DtXf7tFUEP2i3NipMY1ZdeHov1x3A+g@mail.gmail.com>
Message-ID: <CALtRa-5ozLQOrikb=z=NshBfEANHAQ-L8hxz88ptVFsDu63pMA@mail.gmail.com>

I found our meta-documentation. :)

http://www.opencsw.org/manual/for-maintainers/about-documentation.html

Please keep it up to date!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140413/83f8d2b9/attachment.html>

From maciej at opencsw.org  Mon Apr 14 01:07:30 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Mon, 14 Apr 2014 00:07:30 +0100
Subject: [board] Board Election
In-Reply-To: <CAP30j17bbfRzKi-jTcV74uyJHwgJZrFG6hxrQPssHSkJTFHEmQ@mail.gmail.com>
References: <CAP30j16kGORp7oBtGbZGvsvfxsVveL_Mi7D+vSjPdUn7K10mZw@mail.gmail.com>
	<CAP30j16qFFrP-NQx5QXoEpJ1f4QfytPgo0Wf43BOg2K5Yv=3XQ@mail.gmail.com>
	<CAP30j17bbfRzKi-jTcV74uyJHwgJZrFG6hxrQPssHSkJTFHEmQ@mail.gmail.com>
Message-ID: <CALtRa-5V=c6Cuy8vC1ru99CDGwfTkjQqdK=EM6OB5yG08vq+iQ@mail.gmail.com>

2014-04-13 8:00 GMT+01:00 Ben Walton <bwalton at opencsw.org>:
> Objections/nominations? If I've not heard anything in a few days, I'll
> let the new board know that they should delegate positions and we'll
> then coordinate any required handover of duties.

Sounds good!

From bonivart at opencsw.org  Mon Apr 14 14:29:25 2014
From: bonivart at opencsw.org (Peter Bonivart)
Date: Mon, 14 Apr 2014 14:29:25 +0200
Subject: Broken login
In-Reply-To: <808B48D7-8EEB-4751-8622-6821779286BF@opencsw.org>
References: <808B48D7-8EEB-4751-8622-6821779286BF@opencsw.org>
Message-ID: <CABY0g1VxJUTBOq9wcELse8rCoaOrvQYiSsdd1ZxnyZwGi7M46w@mail.gmail.com>

On Sun, Apr 13, 2014 at 4:56 PM, Dagobert Michelsen <dam at opencsw.org> wrote:
> Hi folks,
>
> I was updating "login" yesterday to the latest release and then went on with other stuff
> as the update ran for quite a while. As it seems the update got stuck during updating
> fontcache (I need to look into that). Regardless from that when I noticed the error the
> pkgutil run aborted due to an error during installation in the fontconfig package.
> The difficult problem is that pkgutil removes all packages and exits on error without
> being able to continue or leaving a trace what is left to be done. It would be very useful
> to have some "what is yet to do" statusfile/script somewhere to pick up at that exact
> location and finish the work.

Is this when you run it unattended with -y? Because if you don't then
you at least have a choice of continuing or not and you can easier
prepare for another run.

I've had this suggested before and it may be time to do something
about it. How about some runtime file that gets overwritten on the
next run or should we use syslog to be more resilient against a new
run erasing valuable logs? Timestamped filenames would be a mess I
think. A couple of syslog options in pkgutil.conf may do the trick.

/peter

From maciej at opencsw.org  Mon Apr 14 15:03:00 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Mon, 14 Apr 2014 14:03:00 +0100
Subject: Broken login
In-Reply-To: <CABY0g1VxJUTBOq9wcELse8rCoaOrvQYiSsdd1ZxnyZwGi7M46w@mail.gmail.com>
References: <808B48D7-8EEB-4751-8622-6821779286BF@opencsw.org>
	<CABY0g1VxJUTBOq9wcELse8rCoaOrvQYiSsdd1ZxnyZwGi7M46w@mail.gmail.com>
Message-ID: <CALtRa-5q6=WSd0ZeaN_OiMbZTCHv_3xBbzHPQQV3r94ayNHCLg@mail.gmail.com>

2014-04-14 13:29 GMT+01:00 Peter Bonivart <bonivart at opencsw.org>:
> should we use syslog to be more resilient against a new
> run erasing valuable logs?

How much data can be put in a syslog message? I was thinking about
something like this:

"running pkgutil; if this invocation runs, you can repeat it as
follows: /opt/csw/bin/pkgutil -y -i pkg1 pkg2 pkg3 ..."

This way you can go to syslog, and run pkgutil again to reproduce the problem.

Or maybe an own pkgutil log in with the same information. It could be
a long line with lots of packages, but it's 4k packages max, so still
manageable. It wouldn't crash your text editor.

Maciej

From bonivart at opencsw.org  Mon Apr 14 17:09:47 2014
From: bonivart at opencsw.org (Peter Bonivart)
Date: Mon, 14 Apr 2014 17:09:47 +0200
Subject: Broken login
In-Reply-To: <CALtRa-5q6=WSd0ZeaN_OiMbZTCHv_3xBbzHPQQV3r94ayNHCLg@mail.gmail.com>
References: <808B48D7-8EEB-4751-8622-6821779286BF@opencsw.org>
	<CABY0g1VxJUTBOq9wcELse8rCoaOrvQYiSsdd1ZxnyZwGi7M46w@mail.gmail.com>
	<CALtRa-5q6=WSd0ZeaN_OiMbZTCHv_3xBbzHPQQV3r94ayNHCLg@mail.gmail.com>
Message-ID: <CABY0g1UOx=kjzLDry6OhPNFH-iO0iagXkGeipU_YXeeqPg5NRA@mail.gmail.com>

On Mon, Apr 14, 2014 at 3:03 PM, Maciej (Matchek) Blizi?ski
<maciej at opencsw.org> wrote:
> 2014-04-14 13:29 GMT+01:00 Peter Bonivart <bonivart at opencsw.org>:
>> should we use syslog to be more resilient against a new
>> run erasing valuable logs?
>
> How much data can be put in a syslog message? I was thinking about
> something like this:

Isn't it only 1K or similar?

> "running pkgutil; if this invocation runs, you can repeat it as
> follows: /opt/csw/bin/pkgutil -y -i pkg1 pkg2 pkg3 ..."
>
> This way you can go to syslog, and run pkgutil again to reproduce the problem.
>
> Or maybe an own pkgutil log in with the same information. It could be
> a long line with lots of packages, but it's 4k packages max, so still
> manageable. It wouldn't crash your text editor.

I think we will probably break the syslog limit so a dedicated file
would be better to avoid that risk, logrotate can take care of
maintaining it.

From aironskin at opencsw.org  Tue Apr 15 13:28:46 2014
From: aironskin at opencsw.org (Stefan Schnyder)
Date: Tue, 15 Apr 2014 13:28:46 +0200
Subject: Consolidation
Message-ID: <534D17EE.5070202@opencsw.org>

Hi guys,

I'd like to share some thoughts about our documentation and information 
tools.

It's not hard to see, that "all that OpenCSW has" in regards to any kind 
of information for users/maintainers/devs is spread across a wide 
variety of tools & places.

Dago & I discussed this at the camp, and as Maciej has mentioned, parts 
of this have already been discussed earlier:

  * http://lists.opencsw.org/pipermail/maintainers/2009-March/007260.html
  * http://lists.opencsw.org/pipermail/maintainers/2010-November/013224.html
  * http://lists.opencsw.org/pipermail/maintainers/2013-April/017968.html
  * http://lists.opencsw.org/pipermail/maintainers/2013-September/018607.html


First of all, here's a list of all the tools & places I could find, that 
store information or act as a communication platform:
(tell me if I forgot something)

  * www.opencsw.org (Wordpress)
  * www.opencsw.org/manual (Sphinx - Python Documentation Generator)
  * www.opencsw.org/community (OpenSource Q&A)
  * opencsw.wikidot.com (WikiDot)
  * pkgutil.wikidot.com (WikiDot)
  * github.com/opencsw (GitHub with gar, pkg-all, discourse, osqa)
  * opencsw.sourceforge.net (HTML?)
  * sourceforge.net/projects/opencsw (SourceForge Project)
  * sourceforge.net/projects/gar (SourceForge Project)
  * sourceforge.net/apps/trac/gar & sourceforge.net/p/gar/tracwiki/Home
    (Trac, both sites seem to be the same)


Also - just as an overview - we have/use the following:

  * opencsw.org/mantis
  * buildfarm.opencsw.org
  * #opencsw on irc.freenode.net
  * Mail, Mailing Lists, Lists Archive, Webmail?
  * RSS Feeds
  * Flickr
  * YouTube
  * Google+
  * Twitter
  * Google Docs (group & shared files)
  * Facebook
  * Wikipedia
  * LinkedIn (nearly empty)


I'm not listing all of this because I think we should change it all. 
Just to raise awareness.

Now my thoughts:

  * I think, that our website doesn't need to contain that much
    information. It needs to get people started & provide access to
    further information and tools (Daniel had some nice ideas there).
  * The current info on the website, the manual, the wiki(s) and all
    info out there should be in one place. Preferably a tool which may
    be edited over a browser, if we want to give all people the ability
    to edit as well.
  * I support the idea of separating information from bugtracking from
    mailing lists from social media, etc. There should be only one place
    for the same kind of thing, but a place for each kind of thing.
  * The rework should be coupled with the new website that Daniel is
    working on.
  * It may be worth a thought if we should separate our "product" (the
    recipes & packages) from our own tools (gar, buildfarm, ...) or
    combine them. I'm talking about info & bugtracking & (...) for each
    or for both in one place. Having only one place would/could reduce
    the maintenance on the tools, but maybe lead to confusion for the users.
  * We should decide what needs to be done first, and what may come later.

I would like to propose, that we decide on a existing or new tool for 
storing & presenting information and then gradually start moving stuff 
away from the old locations. I would volunteer to do the moving.

What are your thoughts?

Cheers,
Stefan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140415/5d6fdbea/attachment-0001.html>

From dam at opencsw.org  Tue Apr 15 21:45:12 2014
From: dam at opencsw.org (Dagobert Michelsen)
Date: Tue, 15 Apr 2014 21:45:12 +0200
Subject: Broken login
In-Reply-To: <CABY0g1UOx=kjzLDry6OhPNFH-iO0iagXkGeipU_YXeeqPg5NRA@mail.gmail.com>
References: <808B48D7-8EEB-4751-8622-6821779286BF@opencsw.org>
	<CABY0g1VxJUTBOq9wcELse8rCoaOrvQYiSsdd1ZxnyZwGi7M46w@mail.gmail.com>
	<CALtRa-5q6=WSd0ZeaN_OiMbZTCHv_3xBbzHPQQV3r94ayNHCLg@mail.gmail.com>
	<CABY0g1UOx=kjzLDry6OhPNFH-iO0iagXkGeipU_YXeeqPg5NRA@mail.gmail.com>
Message-ID: <83563CE4-2A09-41F7-A8CE-E0BB8973C127@opencsw.org>

Hi Peter,

Am 14.04.2014 um 17:09 schrieb Peter Bonivart <bonivart at opencsw.org>:
>> 2014-04-14 13:29 GMT+01:00 Peter Bonivart <bonivart at opencsw.org>:
>> "running pkgutil; if this invocation runs, you can repeat it as
>> follows: /opt/csw/bin/pkgutil -y -i pkg1 pkg2 pkg3 ..."
>> 
>> This way you can go to syslog, and run pkgutil again to reproduce the problem.
>> 
>> Or maybe an own pkgutil log in with the same information. It could be
>> a long line with lots of packages, but it's 4k packages max, so still
>> manageable. It wouldn't crash your text editor.
> 
> I think we will probably break the syslog limit so a dedicated file
> would be better to avoid that risk, logrotate can take care of
> maintaining it.

Alternatively after each successfull installation the command for the
remaining packages could be put in /var/opt/csw/pkgutil/finish-pkgupdate.sh
or similar which would contain something like
  #!/bin/sh
  /opt/csw/bin/pkgutil -y -i <list of yet uninstalled packages>
and which is removed after pkgutil successfully installed all packages.
On reinvocation the commandfile must be correctly overwritten and executed
at the same time in some smart way :-)


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: smime.p7s
Type: application/pkcs7-signature
Size: 2418 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140415/6cfa3c5b/attachment.p7s>

From raos at opencsw.org  Wed Apr 16 08:26:35 2014
From: raos at opencsw.org (Rafael Ostertag)
Date: Wed, 16 Apr 2014 08:26:35 +0200
Subject: Unable to login on unstable10x
Message-ID: <20140416062635.GD17233@bender.opencsw.org>

Hi guys

When trying to login on unstable10x, I get the following

 login$ ssh unstable10x
 Connection closed by 192.168.1.33

Any ideas?

TIA

cheers
rafi

From jh at opencsw.org  Wed Apr 16 08:32:27 2014
From: jh at opencsw.org (Jan Holzhueter)
Date: Wed, 16 Apr 2014 08:32:27 +0200
Subject: Unable to login on unstable10x
In-Reply-To: <20140416062635.GD17233@bender.opencsw.org>
References: <20140416062635.GD17233@bender.opencsw.org>
Message-ID: <534E23FB.8060505@opencsw.org>

Hi,


Am 16.04.14 08:26, schrieb Rafael Ostertag:
> Hi guys
> 
> When trying to login on unstable10x, I get the following
> 
>  login$ ssh unstable10x
>  Connection closed by 192.168.1.33
> 
> Any ideas?
> 


yes I broke it :)
There might be more x86 build Servers broken.
Just let me know I will restart them.

unstable10x should be back now.


Greetings
Jan


From raos at opencsw.org  Wed Apr 16 08:43:42 2014
From: raos at opencsw.org (Rafael Ostertag)
Date: Wed, 16 Apr 2014 08:43:42 +0200
Subject: Unable to login on unstable10x
In-Reply-To: <534E23FB.8060505@opencsw.org>
References: <20140416062635.GD17233@bender.opencsw.org>
	<534E23FB.8060505@opencsw.org>
Message-ID: <20140416064342.GE17233@bender.opencsw.org>

Hi Jan
On Wed, Apr 16, 2014 at 08:32:27AM +0200, Jan Holzhueter wrote:
> Hi,
> 
> 
> Am 16.04.14 08:26, schrieb Rafael Ostertag:
> > Hi guys
> > 
> > When trying to login on unstable10x, I get the following
> > 
> >  login$ ssh unstable10x
> >  Connection closed by 192.168.1.33
> > 
> > Any ideas?
> > 
> 
> 
> yes I broke it :)
<lol>

> There might be more x86 build Servers broken.
> Just let me know I will restart them.
> 
> unstable10x should be back now.

Yep. Works again. :)

Thx
rafi

From pfelecan at opencsw.org  Wed Apr 16 20:02:01 2014
From: pfelecan at opencsw.org (Peter FELECAN)
Date: Wed, 16 Apr 2014 20:02:01 +0200
Subject: Consolidation
In-Reply-To: <534D17EE.5070202@opencsw.org> (Stefan Schnyder's message of
	"Tue, 15 Apr 2014 13:28:46 +0200")
References: <534D17EE.5070202@opencsw.org>
Message-ID: <x6vbu9886e.fsf@opencsw.org>

Stefan Schnyder <aironskin at opencsw.org> writes:

> What are your thoughts?

>From my POV, very positive. I endorse entirely your
endeavour. Unfortunately I don't have for the time being the bandwidth
to help in a consistent way.
-- 
Peter

From maciej at opencsw.org  Wed Apr 16 21:35:35 2014
From: maciej at opencsw.org (Maciej =?utf-8?Q?Blizi=C5=84ski?=)
Date: Wed, 16 Apr 2014 20:35:35 +0100
Subject: Consolidation
In-Reply-To: <534D17EE.5070202@opencsw.org>
References: <534D17EE.5070202@opencsw.org>
Message-ID: <20140416193535.GA31992@cotton.home.blizinski.pl>

Hi Stefan,

On Tue, Apr 15, 2014 at 01:28:46PM +0200, Stefan Schnyder wrote:
> Now my thoughts:
> 
>  * I think, that our website doesn't need to contain that much
>    information. It needs to get people started & provide access to
>    further information and tools (Daniel had some nice ideas there).

Yes, I agree.

>  * The current info on the website, the manual, the wiki(s) and all
>    info out there should be in one place. Preferably a tool which may
>    be edited over a browser, if we want to give all people the ability
>    to edit as well.

Two thoughts. One is that maybe not absolutely everything must be in one
place. Different documents are updated with different frequencies. For
example, we have a number of project pages on wikidot used to coordinate
collective efforts, for example the mass perl module rebuild. Others
such as the manual, are updated less frequently. Perhaps the collective
notepad case and the more static notepad case do not have to be accessed
with the same mechanism.

The second thought is access. For example, I like the checked in manual,
because it's simply part of our code base. If you can commit a build
recipe, you can commit a documentation change. The amount of friction is
a tiny bit higher compared to in-browser editing, but at the same time,
it's more inclusive: every maintainer has a text editor and subversion
access. You don't have to ask for extra permissions on wikidot, for
example. It's easy to test the changes: you edit files in
pkg/opencsw-manual/files, type "mgar clean install" and you can view
your modified manual online, e.g. for me the URL is:

http://buildfarm.opencsw.org/~maciej/opencsw-manual/

If people still think this is hard, I won't have an objection to
migrating elsewhere. But for now I want to propose that we stick with
a checked-in manual, and not require in-browser editing.

>  * I support the idea of separating information from bugtracking from
>    mailing lists from social media, etc. There should be only one place
>    for the same kind of thing, but a place for each kind of thing.
>  * The rework should be coupled with the new website that Daniel is
>    working on.
>  * It may be worth a thought if we should separate our "product" (the
>    recipes & packages) from our own tools (gar, buildfarm, ...) or
>    combine them. I'm talking about info & bugtracking & (...) for each
>    or for both in one place. Having only one place would/could reduce
>    the maintenance on the tools, but maybe lead to confusion for the users.

We've talked about this for a long time. AFAIR, Dago argued that it's
better to keep recipes and corresponding GAR versions in the same
repository, because you can check out the repository from a given point
in time and they're likely to match: you can check out an old recipe
from and old revision, get an old version of GAR and build it
successfully.

For my own workflow, I keep two separate checkouts, one for the recipes
and one for GAR (via git), so they're pretty much already separate for
me, and I think would could separate them. I also think that it doesn't
matter that much.

> I would like to propose, that we decide on a existing or new tool
> for storing & presenting information and then gradually start moving
> stuff away from the old locations. I would volunteer to do the
> moving.
> 
> What are your thoughts?

Deciding on documentation formats and places is something we've
generally been bad at. If you want to do the work, I say you get to pick
the technology. Think about how it will be maintained in the future: the
lower maintenance cost, the better. For example, please try to avoid
creating a new place where everybody has to create a new username and
password.

Maciej
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140416/70c05dde/attachment.asc>

From bwalton at opencsw.org  Fri Apr 18 20:10:16 2014
From: bwalton at opencsw.org (Ben Walton)
Date: Fri, 18 Apr 2014 19:10:16 +0100
Subject: New Board Formation
Message-ID: <CAP30j14nOnn4G2vdYLeiu=m_mJyAf5aAeju4TgRv5hFhj=RCFw@mail.gmail.com>

Hi All,

I'd like to congratulate Peter, Dago and Carsten in their election to
the board of OpenCSW. Their contributions and dedication are already
well known to the community and I have full confidence that they'll be
an excellent representation of what OpenCSW stands for.

I'll let them formalize the positions and make the announcement as
their first formal act.

Thanks
-Ben

From maciej at opencsw.org  Sat Apr 19 11:41:57 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sat, 19 Apr 2014 10:41:57 +0100
Subject: [board] New Board Formation
In-Reply-To: <CAP30j14nOnn4G2vdYLeiu=m_mJyAf5aAeju4TgRv5hFhj=RCFw@mail.gmail.com>
References: <CAP30j14nOnn4G2vdYLeiu=m_mJyAf5aAeju4TgRv5hFhj=RCFw@mail.gmail.com>
Message-ID: <CALtRa-7TEsJ5HEOYCFcRGDxk-nAwak3mffAVHPwQ_e_5m4529g@mail.gmail.com>

2014-04-18 19:10 GMT+01:00 Ben Walton <bwalton at opencsw.org>:
> I'd like to congratulate Peter, Dago and Carsten in their election to
> the board of OpenCSW. Their contributions and dedication are already
> well known to the community and I have full confidence that they'll be
> an excellent representation of what OpenCSW stands for.

Congratulations!

From maciej at opencsw.org  Sun Apr 20 22:48:50 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sun, 20 Apr 2014 21:48:50 +0100
Subject: Bugs in the package browser; user names are mismatched
Message-ID: <CALtRa-65XVsTWktTiVdQXYqFewX_Wb0FCOx7QQ+6dz3=eWkMsw@mail.gmail.com>

Let's take Guillaume Rousse for instance. His packages are tagged
correctly, but there's something wrong on the website, because you
can't see the link to the maintainer's page:

http://www.opencsw.org/packages/fi_agent/

"Last uploaded by" is empty.

There's a page with a truncated user name:
http://www.opencsw.org/maintainers/guillomo/

...but there are no packages linked to it.

A similar situation happens with Victor Hooi, I'm sure there are others.

Is anyone aware of the problem?

Maciej

From dam at opencsw.org  Mon Apr 21 23:26:41 2014
From: dam at opencsw.org (Dagobert Michelsen)
Date: Mon, 21 Apr 2014 23:26:41 +0200
Subject: Your script
Message-ID: <A5466004-DC62-44D4-80B0-F6A1E8518EA1@opencsw.org>

Hi Rafi,

I noticed you are working on a changelog edit script. This is superuseful
and I wanted to have that for a very long time. I also keep thinking that it
would be nice to have a dedicated place for the changelog per package in an
easy-to-parse format (probably in ReST/Markdown?) which could be displayed
on pkgutil -u (store the previous changelog before removal and diff to the
newly installed one). Also Catalog changediffs could be generated that way.

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: smime.p7s
Type: application/pkcs7-signature
Size: 2418 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140421/aa484399/attachment.p7s>

From maciej at opencsw.org  Mon Apr 21 23:43:43 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Mon, 21 Apr 2014 22:43:43 +0100
Subject: Your script
In-Reply-To: <A5466004-DC62-44D4-80B0-F6A1E8518EA1@opencsw.org>
References: <A5466004-DC62-44D4-80B0-F6A1E8518EA1@opencsw.org>
Message-ID: <CALtRa-7UqZ+sFqrhPLT6M5Qd99HEL6v2mMX-sO-MQinERmoZyA@mail.gmail.com>

2014-04-21 22:26 GMT+01:00 Dagobert Michelsen <dam at opencsw.org>:
> I also keep thinking that it
> would be nice to have a dedicated place for the changelog per package in an
> easy-to-parse format (probably in ReST/Markdown?) which could be displayed
> on pkgutil -u (store the previous changelog before removal and diff to the
> newly installed one). Also Catalog changediffs could be generated that way.

I'm not super familiar with the changelog files, but they seem to have
a well defined format, so we should first look if there already are
parsers. So it might be fine to keep the regular changelog format, and
use a parser whenever we want to process the data. Checking if the
changelog syntax is correct can be part of package checking.

I also had this idea that instead of using VERSION in the Makefile, we
could take the latest version from changelog:

VERSION = $(call extract_version_from_changelog)

The idea is not mine, it's stolen from Debian, as usual. :)

Maciej

From yann at pleiades.fr.eu.org  Tue Apr 22 00:13:01 2014
From: yann at pleiades.fr.eu.org (Yann Rouillard)
Date: Tue, 22 Apr 2014 00:13:01 +0200
Subject: ld: fatal: file /lib/libc.so: version 'SUNW_1.22.5' is unavailable
In-Reply-To: <C096AEA0-11DC-4725-8DCE-F37463F8F6FC@opencsw.org>
References: <52FD0066.5000203@opencsw.org>
	<C096AEA0-11DC-4725-8DCE-F37463F8F6FC@opencsw.org>
Message-ID: <CAF2fwsemdEb0_0OF6HKZtBmoZJQeHL4Ju0H3TEFs89mPDw55KQ@mail.gmail.com>

Hi,

I am also running into this problem with sasl and I wonder why we couldn't
just raise the minimal libc version interface to 1.22.5 ?
It has been introduced in Solaris 10 update 8 which is nearly 5 years old
now. What do you think ?

Yann



2014-02-16 13:39 GMT+01:00 Dagobert Michelsen <dam at opencsw.org>:

> Hi Jake,
>
> Am 13.02.2014 um 18:27 schrieb Jake Goerzen <jgoerzen at opencsw.org>:
>
>   Since the last update to mysql packages I can no longer build dovecot
> anymore, configure fails with:
>
> checking for mysql_config... mysql_config
> checking for mysql_init in -lmysqlclient... no
> configure: error: Can't build with MySQL support: libmysqlclient not found
> /home/jgoerzen/opencsw/.buildsys/v2/gar//gar.lib.mk:835: recipe for
> target
> 'configure-work/solaris10-i386/build-isa-pentium_pro/dovecot-2.2.10/configure'
> failedgmake[1]: ***
> [configure-work/solaris10-i386/build-isa-pentium_pro/dovecot-2.2.10/configure]
> Error 1
>
>
> Looking In config.log the error encountered is:
> ld: fatal: file /lib/libc.so: version 'SUNW_1.22.5' is unavailable
>
> configure:23474: checking for mysql_init in -lmysqlclient
> configure:23499: /opt/SUNWspro/bin/cc -o conftest -xO3 -m32
> -xarch=pentium_pro -xchip=pentium_pro -I/opt/csw/include
> -I/opt/csw/include/mysql -I/opt/csw/include/postgresql -I/opt/csw/include
> -m32 -xarch=pentium_pro -xchip=pentium_pro -L/opt/csw/lib conftest.c
> -lmysqlclient  -lrt -lnsl -lsocket  -lsendfile -L/opt/csw/lib
> -lmysqlclient  -lsocket -lz -lnsl -lrt -lssl -lcrypto -lz -lm >&5
> "conftest.c", line 155: warning: statement not reached
> ld: fatal: file /lib/libc.so: version 'SUNW_1.22.5' is unavailable:
>         required by file /opt/csw/lib/libmysqlclient.so
> ld: fatal: file processing errors. No output written to conftest
>
>
> I tried switching the compiler to GCC4 but configure still can't find or
> link -lmysqlclient  What could be the problem?
>
>
> The problem is that mysql actually needs the newer libc-version for
> getpagesize2() as reported in
>   https://www.opencsw.org/mantis/view.php?id=5137
> This is not related to GCC or Sun Studio. I suggest you disable the linker
> map forcing 1.22.5 in your Makefile with
>   # Disable linker map forcing SUNW_1.22.2 as the linked MySQL needs
> SUNW_1.22.5
>   LINKER_MAPS =
> After that everything sould work cleanly.
>
>
> 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/20140422/53f242a9/attachment.html>

From maciej at opencsw.org  Tue Apr 22 01:48:12 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Tue, 22 Apr 2014 00:48:12 +0100
Subject: Your script
In-Reply-To: <CALtRa-7UqZ+sFqrhPLT6M5Qd99HEL6v2mMX-sO-MQinERmoZyA@mail.gmail.com>
References: <A5466004-DC62-44D4-80B0-F6A1E8518EA1@opencsw.org>
	<CALtRa-7UqZ+sFqrhPLT6M5Qd99HEL6v2mMX-sO-MQinERmoZyA@mail.gmail.com>
Message-ID: <CALtRa-64rKWRb4NU979CRJ17q15E+_9Py7PUPMG6LAMogt+vsQ@mail.gmail.com>

2014-04-21 22:26 GMT+01:00 Rafael Ostertag <raos at opencsw.org>:
>    ./cswch create packagename 0.1 --log 'Initial release.'

I'm trying this.

packagename and version can be derived from the Makefile, maybe?

After running the tool, the changelog is not added to the svn repository.

maciej at unstable10s [unstable10s]:~/src/opencsw/pkg/fakeroot/trunk >
~/src/opencsw-gar/v2/bin/cswch create fakeroot 1.20 --log
"Garification, package split."
maciej at unstable10s [unstable10s]:~/src/opencsw/pkg/fakeroot/trunk > svn status
?       files/changelog.CSW


Maybe the tool could do that for me, or display a copypastable line?

From raos at opencsw.org  Tue Apr 22 07:51:49 2014
From: raos at opencsw.org (Rafael Ostertag)
Date: Tue, 22 Apr 2014 07:51:49 +0200
Subject: Your script
In-Reply-To: <CALtRa-64rKWRb4NU979CRJ17q15E+_9Py7PUPMG6LAMogt+vsQ@mail.gmail.com>
References: <A5466004-DC62-44D4-80B0-F6A1E8518EA1@opencsw.org>
	<CALtRa-7UqZ+sFqrhPLT6M5Qd99HEL6v2mMX-sO-MQinERmoZyA@mail.gmail.com>
	<CALtRa-64rKWRb4NU979CRJ17q15E+_9Py7PUPMG6LAMogt+vsQ@mail.gmail.com>
Message-ID: <20140422055149.GJ26613@bender.opencsw.org>

Hi Maciej

On Tue, Apr 22, 2014 at 12:48:12AM +0100, Maciej (Matchek) Blizi??ski wrote:
> 2014-04-21 22:26 GMT+01:00 Rafael Ostertag <raos at opencsw.org>:
> >    ./cswch create packagename 0.1 --log 'Initial release.'
> 
> I'm trying this.
> 
> packagename and version can be derived from the Makefile, maybe?

Hmm. But if we take the version to be used in the Makefile from the changelog,
the changelog cannot take the version from the Makefile, right?

You only have to give the package name on initial creation of the changelog.
After that, using 'new', it takes it from the existing changelog entries, so
you don't have to specify it explicitely. How about that?

> 
> After running the tool, the changelog is not added to the svn repository.
Yes. File that under 'not feature complete' :)

> 
> maciej at unstable10s [unstable10s]:~/src/opencsw/pkg/fakeroot/trunk >
> ~/src/opencsw-gar/v2/bin/cswch create fakeroot 1.20 --log
> "Garification, package split."
> maciej at unstable10s [unstable10s]:~/src/opencsw/pkg/fakeroot/trunk > svn status
> ?       files/changelog.CSW
> 
> 
> Maybe the tool could do that for me, or display a copypastable line?

My idea was, the tool being the interface to changelog. Providing a
copypastable line(s) breaks this rule, because then changelog is not under the
tool's control anymore (sort of).

Now, what if 'mgar newpkg' calls cswch with the proper arguments and adds
changelog.CSW to the repo?

cheers
rafi

From raos at opencsw.org  Tue Apr 22 08:00:19 2014
From: raos at opencsw.org (Rafael Ostertag)
Date: Tue, 22 Apr 2014 08:00:19 +0200
Subject: Your script
In-Reply-To: <CALtRa-7UqZ+sFqrhPLT6M5Qd99HEL6v2mMX-sO-MQinERmoZyA@mail.gmail.com>
References: <A5466004-DC62-44D4-80B0-F6A1E8518EA1@opencsw.org>
	<CALtRa-7UqZ+sFqrhPLT6M5Qd99HEL6v2mMX-sO-MQinERmoZyA@mail.gmail.com>
Message-ID: <20140422060019.GK26613@bender.opencsw.org>

Hi
On Mon, Apr 21, 2014 at 10:43:43PM +0100, Maciej (Matchek) Blizi??ski wrote:
> 2014-04-21 22:26 GMT+01:00 Dagobert Michelsen <dam at opencsw.org>:
> > I also keep thinking that it
> > would be nice to have a dedicated place for the changelog per package in an
> > easy-to-parse format (probably in ReST/Markdown?) which could be displayed
> > on pkgutil -u (store the previous changelog before removal and diff to the
> > newly installed one). Also Catalog changediffs could be generated that way.
> 
> I'm not super familiar with the changelog files, but they seem to have
> a well defined format, so we should first look if there already are
> parsers. So it might be fine to keep the regular changelog format, and
> use a parser whenever we want to process the data. Checking if the
> changelog syntax is correct can be part of package checking.

There is a parser in cswch (nothing official, I hacked it together), which
tries to be compliant with [1]. So cswch has a pretty good idea of
changelog.CSW and it should be trivial to convert changelog.CSW into any other
format. Let me know what you need. 

> 
> I also had this idea that instead of using VERSION in the Makefile, we
> could take the latest version from changelog:
> 
> VERSION = $(call extract_version_from_changelog)

+1

cheers
rafi

[1] http://www.debian.org/doc/debian-policy/ch-source.html#s-dpkgchangelog

From dam at opencsw.org  Tue Apr 22 10:10:53 2014
From: dam at opencsw.org (dam)
Date: Tue, 22 Apr 2014 10:10:53 +0200
Subject: Removal of CSWruby18tk from CSWruby18 build
Message-ID: <4844e6ac71cacaf1a840f44b208fea04@opencsw.org>

Hi Yann,

I noticed you removed the generation of CSWruby18tk in the latest Ruby 
build
without changing anything else:
   
https://buildfarm.opencsw.org/source/diff/opencsw/csw/mgar/pkg/ruby18/trunk/Makefile?r2=%2Fopencsw%2Fcsw%2Fmgar%2Fpkg%2Fruby18%2Ftrunk%2FMakefile%4022978&r1=%2Fopencsw%2Fcsw%2Fmgar%2Fpkg%2Fruby18%2Ftrunk%2FMakefile%4019643
Is there a specific reason for this? Unfortunately I have a customer who 
uses this
and I am in need of restoring that in unstable if possible.


Best regards

   -- Dago

From maciej at opencsw.org  Tue Apr 22 11:23:41 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Tue, 22 Apr 2014 10:23:41 +0100
Subject: ld: fatal: use the -z help option for usage information
Message-ID: <CALtRa-5Vq0rW5v_0Zi8jKaOEWDY56LqSbd6qGA5jRWsK1sxjEg@mail.gmail.com>

I'm having problems building Python:

ld: fatal: use the -z help option for usage information

Compilation of all modules fails with this message. Has anyone seen
this before? I thought it was related to
https://sourceforge.net/apps/trac/gar/wiki/Mapfiles so I added:

LINKER_IGNORE =

But I'm still seeing the problem.

My work is committed:
~/opencsw/lang-python/python/branches/python-3.4

Do we have a standard solution for this?

Maciej

From maciej at opencsw.org  Tue Apr 22 11:27:10 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Tue, 22 Apr 2014 10:27:10 +0100
Subject: Your script
In-Reply-To: <20140422060019.GK26613@bender.opencsw.org>
References: <A5466004-DC62-44D4-80B0-F6A1E8518EA1@opencsw.org>
	<CALtRa-7UqZ+sFqrhPLT6M5Qd99HEL6v2mMX-sO-MQinERmoZyA@mail.gmail.com>
	<20140422060019.GK26613@bender.opencsw.org>
Message-ID: <CALtRa-4q12Zz1_1qWg3=d87Cvhyi_JBiDLcG85XAfk8tVU08QQ@mail.gmail.com>

2014-04-22 7:00 GMT+01:00 Rafael Ostertag <raos at opencsw.org>:
> There is a parser in cswch (nothing official, I hacked it together), which
> tries to be compliant with [1]. So cswch has a pretty good idea of
> changelog.CSW and it should be trivial to convert changelog.CSW into any other
> format. Let me know what you need.

How about using the Debian parser?

http://manpages.ubuntu.com/manpages/hardy/man1/dpkg-parsechangelog.1.html

I guess extracting the version is the first thing we want.

From raos at opencsw.org  Tue Apr 22 12:31:01 2014
From: raos at opencsw.org (Rafael Ostertag)
Date: Tue, 22 Apr 2014 12:31:01 +0200
Subject: Your script
In-Reply-To: <CALtRa-4q12Zz1_1qWg3=d87Cvhyi_JBiDLcG85XAfk8tVU08QQ@mail.gmail.com>
References: <A5466004-DC62-44D4-80B0-F6A1E8518EA1@opencsw.org>
	<CALtRa-7UqZ+sFqrhPLT6M5Qd99HEL6v2mMX-sO-MQinERmoZyA@mail.gmail.com>
	<20140422060019.GK26613@bender.opencsw.org>
	<CALtRa-4q12Zz1_1qWg3=d87Cvhyi_JBiDLcG85XAfk8tVU08QQ@mail.gmail.com>
Message-ID: <20140422103101.GL26613@bender.opencsw.org>

Hi Maciej

On Tue, Apr 22, 2014 at 10:27:10AM +0100, Maciej (Matchek) Blizi??ski wrote:
> 2014-04-22 7:00 GMT+01:00 Rafael Ostertag <raos at opencsw.org>:
> > There is a parser in cswch (nothing official, I hacked it together), which
> > tries to be compliant with [1]. So cswch has a pretty good idea of
> > changelog.CSW and it should be trivial to convert changelog.CSW into any other
> > format. Let me know what you need.
> 
> How about using the Debian parser?
> 
> http://manpages.ubuntu.com/manpages/hardy/man1/dpkg-parsechangelog.1.html

I'll have a look at it and see how it fits in.

> 
> I guess extracting the version is the first thing we want.

It's in r23465:

 ./cswch version

will print the version found in the first change log entry, i.e. the top most.

cheers
rafi

From maciej at opencsw.org  Tue Apr 22 12:33:49 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Tue, 22 Apr 2014 11:33:49 +0100
Subject: ld: fatal: use the -z help option for usage information
In-Reply-To: <CALtRa-5Vq0rW5v_0Zi8jKaOEWDY56LqSbd6qGA5jRWsK1sxjEg@mail.gmail.com>
References: <CALtRa-5Vq0rW5v_0Zi8jKaOEWDY56LqSbd6qGA5jRWsK1sxjEg@mail.gmail.com>
Message-ID: <CALtRa-7dAn2rfWdpfJtPVMW5DiHPV9JPwRC_LRZRdwXPnJJLzA@mail.gmail.com>

The failing invocation is:

(cd work/solaris10-sparc/build-isa-sparcv8plus/Python-3.4.0/; \
ld -mcpu=v9 -Wa,-xarch=v8plus -L/opt/csw/lib/ffi -L/opt/csw/lib
-lsocket -lresolv -lrt -mcpu=v9 -Wa,-xarch=v8plus -L/opt/csw/lib/ffi
-L/opt/csw/lib -lsocket -lresolv -lrt -mcpu=v9 -Wa,-xarch=v8plus
-L/opt/csw/lib/ffi -L/opt/csw/lib -lsocket -lresolv -lrt -g -mcpu=v9
-Wa,-xarch=v8plus -D_XPG5 -I/opt/csw/include
build/temp.solaris-2.10-sun4v.32bit-3.4/home/maciej/src/opencsw/pkg/lang-python/python/branches/python-3.4/work/solaris10-sparc/build-isa-sparcv8plus/Python-3.4.0/Modules/_ctypes/_ctypes_test.o
-L. -L/opt/csw/lib/ffi -L/opt/csw/lib -lpython3.4m -o
build/lib.solaris-2.10-sun4v.32bit-3.4/_ctypes_test.so)

And the error message is:

ld: warning: option -c appears more than once, first setting taken
ld: warning: option -c appears more than once, first setting taken
ld: fatal: unrecognized option '-g'
ld: warning: option -c appears more than once, first setting taken
debug: warning: unrecognized debug option (try help): _XPG5
debug:
debug: Solaris Linkers: 5.10-1.1518
debug:
ld: fatal: use the -z help option for usage information

...but the -z flag isn't even there. I also don't know what's up with
the -g flag, I can see it in "mgar modenv" output.

Maciej

From raos at opencsw.org  Tue Apr 22 12:45:48 2014
From: raos at opencsw.org (Rafael Ostertag)
Date: Tue, 22 Apr 2014 12:45:48 +0200
Subject: ld: fatal: use the -z help option for usage information
In-Reply-To: <CALtRa-7dAn2rfWdpfJtPVMW5DiHPV9JPwRC_LRZRdwXPnJJLzA@mail.gmail.com>
References: <CALtRa-5Vq0rW5v_0Zi8jKaOEWDY56LqSbd6qGA5jRWsK1sxjEg@mail.gmail.com>
	<CALtRa-7dAn2rfWdpfJtPVMW5DiHPV9JPwRC_LRZRdwXPnJJLzA@mail.gmail.com>
Message-ID: <20140422104548.GM26613@bender.opencsw.org>

Hi Maciej

On Tue, Apr 22, 2014 at 11:33:49AM +0100, Maciej (Matchek) Blizi??ski wrote:
> The failing invocation is:
> 
> (cd work/solaris10-sparc/build-isa-sparcv8plus/Python-3.4.0/; \
> ld -mcpu=v9 -Wa,-xarch=v8plus -L/opt/csw/lib/ffi -L/opt/csw/lib
> -lsocket -lresolv -lrt -mcpu=v9 -Wa,-xarch=v8plus -L/opt/csw/lib/ffi
> -L/opt/csw/lib -lsocket -lresolv -lrt -mcpu=v9 -Wa,-xarch=v8plus
> -L/opt/csw/lib/ffi -L/opt/csw/lib -lsocket -lresolv -lrt -g -mcpu=v9
> -Wa,-xarch=v8plus -D_XPG5 -I/opt/csw/include
> build/temp.solaris-2.10-sun4v.32bit-3.4/home/maciej/src/opencsw/pkg/lang-python/python/branches/python-3.4/work/solaris10-sparc/build-isa-sparcv8plus/Python-3.4.0/Modules/_ctypes/_ctypes_test.o
> -L. -L/opt/csw/lib/ffi -L/opt/csw/lib -lpython3.4m -o
> build/lib.solaris-2.10-sun4v.32bit-3.4/_ctypes_test.so)
> 
> And the error message is:
> 
> ld: warning: option -c appears more than once, first setting taken
> ld: warning: option -c appears more than once, first setting taken
> ld: fatal: unrecognized option '-g'
> ld: warning: option -c appears more than once, first setting taken
> debug: warning: unrecognized debug option (try help): _XPG5
> debug:
> debug: Solaris Linkers: 5.10-1.1518
> debug:
> ld: fatal: use the -z help option for usage information
> 
> ...but the -z flag isn't even there. I also don't know what's up with
> the -g flag, I can see it in "mgar modenv" output.

Apparently, you can think of `ld -z help' as `ld --help'. To me, it looks like
a lot of compiler flags have leaked into the ld command line arguments

Just for the heck of it, what happens if you replace `ld' by `cc' and run it manually?

cheers
rafi

From dam at opencsw.org  Tue Apr 22 13:24:30 2014
From: dam at opencsw.org (dam)
Date: Tue, 22 Apr 2014 13:24:30 +0200
Subject: Your script
In-Reply-To: <20140422060019.GK26613@bender.opencsw.org>
References: <A5466004-DC62-44D4-80B0-F6A1E8518EA1@opencsw.org>
	<CALtRa-7UqZ+sFqrhPLT6M5Qd99HEL6v2mMX-sO-MQinERmoZyA@mail.gmail.com>
	<20140422060019.GK26613@bender.opencsw.org>
Message-ID: <838709a7f76f69f65bda5484e4b67e6b@opencsw.org>

Hi Rafi,

Am 2014-04-22 08:00, schrieb Rafael Ostertag:
> On Mon, Apr 21, 2014 at 10:43:43PM +0100, Maciej (Matchek) Blizi??ski 
> wrote:
>> 2014-04-21 22:26 GMT+01:00 Dagobert Michelsen <dam at opencsw.org>:
>> > I also keep thinking that it
>> > would be nice to have a dedicated place for the changelog per package in an
>> > easy-to-parse format (probably in ReST/Markdown?) which could be displayed
>> > on pkgutil -u (store the previous changelog before removal and diff to the
>> > newly installed one). Also Catalog changediffs could be generated that way.
>> 
>> I'm not super familiar with the changelog files, but they seem to have
>> a well defined format, so we should first look if there already are
>> parsers. So it might be fine to keep the regular changelog format, and
>> use a parser whenever we want to process the data. Checking if the
>> changelog syntax is correct can be part of package checking.
> 
> There is a parser in cswch (nothing official, I hacked it together), 
> which
> tries to be compliant with [1]. So cswch has a pretty good idea of
> changelog.CSW and it should be trivial to convert changelog.CSW into 
> any other
> format. Let me know what you need.
> 
>> 
>> I also had this idea that instead of using VERSION in the Makefile, we
>> could take the latest version from changelog:
>> 
>> VERSION = $(call extract_version_from_changelog)
> 
> +1
> 
> [1] 
> http://www.debian.org/doc/debian-policy/ch-source.html#s-dpkgchangelog

I don't think that is a good idea for two reasons:

1. The application version (e.g. 1.2) is tightly coupled to DISTFILE and
    updated only on version bumps.
2. The REV is calculated from the date which is good IMHO

The Changelog should IMHO contain high-level descriptions of changes, 
like
"Switch from OpenSSL to GnuTLS" accommodated by a date when the change 
was
done. This may not be related to package rebuilds.
What may be a good idea is to retrieve the REV timestamp from the change 
log,
but again rebuilding may result in binary-different packages with the 
same
revstamp.

One related thing: It would be nice if we could enable the catalog 
versions
on the webpage and have a "svn diff" button between REVs to show the 
Makefile
diffs as calculated by OpenGrok.


Best regards

   -- Dago

From yann at pleiades.fr.eu.org  Tue Apr 22 15:09:58 2014
From: yann at pleiades.fr.eu.org (Yann Rouillard)
Date: Tue, 22 Apr 2014 15:09:58 +0200
Subject: Removal of CSWruby18tk from CSWruby18 build
In-Reply-To: <4844e6ac71cacaf1a840f44b208fea04@opencsw.org>
References: <4844e6ac71cacaf1a840f44b208fea04@opencsw.org>
Message-ID: <CAF2fwscRoLAZy4CRwfE2hYiALPMWEzRLxNL320cysaMShF6w-A@mail.gmail.com>

Hi Dago,

The rubytk doesn't compile anymore because pthread was enabled in the
tcl/tk package.
Either I enable pthread in ruby or it is disabled in tcl/tk.

I didn't enable pthread in ruby as I don't know enough the impact of such a
modification
and I choose to release a new ruby package relinked against libssl because
it doesn't change
the current situation. The rubytk package is still present
http://www.opencsw.org/packages/CSWruby18-tk/ and
if it has a problem, it has been present since tcl/tk was compiled with
phtread support.

I talked about it with you on IRC:

14:03 < chninkel> Dagobert: other question: did you change the
configuration option for the tcl/tk package ?
14:03 < chninkel> more precisely: did you added "--enable-pthreads" or
something like that ?
14:04 <@Dagobert> Maybe, I reworked them a long time ago together with some
other guy
14:04 <@Dagobert> Sorry, can't remember
14:04 <@Dagobert> Mmmhh.... CONFIGURE_ARGS += --enable-threads
14:04 <@Dagobert> Probably.
14:05 < chninkel> this was probably not good for the rubytk package
14:05 <@Dagobert> *Sigh**
14:06 < chninkel> I am not sure if I should enable pthreads in ruby, ask to
disable threads in tcl/tk or drop rubytk


What does your customer need exactly ? The ruby18_tk package is still
present in unstable.

I could be on IRC tonight, we could talk about it.


Yann



2014-04-22 10:10 GMT+02:00 dam <dam at opencsw.org>:

> Hi Yann,
>
> I noticed you removed the generation of CSWruby18tk in the latest Ruby
> build
> without changing anything else:
>   https://buildfarm.opencsw.org/source/diff/opencsw/csw/mgar/
> pkg/ruby18/trunk/Makefile?r2=%2Fopencsw%2Fcsw%2Fmgar%2Fpkg%
> 2Fruby18%2Ftrunk%2FMakefile%4022978&r1=%2Fopencsw%2Fcsw%
> 2Fmgar%2Fpkg%2Fruby18%2Ftrunk%2FMakefile%4019643
> Is there a specific reason for this? Unfortunately I have a customer who
> uses this
> and I am in need of restoring that in unstable if possible.
>
>
> Best regards
>
>   -- Dago
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140422/fd412123/attachment.html>

From raos at opencsw.org  Tue Apr 22 15:19:43 2014
From: raos at opencsw.org (Rafael Ostertag)
Date: Tue, 22 Apr 2014 15:19:43 +0200
Subject: Your script
In-Reply-To: <838709a7f76f69f65bda5484e4b67e6b@opencsw.org>
References: <A5466004-DC62-44D4-80B0-F6A1E8518EA1@opencsw.org>
	<CALtRa-7UqZ+sFqrhPLT6M5Qd99HEL6v2mMX-sO-MQinERmoZyA@mail.gmail.com>
	<20140422060019.GK26613@bender.opencsw.org>
	<838709a7f76f69f65bda5484e4b67e6b@opencsw.org>
Message-ID: <20140422131943.GN26613@bender.opencsw.org>

Hi Dago
On Tue, Apr 22, 2014 at 01:24:30PM +0200, dam wrote:
> Hi Rafi,
> 
> Am 2014-04-22 08:00, schrieb Rafael Ostertag:
> >On Mon, Apr 21, 2014 at 10:43:43PM +0100, Maciej (Matchek) Blizi??ski
> >wrote:
> >>2014-04-21 22:26 GMT+01:00 Dagobert Michelsen <dam at opencsw.org>:
> >>> I also keep thinking that it
> >>> would be nice to have a dedicated place for the changelog per package in an
> >>> easy-to-parse format (probably in ReST/Markdown?) which could be displayed
> >>> on pkgutil -u (store the previous changelog before removal and diff to the
> >>> newly installed one). Also Catalog changediffs could be generated that way.
> >>
> >>I'm not super familiar with the changelog files, but they seem to have
> >>a well defined format, so we should first look if there already are
> >>parsers. So it might be fine to keep the regular changelog format, and
> >>use a parser whenever we want to process the data. Checking if the
> >>changelog syntax is correct can be part of package checking.
> >
> >There is a parser in cswch (nothing official, I hacked it together), which
> >tries to be compliant with [1]. So cswch has a pretty good idea of
> >changelog.CSW and it should be trivial to convert changelog.CSW into any
> >other
> >format. Let me know what you need.
> >
> >>
> >>I also had this idea that instead of using VERSION in the Makefile, we
> >>could take the latest version from changelog:
> >>
> >>VERSION = $(call extract_version_from_changelog)
> >
> >+1
> >
> >[1] http://www.debian.org/doc/debian-policy/ch-source.html#s-dpkgchangelog
> 
> I don't think that is a good idea for two reasons:
> 
> 1. The application version (e.g. 1.2) is tightly coupled to DISTFILE and
>    updated only on version bumps.
> 2. The REV is calculated from the date which is good IMHO
> 
> The Changelog should IMHO contain high-level descriptions of changes, like
> "Switch from OpenSSL to GnuTLS" accommodated by a date when the change was
> done.

I don't see a contradiction. Let's see how a changelog might look like. Upon
initial CSW package creation it might look like this:

 foo (0.2,REV=2014.01.01)

   * Initial packaging for OpenCSW.

  -- Rafael Ostertag  ...


Then, a new release comes out:

 foo (0.3,REV=2014.04.01)

   * Upstream graced us with a new release.

  -- Rafael Ostertag ...

 foo (0.2,REV=2014.04.01)

   * Initial packaging for OpenCSW.

  -- Rafael Ostertag  ...


A respin with different configuration options, e.g. the 'Switch from OpenSSL to
GnuTLS', would lead to:

 foo (0.3,REV=2014.04.08)

   * Switch to GnuTLS, because it has no heart.

  -- Rafael Ostertag ...

 foo (0.3,REV=2014.04.01)

   * Upstream graced us with a new release.

  -- Rafael Ostertag ...

 foo (0.2,REV=2014.01.01)

   * Initial packaging for OpenCSW.

  -- Rafael Ostertag  ...


>From my POV, those were all high level descriptions. And they give the user a
clue what has changed. Low level stuff will be in svn or the recipe itself.
Correct me if I'm wrong, or maybe I don't get the point of the changelog.CSW.


> This may not be related to package rebuilds.
Can you elaborate on this? What type of change in the build recipe does not
require a respin? There is none on top of my head ;)

> What may be a good idea is to retrieve the REV timestamp from the change
> log,
> but again rebuilding may result in binary-different packages with the same
> revstamp.
Yes, but is that really of any concern to the changelog? This happens with or
without changelog.

cheers
rafi

> 
> One related thing: It would be nice if we could enable the catalog versions
> on the webpage and have a "svn diff" button between REVs to show the
> Makefile
> diffs as calculated by OpenGrok.
> 
> 
> Best regards
> 
>   -- Dago
> 

From raos at opencsw.org  Tue Apr 22 17:17:46 2014
From: raos at opencsw.org (Rafael Ostertag)
Date: Tue, 22 Apr 2014 17:17:46 +0200
Subject: ld: fatal: use the -z help option for usage information
In-Reply-To: <CALtRa-7dAn2rfWdpfJtPVMW5DiHPV9JPwRC_LRZRdwXPnJJLzA@mail.gmail.com>
References: <CALtRa-5Vq0rW5v_0Zi8jKaOEWDY56LqSbd6qGA5jRWsK1sxjEg@mail.gmail.com>
	<CALtRa-7dAn2rfWdpfJtPVMW5DiHPV9JPwRC_LRZRdwXPnJJLzA@mail.gmail.com>
Message-ID: <20140422151746.GO26613@bender.opencsw.org>

Hi Maciej

On Tue, Apr 22, 2014 at 11:33:49AM +0100, Maciej (Matchek) Blizi??ski wrote:
> The failing invocation is:
> 
> (cd work/solaris10-sparc/build-isa-sparcv8plus/Python-3.4.0/; \
> ld -mcpu=v9 -Wa,-xarch=v8plus -L/opt/csw/lib/ffi -L/opt/csw/lib
> -lsocket -lresolv -lrt -mcpu=v9 -Wa,-xarch=v8plus -L/opt/csw/lib/ffi
> -L/opt/csw/lib -lsocket -lresolv -lrt -mcpu=v9 -Wa,-xarch=v8plus
> -L/opt/csw/lib/ffi -L/opt/csw/lib -lsocket -lresolv -lrt -g -mcpu=v9
> -Wa,-xarch=v8plus -D_XPG5 -I/opt/csw/include
> build/temp.solaris-2.10-sun4v.32bit-3.4/home/maciej/src/opencsw/pkg/lang-python/python/branches/python-3.4/work/solaris10-sparc/build-isa-sparcv8plus/Python-3.4.0/Modules/_ctypes/_ctypes_test.o
> -L. -L/opt/csw/lib/ffi -L/opt/csw/lib -lpython3.4m -o
> build/lib.solaris-2.10-sun4v.32bit-3.4/_ctypes_test.so)
> 

Is there a particular reason, you set 

 MACHDEP = $(ISA)
 EXTRA_CONFIGURE_EXPORTS += MACHDEP

By doing so, some internal configure variables won't be set which in turn lead
to Makefile using `ld' instead of `gcc'. When MACHDEP is not set, the configure
output looks like

 [...]
 checking LDSHARED... $(CC) -shared
 checking CCSHARED... -fPIC
 checking LINKFORSHARED... 
 checking CFLAGSFORSHARED... $(CCSHARED)
 [...]

which is a good thing. When MACHDEP is set, it looks more like

 [...]
 checking LDSHARED... ld
 checking CCSHARED... 
 checking LINKFORSHARED... 
 checking CFLAGSFORSHARED... 
 [...]

which is bad.

Specifically, setting MACHDEP manually inhibits $ac_sys_system, and
$ac_sys_release to be set, which are used all over the place as quick peek in
configure.ac reveals. I can't tell if that's a bug or not, though.

HTH
rafi

From maciej at opencsw.org  Tue Apr 22 17:54:26 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Tue, 22 Apr 2014 16:54:26 +0100
Subject: ld: fatal: use the -z help option for usage information
In-Reply-To: <20140422151746.GO26613@bender.opencsw.org>
References: <CALtRa-5Vq0rW5v_0Zi8jKaOEWDY56LqSbd6qGA5jRWsK1sxjEg@mail.gmail.com>
	<CALtRa-7dAn2rfWdpfJtPVMW5DiHPV9JPwRC_LRZRdwXPnJJLzA@mail.gmail.com>
	<20140422151746.GO26613@bender.opencsw.org>
Message-ID: <CALtRa-5Mf3+mmiryoE-Z8s1GXMPn9VBRFCKTDWyus1RWFDWLNw@mail.gmail.com>

2014-04-22 16:17 GMT+01:00 Rafael Ostertag <raos at opencsw.org>:
> Is there a particular reason, you set
>
>  MACHDEP = $(ISA)
>  EXTRA_CONFIGURE_EXPORTS += MACHDEP
>
> By doing so, some internal configure variables won't be set which in turn lead
> to Makefile using `ld' instead of `gcc'.

Hm, ok. I'm trying to work around http://bugs.python.org/issue18083
and modify paths to make the architecture dependent. MACHDEP is
probably a wrong approach though. I'd like to do what they suggest in
the bug report in python.org, but I don't know yet how to do it.

Maciej

From dam at opencsw.org  Tue Apr 22 18:29:31 2014
From: dam at opencsw.org (Dagobert Michelsen)
Date: Tue, 22 Apr 2014 18:29:31 +0200
Subject: Removal of CSWruby18tk from CSWruby18 build
In-Reply-To: <CAF2fwscRoLAZy4CRwfE2hYiALPMWEzRLxNL320cysaMShF6w-A@mail.gmail.com>
References: <4844e6ac71cacaf1a840f44b208fea04@opencsw.org>
	<CAF2fwscRoLAZy4CRwfE2hYiALPMWEzRLxNL320cysaMShF6w-A@mail.gmail.com>
Message-ID: <1565B0EC-A78A-48C6-B9EF-57E505C913A8@opencsw.org>

Hi Yann,

Am 22.04.2014 um 15:09 schrieb Yann Rouillard <yann at pleiades.fr.eu.org>:
> The rubytk doesn't compile anymore because pthread was enabled in the tcl/tk package.
> Either I enable pthread in ruby or it is disabled in tcl/tk.
> 
> I didn't enable pthread in ruby as I don't know enough the impact of such a modification
> and I choose to release a new ruby package relinked against libssl because it doesn't change
> the current situation. The rubytk package is still present http://www.opencsw.org/packages/CSWruby18-tk/ and
> if it has a problem, it has been present since tcl/tk was compiled with phtread support.
> 
> I talked about it with you on IRC:
> 
> 14:03 < chninkel> Dagobert: other question: did you change the configuration option for the tcl/tk package ?
> 14:03 < chninkel> more precisely: did you added "--enable-pthreads" or something like that ?
> 14:04 <@Dagobert> Maybe, I reworked them a long time ago together with some other guy
> 14:04 <@Dagobert> Sorry, can't remember
> 14:04 <@Dagobert> Mmmhh.... CONFIGURE_ARGS += --enable-threads
> 14:04 <@Dagobert> Probably.
> 14:05 < chninkel> this was probably not good for the rubytk package
> 14:05 <@Dagobert> *Sigh**
> 14:06 < chninkel> I am not sure if I should enable pthreads in ruby, ask to disable threads in tcl/tk or drop rubytk
> 
> 
> What does your customer need exactly ? The ruby18_tk package is still present in unstable.
> 
> I could be on IRC tonight, we could talk about it.


I remembered and also figured it out what to do.

The existing package does not work any more with some unresolved symbols.

The RubyTk requires pthreads:
  https://blogs.oracle.com/prashant/entry/ruby_and_enable_pthreads
enable pthreads is 30-50% down in performance on Ruby, solution is to use
this patch which disables switching ucontext with enabled pthreads:
  http://timetobleed.com/fix-a-bug-in-rubys-configurein-and-get-a-30-performance-boost/

I?ll add that, respin, test and push.


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: smime.p7s
Type: application/pkcs7-signature
Size: 2418 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140422/891d2392/attachment-0001.p7s>

From dam at opencsw.org  Tue Apr 22 18:36:15 2014
From: dam at opencsw.org (Dagobert Michelsen)
Date: Tue, 22 Apr 2014 18:36:15 +0200
Subject: Your script
In-Reply-To: <20140422131943.GN26613@bender.opencsw.org>
References: <A5466004-DC62-44D4-80B0-F6A1E8518EA1@opencsw.org>
	<CALtRa-7UqZ+sFqrhPLT6M5Qd99HEL6v2mMX-sO-MQinERmoZyA@mail.gmail.com>
	<20140422060019.GK26613@bender.opencsw.org>
	<838709a7f76f69f65bda5484e4b67e6b@opencsw.org>
	<20140422131943.GN26613@bender.opencsw.org>
Message-ID: <A97BF8C7-FA6B-40E9-A40D-A3E554432C58@opencsw.org>

Hi Rafi,

Am 22.04.2014 um 15:19 schrieb Rafael Ostertag <raos at opencsw.org>:

> Hi Dago
> On Tue, Apr 22, 2014 at 01:24:30PM +0200, dam wrote:
>> Hi Rafi,
>> 
>> Am 2014-04-22 08:00, schrieb Rafael Ostertag:
>>> On Mon, Apr 21, 2014 at 10:43:43PM +0100, Maciej (Matchek) Blizi??ski
>>> wrote:
>>>> 2014-04-21 22:26 GMT+01:00 Dagobert Michelsen <dam at opencsw.org>:
>>>>> I also keep thinking that it
>>>>> would be nice to have a dedicated place for the changelog per package in an
>>>>> easy-to-parse format (probably in ReST/Markdown?) which could be displayed
>>>>> on pkgutil -u (store the previous changelog before removal and diff to the
>>>>> newly installed one). Also Catalog changediffs could be generated that way.
>>>> 
>>>> I'm not super familiar with the changelog files, but they seem to have
>>>> a well defined format, so we should first look if there already are
>>>> parsers. So it might be fine to keep the regular changelog format, and
>>>> use a parser whenever we want to process the data. Checking if the
>>>> changelog syntax is correct can be part of package checking.
>>> 
>>> There is a parser in cswch (nothing official, I hacked it together), which
>>> tries to be compliant with [1]. So cswch has a pretty good idea of
>>> changelog.CSW and it should be trivial to convert changelog.CSW into any
>>> other
>>> format. Let me know what you need.
>>> 
>>>> 
>>>> I also had this idea that instead of using VERSION in the Makefile, we
>>>> could take the latest version from changelog:
>>>> 
>>>> VERSION = $(call extract_version_from_changelog)
>>> 
>>> +1
>>> 
>>> [1] http://www.debian.org/doc/debian-policy/ch-source.html#s-dpkgchangelog
>> 
>> I don't think that is a good idea for two reasons:
>> 
>> 1. The application version (e.g. 1.2) is tightly coupled to DISTFILE and
>>   updated only on version bumps.
>> 2. The REV is calculated from the date which is good IMHO
>> 
>> The Changelog should IMHO contain high-level descriptions of changes, like
>> "Switch from OpenSSL to GnuTLS" accommodated by a date when the change was
>> done.
> 
> I don't see a contradiction. Let's see how a changelog might look like. Upon
> initial CSW package creation it might look like this:
> 
> foo (0.2,REV=2014.01.01)
> 
>   * Initial packaging for OpenCSW.
> 
>  -- Rafael Ostertag  ?

I was more thinking of

foo (2004-06-14T23:34:30)

  * Initial packaging

 -- Rafael Ostertag ...

> From my POV, those were all high level descriptions. And they give the user a
> clue what has changed. Low level stuff will be in svn or the recipe itself.
> Correct me if I'm wrong, or maybe I don't get the point of the changelog.CSW.

My point was that not version/REV should be in the timemark, but just a real, precise
time, like ISO8601

>> This may not be related to package rebuilds.
> Can you elaborate on this? What type of change in the build recipe does not
> require a respin? There is none on top of my head ;)

Because it is progress. The Changelog is for me some documentation of continuous
work which documents larger chunks than a commit but less then a release of the
package.

>> What may be a good idea is to retrieve the REV timestamp from the change
>> log,
>> but again rebuilding may result in binary-different packages with the same
>> revstamp.
> Yes, but is that really of any concern to the changelog? This happens with or
> without changelog.

Having the same format in the changelog is IMHO confusing as it suggests that
a package with the version and REV actually exists/existed.


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: smime.p7s
Type: application/pkcs7-signature
Size: 2418 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140422/ac583638/attachment.p7s>

From raos at opencsw.org  Tue Apr 22 19:36:37 2014
From: raos at opencsw.org (Rafael Ostertag)
Date: Tue, 22 Apr 2014 19:36:37 +0200
Subject: Your script
In-Reply-To: <A97BF8C7-FA6B-40E9-A40D-A3E554432C58@opencsw.org>
References: <A5466004-DC62-44D4-80B0-F6A1E8518EA1@opencsw.org>
	<CALtRa-7UqZ+sFqrhPLT6M5Qd99HEL6v2mMX-sO-MQinERmoZyA@mail.gmail.com>
	<20140422060019.GK26613@bender.opencsw.org>
	<838709a7f76f69f65bda5484e4b67e6b@opencsw.org>
	<20140422131943.GN26613@bender.opencsw.org>
	<A97BF8C7-FA6B-40E9-A40D-A3E554432C58@opencsw.org>
Message-ID: <20140422173637.GP26613@bender.opencsw.org>

Hi Dago

On Tue, Apr 22, 2014 at 06:36:15PM +0200, Dagobert Michelsen wrote:
> Hi Rafi,
> 
> Am 22.04.2014 um 15:19 schrieb Rafael Ostertag <raos at opencsw.org>:
> >>>> 
> >>>> I also had this idea that instead of using VERSION in the Makefile, we
> >>>> could take the latest version from changelog:
> >>>> 
> >>>> VERSION = $(call extract_version_from_changelog)
> >>> 
> >>> +1
> >>> 
> >>> [1] http://www.debian.org/doc/debian-policy/ch-source.html#s-dpkgchangelog
> >> 
> >> I don't think that is a good idea for two reasons:
> >> 
> >> 1. The application version (e.g. 1.2) is tightly coupled to DISTFILE and
> >>   updated only on version bumps.
> >> 2. The REV is calculated from the date which is good IMHO
> >> 
> >> The Changelog should IMHO contain high-level descriptions of changes, like
> >> "Switch from OpenSSL to GnuTLS" accommodated by a date when the change was
> >> done.
> > 
> > I don't see a contradiction. Let's see how a changelog might look like. Upon
> > initial CSW package creation it might look like this:
> > 
> > foo (0.2,REV=2014.01.01)
> > 
> >   * Initial packaging for OpenCSW.
> > 
> >  -- Rafael Ostertag  ?
> 
> I was more thinking of
> 
> foo (2004-06-14T23:34:30)
> 
>   * Initial packaging
> 
>  -- Rafael Ostertag ...
> 
> > From my POV, those were all high level descriptions. And they give the user a
> > clue what has changed. Low level stuff will be in svn or the recipe itself.
> > Correct me if I'm wrong, or maybe I don't get the point of the changelog.CSW.
> 
> My point was that not version/REV should be in the timemark, but just a real, precise
> time, like ISO8601

I see.

> 
> >> This may not be related to package rebuilds.
> > Can you elaborate on this? What type of change in the build recipe does not
> > require a respin? There is none on top of my head ;)
> 
> Because it is progress. The Changelog is for me some documentation of continuous
> work which documents larger chunks than a commit but less then a release of the
> package.

Aha! Apparently we use the changelog.CSW differently. I use it more the way as
outlined throughout [1]. I guess we should reach a consensus about this OR I
make cswch support both styles. Maintainers could then decide which style they
want to use and, if they use the debian style, they might even use Maciej's

 VERSION = $(call extract_version_from_changelog)

> 
> >> What may be a good idea is to retrieve the REV timestamp from the change
> >> log,
> >> but again rebuilding may result in binary-different packages with the same
> >> revstamp.
> > Yes, but is that really of any concern to the changelog? This happens with or
> > without changelog.
> 
> Having the same format in the changelog is IMHO confusing as it suggests that
> a package with the version and REV actually exists/existed.

Indeed, but the way I use it, this is the case...

cheers
rafi

[1] http://www.debian.org/doc/manuals/maint-guide/

From maciej at opencsw.org  Tue Apr 22 19:43:42 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Tue, 22 Apr 2014 18:43:42 +0100
Subject: Your script
In-Reply-To: <20140422173637.GP26613@bender.opencsw.org>
References: <A5466004-DC62-44D4-80B0-F6A1E8518EA1@opencsw.org>
	<CALtRa-7UqZ+sFqrhPLT6M5Qd99HEL6v2mMX-sO-MQinERmoZyA@mail.gmail.com>
	<20140422060019.GK26613@bender.opencsw.org>
	<838709a7f76f69f65bda5484e4b67e6b@opencsw.org>
	<20140422131943.GN26613@bender.opencsw.org>
	<A97BF8C7-FA6B-40E9-A40D-A3E554432C58@opencsw.org>
	<20140422173637.GP26613@bender.opencsw.org>
Message-ID: <CALtRa-636yUiH=R0qJh+5WbqD0RoJHYz5FG6LY+QFpnMYn0j4Q@mail.gmail.com>

2014-04-22 18:36 GMT+01:00 Rafael Ostertag <raos at opencsw.org>:
> > Having the same format in the changelog is IMHO confusing as it suggests that
> > a package with the version and REV actually exists/existed.

I don't see that as a problem: if there's a changelog entry but there
wasn't a related package release, that's fine.

What I like is that you have to add a changelog entry to push out a
new version of the package. This simple trick will ensure that people
add changelog entries when upload new versions.

Maciej

From raos at opencsw.org  Tue Apr 22 20:27:25 2014
From: raos at opencsw.org (Rafael Ostertag)
Date: Tue, 22 Apr 2014 20:27:25 +0200
Subject: ld: fatal: use the -z help option for usage information
In-Reply-To: <CALtRa-5Mf3+mmiryoE-Z8s1GXMPn9VBRFCKTDWyus1RWFDWLNw@mail.gmail.com>
References: <CALtRa-5Vq0rW5v_0Zi8jKaOEWDY56LqSbd6qGA5jRWsK1sxjEg@mail.gmail.com>
	<CALtRa-7dAn2rfWdpfJtPVMW5DiHPV9JPwRC_LRZRdwXPnJJLzA@mail.gmail.com>
	<20140422151746.GO26613@bender.opencsw.org>
	<CALtRa-5Mf3+mmiryoE-Z8s1GXMPn9VBRFCKTDWyus1RWFDWLNw@mail.gmail.com>
Message-ID: <20140422182725.GQ26613@bender.opencsw.org>

Hi Maciej

On Tue, Apr 22, 2014 at 04:54:26PM +0100, Maciej (Matchek) Blizi??ski wrote:
> 2014-04-22 16:17 GMT+01:00 Rafael Ostertag <raos at opencsw.org>:
> > Is there a particular reason, you set
> >
> >  MACHDEP = $(ISA)
> >  EXTRA_CONFIGURE_EXPORTS += MACHDEP
> >
> > By doing so, some internal configure variables won't be set which in turn lead
> > to Makefile using `ld' instead of `gcc'.
> 
> Hm, ok. I'm trying to work around http://bugs.python.org/issue18083
> and modify paths to make the architecture dependent. MACHDEP is
> probably a wrong approach though. I'd like to do what they suggest in
> the bug report in python.org, but I don't know yet how to do it.

I don't know if it helps or gives some consolation, but I just had a glance at
the Fedora SRPM for python 3.3.0. They use a patch which replaces 'lib' by
'lib64' in following files

 Lib/distutils/command/install.py
 Lib/distutils/sysconfig.py
 Lib/site.py
 Lib/sysconfig.py
 Lib/test/test_site.py
 Makefile.pre.in
 Modules/getpath.c
 setup.py

cheers
rafi

From yann at pleiades.fr.eu.org  Tue Apr 22 22:25:51 2014
From: yann at pleiades.fr.eu.org (Yann Rouillard)
Date: Tue, 22 Apr 2014 22:25:51 +0200
Subject: Removal of CSWruby18tk from CSWruby18 build
In-Reply-To: <1565B0EC-A78A-48C6-B9EF-57E505C913A8@opencsw.org>
References: <4844e6ac71cacaf1a840f44b208fea04@opencsw.org>
	<CAF2fwscRoLAZy4CRwfE2hYiALPMWEzRLxNL320cysaMShF6w-A@mail.gmail.com>
	<1565B0EC-A78A-48C6-B9EF-57E505C913A8@opencsw.org>
Message-ID: <CAF2fwscQ0eicW-56uR8nVQfLDFLOtnyPY=xa74eZh3SYaWnE+w@mail.gmail.com>

>
>
> The RubyTk requires pthreads:
>   https://blogs.oracle.com/prashant/entry/ruby_and_enable_pthreads
> enable pthreads is 30-50% down in performance on Ruby, solution is to use
> this patch which disables switching ucontext with enabled pthreads:
>
> http://timetobleed.com/fix-a-bug-in-rubys-configurein-and-get-a-30-performance-boost/
>
> I?ll add that, respin, test and push.
>

Oh ! Great ! Feel free to take over the package. I only updated the package
to be able to close the openssl transition.
Are you sure this change can't have side effects on other modules ?

Yann
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140422/5db4bf71/attachment.html>

From pfelecan at opencsw.org  Wed Apr 23 19:56:09 2014
From: pfelecan at opencsw.org (Peter FELECAN)
Date: Wed, 23 Apr 2014 19:56:09 +0200
Subject: Your script
In-Reply-To: <A5466004-DC62-44D4-80B0-F6A1E8518EA1@opencsw.org> (Dagobert
	Michelsen's message of "Mon, 21 Apr 2014 23:26:41 +0200")
References: <A5466004-DC62-44D4-80B0-F6A1E8518EA1@opencsw.org>
Message-ID: <x6d2g82ame.fsf@opencsw.org>

Dagobert Michelsen <dam at opencsw.org> writes:

> Hi Rafi,
>
> I noticed you are working on a changelog edit script. This is superuseful
> and I wanted to have that for a very long time. I also keep thinking that it
> would be nice to have a dedicated place for the changelog per package in an
> easy-to-parse format (probably in ReST/Markdown?) which could be displayed
> on pkgutil -u (store the previous changelog before removal and diff to the
> newly installed one). Also Catalog changediffs could be generated that way.
>
> Thoughts?

I implemented this kind of mechanism when started to package for Debian
(private projects). What was very useful, aside the "Debian Way" is the
usage of svn2cl, which extract the last commit messages from
subversion. A must.
-- 
Peter

From maciej at opencsw.org  Thu Apr 24 00:59:33 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Wed, 23 Apr 2014 23:59:33 +0100
Subject: Your script
In-Reply-To: <x6d2g82ame.fsf@opencsw.org>
References: <A5466004-DC62-44D4-80B0-F6A1E8518EA1@opencsw.org>
	<x6d2g82ame.fsf@opencsw.org>
Message-ID: <CALtRa-7mUfDyc8NF5W+8w=+LeR3WnuqOfjjtn9TFe0EGSia9Hg@mail.gmail.com>

2014-04-23 18:56 GMT+01:00 Peter FELECAN <pfelecan at opencsw.org>:
> What was very useful, aside the "Debian Way" is the
> usage of svn2cl, which extract the last commit messages from
> subversion. A must.

I've implemented this in 2009:
http://lists.opencsw.org/pipermail/maintainers/2009-December/010809.html

And it was immediately shot down:
http://lists.opencsw.org/pipermail/maintainers/2009-December/010820.html

:(

Maciej

From maciej at opencsw.org  Thu Apr 24 11:47:26 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Thu, 24 Apr 2014 10:47:26 +0100
Subject: Reminder about *_dev package naming
Message-ID: <CALtRa-582xz+vAegA8E+mOaT--e3dHmcgn_VqknqGojJ6LHkww@mail.gmail.com>

If you're packaging a new library, let's call it foo, keep the
development package name "foo_dev", not "foo1_dev" (or any other
number).

Good: libfoo1 and foo_dev

Not good: libfoo1 and foo1_dev

Why? Because as API of the shared library changes, the development
package will likely stay the same. You'll end up with libfoo2 and
corresponding libfoo1_dev.

An exception could be when multiple versions of the development
package can coexist, e.g. when they use versioned file names such as
/opt/csw/include/foo-1.h.

Maciej

From maciej at opencsw.org  Sat Apr 26 14:09:04 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sat, 26 Apr 2014 13:09:04 +0100
Subject: unstable is broken. CSWlibgnutls28 is missing
Message-ID: <CALtRa-60kzOUTBVkg0kRn8POy_ZijBnCXS0kMcWtM+pVifhwGw@mail.gmail.com>

I'm investigating.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140426/7b4f6cf7/attachment.html>

From yann at pleiades.fr.eu.org  Sat Apr 26 14:18:45 2014
From: yann at pleiades.fr.eu.org (Yann Rouillard)
Date: Sat, 26 Apr 2014 14:18:45 +0200
Subject: unstable is broken. CSWlibgnutls28 is missing
In-Reply-To: <CALtRa-60kzOUTBVkg0kRn8POy_ZijBnCXS0kMcWtM+pVifhwGw@mail.gmail.com>
References: <CALtRa-60kzOUTBVkg0kRn8POy_ZijBnCXS0kMcWtM+pVifhwGw@mail.gmail.com>
Message-ID: <CAF2fwse=FH-bM5AU2zBj09DJ0sMxWXbagj2uzSTAFeSKtYQ1nw@mail.gmail.com>

Very strange.

I uploaded a new version of the package 3 days ago and I had a proper
acknowledgement from the catalog update script (see below).

Yann

Catalog update report for yann at opencsw.org
Catalog URL: http://mirror.opencsw.org/opencsw/

Version change (probably upgrade):
- screen-4.0.3,REV=2012.08.25-SunOS5.10-i386-CSW.pkg.gz
+ screen-4.2.0,REV=2014.04.23-SunOS5.10-i386-CSW.pkg.gz
  In catalogs:
  - unstable: i386 (5.10, 5.11)

- libgnutls28-3.1.22,REV=2014.03.06-SunOS5.10-sparc-CSW.pkg.gz
+ libgnutls28-3.1.23,REV=2014.04.22-SunOS5.10-sparc-CSW.pkg.gz
  In catalogs:
  - unstable: sparc (5.10, 5.11)

- libgnutls_dev-3.1.22,REV=2014.03.06-SunOS5.10-i386-CSW.pkg.gz
+ libgnutls_dev-3.1.23,REV=2014.04.22-SunOS5.10-i386-CSW.pkg.gz
  In catalogs:
  - unstable: i386 (5.10, 5.11)

- gnutls-3.1.22,REV=2014.03.06-SunOS5.10-i386-CSW.pkg.gz
+ gnutls-3.1.23,REV=2014.04.22-SunOS5.10-i386-CSW.pkg.gz
  In catalogs:
  - unstable: i386 (5.10, 5.11)

- screen-4.0.3,REV=2012.08.25-SunOS5.10-sparc-CSW.pkg.gz
+ screen-4.2.0,REV=2014.04.23-SunOS5.10-sparc-CSW.pkg.gz
  In catalogs:
  - unstable: sparc (5.10, 5.11)

- libgnutls_dev-3.1.22,REV=2014.03.06-SunOS5.10-sparc-CSW.pkg.gz
+ libgnutls_dev-3.1.23,REV=2014.04.22-SunOS5.10-sparc-CSW.pkg.gz
  In catalogs:
  - unstable: sparc (5.10, 5.11)

- libgnutls28-3.1.22,REV=2014.03.06-SunOS5.10-i386-CSW.pkg.gz
+ libgnutls28-3.1.23,REV=2014.04.22-SunOS5.10-i386-CSW.pkg.gz
  In catalogs:
  - unstable: i386 (5.10, 5.11)

- gnutls-3.1.22,REV=2014.03.06-SunOS5.10-sparc-CSW.pkg.gz
+ gnutls-3.1.23,REV=2014.04.22-SunOS5.10-sparc-CSW.pkg.gz
  In catalogs:
  - unstable: sparc (5.10, 5.11)


2014-04-26 14:09 GMT+02:00 Maciej (Matchek) Blizi?ski <maciej at opencsw.org>:

> I'm investigating.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140426/d5b10438/attachment.html>

From maciej at opencsw.org  Sat Apr 26 15:58:37 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sat, 26 Apr 2014 14:58:37 +0100
Subject: unstable is broken. CSWlibgnutls28 is missing
In-Reply-To: <CAF2fwse=FH-bM5AU2zBj09DJ0sMxWXbagj2uzSTAFeSKtYQ1nw@mail.gmail.com>
References: <CALtRa-60kzOUTBVkg0kRn8POy_ZijBnCXS0kMcWtM+pVifhwGw@mail.gmail.com>
	<CAF2fwse=FH-bM5AU2zBj09DJ0sMxWXbagj2uzSTAFeSKtYQ1nw@mail.gmail.com>
Message-ID: <CALtRa-5e3Mw5iiRRw-h=3UYtj8=uNBaXTOuSNiALz6Y8LGV4Bg@mail.gmail.com>

2014-04-26 13:18 GMT+01:00 Yann Rouillard <yann at pleiades.fr.eu.org>:
> I uploaded a new version of the package 3 days ago and I had a proper acknowledgement from the catalog update script (see below).

Thanks. This means that the problem does not occur during uploads, but
later. I'll keep investigating.

In the meantime, Yann reuploaded gnutls and the catalog is happy again.

Maciej

From ihsan at opencsw.org  Sun Apr 27 11:26:40 2014
From: ihsan at opencsw.org (=?UTF-8?B?xLBoc2FuwqBEb8SfYW4=?=)
Date: Sun, 27 Apr 2014 11:26:40 +0200
Subject: Killing newpkgs and pkgsubmissions lists
In-Reply-To: <CALtRa-7KWvT805aci8Luq=gqjBU2KhaNpgyvQwPbojMnE5sEXQ@mail.gmail.com>
References: <CALtRa-7KWvT805aci8Luq=gqjBU2KhaNpgyvQwPbojMnE5sEXQ@mail.gmail.com>
Message-ID: <535CCD50.2060800@opencsw.org>

Hi Maciej,

Am 12.04.2014 13:07, schrieb Maciej (Matchek) Blizi?ski:

> I propose we kill the newpkgs and pkgsubmissions mailing lists and
> remove them from the listinfo page[1]. They aren't used any more.

Fine for me.
Is anyone against this? The list haven't been in use for years.




Ihsan

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

From maciej at opencsw.org  Sun Apr 27 13:35:42 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sun, 27 Apr 2014 12:35:42 +0100
Subject: Killing newpkgs and pkgsubmissions lists
In-Reply-To: <535CCD50.2060800@opencsw.org>
References: <CALtRa-7KWvT805aci8Luq=gqjBU2KhaNpgyvQwPbojMnE5sEXQ@mail.gmail.com>
	<535CCD50.2060800@opencsw.org>
Message-ID: <CALtRa-70TYV1LM9snY3XbT=1kkhTnhUniD4tJzACbgzric-wYw@mail.gmail.com>

2014-04-27 10:26 GMT+01:00 ?hsan Do?an <ihsan at opencsw.org>:
> Fine for me.
> Is anyone against this? The list haven't been in use for years

I've sent my original email over 2 weeks ago, nobody objected, we can
go ahead and delete them.

Maciej

From maciej at opencsw.org  Mon Apr 28 10:16:15 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Mon, 28 Apr 2014 09:16:15 +0100
Subject: Bugs in the package browser; user names are mismatched
In-Reply-To: <CALtRa-65XVsTWktTiVdQXYqFewX_Wb0FCOx7QQ+6dz3=eWkMsw@mail.gmail.com>
References: <CALtRa-65XVsTWktTiVdQXYqFewX_Wb0FCOx7QQ+6dz3=eWkMsw@mail.gmail.com>
Message-ID: <CALtRa-5X2kj9=yZ8Z2M=nYxKGFE0P8uyyU0U_PmkirQJ=bWrcg@mail.gmail.com>

2014-04-20 21:48 GMT+01:00 Maciej (Matchek) Blizi?ski <maciej at opencsw.org>:
> http://www.opencsw.org/packages/fi_agent/
>
> "Last uploaded by" is empty.
>
> There's a page with a truncated user name:
> http://www.opencsw.org/maintainers/guillomo/

So... nobody knows? I was hoping Ben would know.

From aironskin at opencsw.org  Mon Apr 28 10:53:50 2014
From: aironskin at opencsw.org (Stefan Schnyder)
Date: Mon, 28 Apr 2014 10:53:50 +0200
Subject: Website news
Message-ID: <535E171E.5020808@opencsw.org>

Hey guys,

Does anyone have some news for the website? The last entry will soon be 
a month old.
I'd be nice if we could post at least each month something.

I'm not saying we should post useless information - it there's nothing 
to say that's fine. But people should see that stuff is going on.

Cheers,
Stefan

PS: you can always send me the news and I'll post them if you don't have 
an account or are too lazy ;)

From dam at opencsw.org  Mon Apr 28 10:54:28 2014
From: dam at opencsw.org (Dagobert Michelsen)
Date: Mon, 28 Apr 2014 10:54:28 +0200
Subject: Website news
In-Reply-To: <535E171E.5020808@opencsw.org>
References: <535E171E.5020808@opencsw.org>
Message-ID: <13E91EE9-A88B-4385-97CB-63A28B83B0AD@opencsw.org>

Hi Stefan,

Am 28.04.2014 um 10:53 schrieb Stefan Schnyder <aironskin at opencsw.org>:
> Does anyone have some news for the website? The last entry will soon be a month old.
> I'd be nice if we could post at least each month something.
> 
> I'm not saying we should post useless information - it there's nothing to say that's fine. But people should see that stuff is going on.
> 
> Cheers,
> Stefan
> 
> PS: you can always send me the news and I'll post them if you don't have an account or are too lazy ;)

Would it be possible to add the released packages RSS feed on the webpage?


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: smime.p7s
Type: application/pkcs7-signature
Size: 2418 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140428/d02dace2/attachment.p7s>

From aironskin at opencsw.org  Mon Apr 28 10:56:23 2014
From: aironskin at opencsw.org (Stefan Schnyder)
Date: Mon, 28 Apr 2014 10:56:23 +0200
Subject: Website news
In-Reply-To: <13E91EE9-A88B-4385-97CB-63A28B83B0AD@opencsw.org>
References: <535E171E.5020808@opencsw.org>
	<13E91EE9-A88B-4385-97CB-63A28B83B0AD@opencsw.org>
Message-ID: <535E17B7.2070007@opencsw.org>

I don't feel confident enough to automate that (embedd it on the 
website... don't know how to do that). I could however do it manually 
once a week or once a month...

On 04/28/2014 10:54 AM, Dagobert Michelsen wrote:
> Hi Stefan,
>
> Am 28.04.2014 um 10:53 schrieb Stefan Schnyder <aironskin at opencsw.org>:
>> Does anyone have some news for the website? The last entry will soon be a month old.
>> I'd be nice if we could post at least each month something.
>>
>> I'm not saying we should post useless information - it there's nothing to say that's fine. But people should see that stuff is going on.
>>
>> Cheers,
>> Stefan
>>
>> PS: you can always send me the news and I'll post them if you don't have an account or are too lazy ;)
> Would it be possible to add the released packages RSS feed on the webpage?
>
>
> Best regards
>
>    ? Dago
>
>


From maciej at opencsw.org  Mon Apr 28 10:56:17 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Mon, 28 Apr 2014 09:56:17 +0100
Subject: Website news
In-Reply-To: <13E91EE9-A88B-4385-97CB-63A28B83B0AD@opencsw.org>
References: <535E171E.5020808@opencsw.org>
	<13E91EE9-A88B-4385-97CB-63A28B83B0AD@opencsw.org>
Message-ID: <CALtRa-7OCE3tBUVUfK+sGW+ec7LtOO=Hv4KAo78ytGa1DWX0gQ@mail.gmail.com>

2014-04-28 9:54 GMT+01:00 Dagobert Michelsen <dam at opencsw.org>:
> Would it be possible to add the released packages RSS feed on the webpage?

I support that, pushing out new packages is what we do best, we should
advertise it more.

From maciej at opencsw.org  Mon Apr 28 10:59:20 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Mon, 28 Apr 2014 09:59:20 +0100
Subject: Website news
In-Reply-To: <535E17B7.2070007@opencsw.org>
References: <535E171E.5020808@opencsw.org>
	<13E91EE9-A88B-4385-97CB-63A28B83B0AD@opencsw.org>
	<535E17B7.2070007@opencsw.org>
Message-ID: <CALtRa-6f+7J2T88mHnedVRWX48QZHyTP7MhyfwhTj8ook5ZtbA@mail.gmail.com>

2014-04-28 9:56 GMT+01:00 Stefan Schnyder <aironskin at opencsw.org>:
> I don't feel confident enough to automate that (embedd it on the website...
> don't know how to do that). I could however do it manually once a week or
> once a month...

The data, always fresh, are here:
http://www.opencsw.org/catalogfeeds/feed.mirror.opencsw.org.opencsw.unstable.atom

All we need it automatic formatting into HTML and including it in the page.

BTW, feed index is here: http://www.opencsw.org/feeds/

From aironskin at opencsw.org  Mon Apr 28 11:08:16 2014
From: aironskin at opencsw.org (Stefan Schnyder)
Date: Mon, 28 Apr 2014 11:08:16 +0200
Subject: Website news
In-Reply-To: <CALtRa-6f+7J2T88mHnedVRWX48QZHyTP7MhyfwhTj8ook5ZtbA@mail.gmail.com>
References: <535E171E.5020808@opencsw.org>	<13E91EE9-A88B-4385-97CB-63A28B83B0AD@opencsw.org>	<535E17B7.2070007@opencsw.org>
	<CALtRa-6f+7J2T88mHnedVRWX48QZHyTP7MhyfwhTj8ook5ZtbA@mail.gmail.com>
Message-ID: <535E1A80.7000406@opencsw.org>

And do you want to do this in the form of (Wordpress-)posts, or as a 
constantly up to date feed, somewhere on the website?

The problem with the first approach would be the interval. You'd have to 
do something every week and generate a post from it.
The problem with the second approach is, that space is kind of limited 
on the site. Also, this put's an additional information element on the 
site, which goes somehow against what was discussed earlier on the topic 
of consolidation:

Now my thoughts:

  * I think, that our website doesn't need to contain that much
    information. It needs to get people started & provide access to
    further information and tools (Daniel had some nice ideas there).

Yes, I agree.

Although it has a higher maintenance load, I'd go for approach one...

Cheers,
Stefan

On 04/28/2014 10:59 AM, Maciej (Matchek) Blizi?ski wrote:
> 2014-04-28 9:56 GMT+01:00 Stefan Schnyder <aironskin at opencsw.org>:
>> I don't feel confident enough to automate that (embedd it on the website...
>> don't know how to do that). I could however do it manually once a week or
>> once a month...
> The data, always fresh, are here:
> http://www.opencsw.org/catalogfeeds/feed.mirror.opencsw.org.opencsw.unstable.atom
>
> All we need it automatic formatting into HTML and including it in the page.
>
> BTW, feed index is here: http://www.opencsw.org/feeds/
>


From dam at opencsw.org  Mon Apr 28 11:47:07 2014
From: dam at opencsw.org (Dagobert Michelsen)
Date: Mon, 28 Apr 2014 11:47:07 +0200
Subject: Website news
In-Reply-To: <535E1A80.7000406@opencsw.org>
References: <535E171E.5020808@opencsw.org>	<13E91EE9-A88B-4385-97CB-63A28B83B0AD@opencsw.org>	<535E17B7.2070007@opencsw.org>
	<CALtRa-6f+7J2T88mHnedVRWX48QZHyTP7MhyfwhTj8ook5ZtbA@mail.gmail.com>
	<535E1A80.7000406@opencsw.org>
Message-ID: <C343F9AB-FF0A-4781-B57D-38C32AB5FEE5@opencsw.org>

Hi Stefan,

Am 28.04.2014 um 11:08 schrieb Stefan Schnyder <aironskin at opencsw.org>:
> And do you want to do this in the form of (Wordpress-)posts, or as a constantly up to date feed, somewhere on the website?

I was thinking of just using a plugin for that like
  https://wordpress.org/plugins/tags/rss

> The problem with the first approach would be the interval. You'd have to do something every week and generate a post from it.
> The problem with the second approach is, that space is kind of limited on the site. Also, this put's an additional information element on the site, which goes somehow against what was discussed earlier on the topic of consolidation:
> 
> Now my thoughts:
> 
> * I think, that our website doesn't need to contain that much
>   information. It needs to get people started & provide access to
>   further information and tools (Daniel had some nice ideas there).
> 
> Yes, I agree.
> 
> Although it has a higher maintenance load, I'd go for approach one...

And it needs to make people confident that there is activity in the project :-)


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: smime.p7s
Type: application/pkcs7-signature
Size: 2418 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140428/f64a097f/attachment.p7s>

From pfelecan at opencsw.org  Mon Apr 28 19:36:59 2014
From: pfelecan at opencsw.org (Peter FELECAN)
Date: Mon, 28 Apr 2014 19:36:59 +0200
Subject: Website news
In-Reply-To: <CALtRa-7OCE3tBUVUfK+sGW+ec7LtOO=Hv4KAo78ytGa1DWX0gQ@mail.gmail.com>
	("Maciej (Matchek) =?utf-8?Q?Blizi=C5=84ski=22's?= message of "Mon,
	28 Apr 2014 09:56:17 +0100")
References: <535E171E.5020808@opencsw.org>
	<13E91EE9-A88B-4385-97CB-63A28B83B0AD@opencsw.org>
	<CALtRa-7OCE3tBUVUfK+sGW+ec7LtOO=Hv4KAo78ytGa1DWX0gQ@mail.gmail.com>
Message-ID: <x6bnvlz77o.fsf@opencsw.org>

"Maciej (Matchek) Blizi?ski" <maciej at opencsw.org> writes:

> 2014-04-28 9:54 GMT+01:00 Dagobert Michelsen <dam at opencsw.org>:
>> Would it be possible to add the released packages RSS feed on the webpage?
>
> I support that, pushing out new packages is what we do best, we should
> advertise it more.

FWIW +1
-- 
Peter

From igalic at opencsw.org  Tue Apr 29 11:11:13 2014
From: igalic at opencsw.org (Igor =?utf-8?Q?Gali=C4=87?=)
Date: Tue, 29 Apr 2014 09:11:13 +0000 (UTC)
Subject: Eremitus
In-Reply-To: <1234265946.43680.1398757661509.JavaMail.zimbra@brainsware.org>
Message-ID: <676690348.49086.1398762673484.JavaMail.zimbra@brainsware.org>

Hi folks,


recently I've been increasingly overwhelmed with email, but have had less
and less time to contribute to FOSS that is outside of my work's scope
Unfortunately Solaris has been outside of that for quite some time now :(

I'd like to go emeritus for now, and if possible come back FOSS time and
work time realign again.

Thank you very much,

So long,

i

From wilbury at opencsw.org  Wed Apr 30 00:12:07 2014
From: wilbury at opencsw.org (Juraj Lutter)
Date: Wed, 30 Apr 2014 00:12:07 +0200
Subject: PHP 5.5 build error
In-Reply-To: <53602397.3000002@lutter.sk>
References: <53602397.3000002@lutter.sk>
Message-ID: <536023B7.4080008@opencsw.org>

Folks,

does anyone of you know how to deal with this?

CHECKPKG_OVERRIDES_CSWap2-modphp5 +=
bad-rpath-entry|/usr/ucblib|opt/csw/apache2/libexec/libphp5.so
CHECKPKG_OVERRIDES_CSWap2-modphp5 +=
forbidden-version-interface-dependencies|/opt/csw/apache2/libexec/libphp5.so|requires|forbidden|interface|version|SUNW_1.22.7|in|library|libc.so.1


CHECKPKG_OVERRIDES_CSWphp5 +=
bad-rpath-entry|/usr/ucblib|opt/csw/php5/bin/php
CHECKPKG_OVERRIDES_CSWphp5 +=
bad-rpath-entry|/usr/ucblib|opt/csw/php5/bin/php-cgi
CHECKPKG_OVERRIDES_CSWphp5 +=
forbidden-version-interface-dependencies|/opt/csw/php5/bin/php|requires|forbidden|interface|version|SUNW_1.22.7|in|library|libc.so.1
CHECKPKG_OVERRIDES_CSWphp5 +=
forbidden-version-interface-dependencies|/opt/csw/php5/bin/php-cgi|requires|forbidden|interface|version|SUNW_1.22.7|in|library|libc.so.1


Thanks.

/w

-- 
Juraj Lutter
URL:  http://www.wilbury.sk/
XMPP: juraj at lutter.sk
Pekny, mily a usmievavy webhosting a serverhousing: http://www.nic.sk/



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

From dam at opencsw.org  Wed Apr 30 08:36:11 2014
From: dam at opencsw.org (Dagobert Michelsen)
Date: Wed, 30 Apr 2014 08:36:11 +0200
Subject: PHP 5.5 build error
In-Reply-To: <536023B7.4080008@opencsw.org>
References: <53602397.3000002@lutter.sk> <536023B7.4080008@opencsw.org>
Message-ID: <F2D2D96C-C6F2-4564-ADA9-1511B19999FA@opencsw.org>

Hi Juraj,

Am 30.04.2014 um 00:12 schrieb Juraj Lutter <wilbury at opencsw.org>:

> Folks,
> 
> does anyone of you know how to deal with this?
> 
> CHECKPKG_OVERRIDES_CSWap2-modphp5 += bad-rpath-entry|/usr/ucblib|opt/csw/apache2/libexec/libphp5.so

There is a patch that was used earlier, maybe it needs forward porting:
  https://buildfarm.opencsw.org/source/xref/opencsw/csw/mgar/pkg/php5/branches/php-5.5.x/Makefile#48

> CHECKPKG_OVERRIDES_CSWap2-modphp5 += forbidden-version-interface-dependencies|/opt/csw/apache2/libexec/libphp5.so|requires|forbidden|interface|version|SUNW_1.22.7|in|library|libc.so.1

This is probably because of libmysql. I suggest just overriding it.

> 
> 
> CHECKPKG_OVERRIDES_CSWphp5 += bad-rpath-entry|/usr/ucblib|opt/csw/php5/bin/php
> CHECKPKG_OVERRIDES_CSWphp5 += bad-rpath-entry|/usr/ucblib|opt/csw/php5/bin/php-cgi

Same as above.

> CHECKPKG_OVERRIDES_CSWphp5 += forbidden-version-interface-dependencies|/opt/csw/php5/bin/php|requires|forbidden|interface|version|SUNW_1.22.7|in|library|libc.so.1
> CHECKPKG_OVERRIDES_CSWphp5 += forbidden-version-interface-dependencies|/opt/csw/php5/bin/php-cgi|requires|forbidden|interface|version|SUNW_1.22.7|in|library|libc.so.1

Same as above.


Best regards & thanks for the effort!

  ? 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/20140430/a2005dfd/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2418 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140430/a2005dfd/attachment-0001.p7s>

From jh at opencsw.org  Wed Apr 30 08:43:47 2014
From: jh at opencsw.org (Jan Holzhueter)
Date: Wed, 30 Apr 2014 08:43:47 +0200
Subject: PHP 5.5 build error
In-Reply-To: <F2D2D96C-C6F2-4564-ADA9-1511B19999FA@opencsw.org>
References: <53602397.3000002@lutter.sk> <536023B7.4080008@opencsw.org>
	<F2D2D96C-C6F2-4564-ADA9-1511B19999FA@opencsw.org>
Message-ID: <53609BA3.4010304@opencsw.org>

Hi,

Am 30.04.14 08:36, schrieb Dagobert Michelsen:
> Hi Juraj,
> 
> Am 30.04.2014 um 00:12 schrieb Juraj Lutter <wilbury at opencsw.org
> <mailto:wilbury at opencsw.org>>:
> 
>> Folks,
>>
>> does anyone of you know how to deal with this?
>>
>> CHECKPKG_OVERRIDES_CSWap2-modphp5 +=
>> bad-rpath-entry|/usr/ucblib|opt/csw/apache2/libexec/libphp5.so
> 
> There is a patch that was used earlier, maybe it needs forward porting:
>   https://buildfarm.opencsw.org/source/xref/opencsw/csw/mgar/pkg/php5/branches/php-5.5.x/Makefile#48
> 
>> CHECKPKG_OVERRIDES_CSWap2-modphp5 +=
>> forbidden-version-interface-dependencies|/opt/csw/apache2/libexec/libphp5.so|requires|forbidden|interface|version|SUNW_1.22.7|in|library|libc.so.1
> 
> This is probably because of libmysql. I suggest just overriding it.
> 

libmysql would be 1.22.5.
1.22.7 is default iirc. So map file is not pulled in at all I think
This needs to be locked at.

Greetings
Jan



From maciej at opencsw.org  Wed Apr 30 19:51:32 2014
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Wed, 30 Apr 2014 18:51:32 +0100
Subject: Eremitus
In-Reply-To: <676690348.49086.1398762673484.JavaMail.zimbra@brainsware.org>
References: <1234265946.43680.1398757661509.JavaMail.zimbra@brainsware.org>
	<676690348.49086.1398762673484.JavaMail.zimbra@brainsware.org>
Message-ID: <CALtRa-4vYFD30rkaQYNk+gAhtA0aMza4R7HcB_HtE+6uBd4dBw@mail.gmail.com>

Hi Igor,

I'm sad to see you go. Thanks for all the packaging work! Hang around
the project IRC channel for random chatter. :)

Maciej