From maciej at opencsw.org  Thu Sep  1 14:36:00 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=)
Date: Thu, 1 Sep 2011 13:36:00 +0100
Subject: [csw-maintainers] Reasons for gcc to have a separate prefix
In-Reply-To: <CALtRa-58xD0J6kNw6hHSSQpQenL7TX_fOwOad7aaQUmUTJTXWg@mail.gmail.com>
References: <CALtRa-4=7HWC=+i7VS-n_s8_8ZunNbp6RH-0HxGfK6-ePwtYcA@mail.gmail.com>
	<1314317946-sup-2767@pinkfloyd.chass.utoronto.ca>
	<CALtRa-58xD0J6kNw6hHSSQpQenL7TX_fOwOad7aaQUmUTJTXWg@mail.gmail.com>
Message-ID: <CALtRa-7b-L4PUw5ReqAZsS-UQBCVLL6PoOT6zkjWOQdFt2gj1A@mail.gmail.com>

2011/8/31 Maciej Blizi?ski <maciej at opencsw.org>:
> /opt/csw/gcc4/bin/gcc ? ../../bin/gcc-4.6
>
> All other links accordingly.

Done!

Please test!

http://buildfarm.opencsw.org/experimental.html#gcc4

As a bonus, I have rebuilt gcc-3.4.6 with GAR.  This means we'll be
able to introduce alternatives to gcc-3.x as well, but the build
recipe needs more work to nicely split the installed files into
packages.

Peter F, do you by any chance have the file?pkg mapping from your
non-gar builds of gcc-3.x?

Maciej

From bwalton at opencsw.org  Fri Sep  2 05:05:22 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Thu, 01 Sep 2011 23:05:22 -0400
Subject: [csw-maintainers] catalog fun
Message-ID: <1314931865-sup-91@pinkfloyd.chass.utoronto.ca>


Hi All,

I'm gradually weeding out the error cases in detecting catalog changes
in order to generate updates for mantis and the web db.  Here's an
interesting case I found tonight (trimmed to illustrate the point):

Old catalog:

perl/CSWperl
pm_dbd_sqlite/CSWpm-dbd-sqlite -> CSWperl, CSWpmdbi
pm_dbi_stub/CSWpmdbi -> CSWperl, CSWpm-dbi
pm_dbi/CSWpm-dbi -> CSWperl

New catalog:

perl/CSWperl
pm_dbd_sqlite/CSWpm-dbd-sqlite -> CSWperl,CSWpmdbi
pm_dbi2/CSWpmdbi -> CSWperl, CSWpm-dbi
pm_dbi/CSWpm-dbi -> CSWperl

This is a technically valid catalog as all dependencies are met
(chkcat should be happy).  I'm currently detecting this as a "Silent
Name Change."  This is an instance of 'un-stubbing' which I think
should be considered an error.  What do others think?

In this specific case, was the name change intentional?  It looks a
bit funny to me to start calling CSWpmdbi pm_dbi2 (version number is
1.616) all of a sudden after stubbing it out.  Can someone provide
insight on this?

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From pfelecan at opencsw.org  Fri Sep  2 14:23:41 2011
From: pfelecan at opencsw.org (Peter FELECAN)
Date: Fri, 02 Sep 2011 14:23:41 +0200
Subject: [csw-maintainers] Reasons for gcc to have a separate prefix
In-Reply-To: <CALtRa-7b-L4PUw5ReqAZsS-UQBCVLL6PoOT6zkjWOQdFt2gj1A@mail.gmail.com>
	("Maciej =?utf-8?Q?Blizi=C5=84ski=22's?= message of "Thu, 1 Sep 2011
	13:36:00 +0100")
References: <CALtRa-4=7HWC=+i7VS-n_s8_8ZunNbp6RH-0HxGfK6-ePwtYcA@mail.gmail.com>
	<1314317946-sup-2767@pinkfloyd.chass.utoronto.ca>
	<CALtRa-58xD0J6kNw6hHSSQpQenL7TX_fOwOad7aaQUmUTJTXWg@mail.gmail.com>
	<CALtRa-7b-L4PUw5ReqAZsS-UQBCVLL6PoOT6zkjWOQdFt2gj1A@mail.gmail.com>
Message-ID: <x662lbceuq.fsf@opencsw.org>

Maciej Blizi?ski <maciej at opencsw.org> writes:

> Peter F, do you by any chance have the file?pkg mapping from your
> non-gar builds of gcc-3.x?

Look in my home directory for gcc3.4.6-prune.tar; each file contains a
list of regular expressions, those with a - prefix are exclusions and
those with a + prefix are inclusions.

HTH

-- 
Peter

From maciej at opencsw.org  Sat Sep  3 12:00:44 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=)
Date: Sat, 3 Sep 2011 11:00:44 +0100
Subject: [csw-maintainers] Catalog layout
Message-ID: <CALtRa-79EXWEJ6CGWb9OU_NUXfH96mQP0TXDFiC8s7Z2kCgUFw@mail.gmail.com>

Hello maintainers,

Early in the planning of the new catalog layout, we introduced the
notion of snapshots.  They are currently available from the mirror:

http://mirror.opencsw.org/opencsw-future/snapshots/

I initially thought of snapshots as of something that can be
eventually promoted to stable.  But we've come up with the idea of
named releases, which I think is a much better one.

I'd like to remove snapshots from the mirror.  If we want to have some
sort of catalog tracking system, we can have it on the buildfarm, but
I think that the price we pay in terms of the archive size is too
high.  Having snapshots means that we have a lot more hardlinks to
cross-check and rsync, and we can't garbage-collect allpkgs as
efficiently, because files keep being used by the snapshots.

However, I just realized I can't back up my claim by numbers, so I'll
try to measure how many files and how much space we're talking about.
All I have right now is watching rsync and thinking "man, this is
taking too much time."

Maciej

From maciej at opencsw.org  Sat Sep  3 18:06:33 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=)
Date: Sat, 3 Sep 2011 17:06:33 +0100
Subject: [csw-maintainers] GAR coding style
Message-ID: <CALtRa-62mp5HcXPhKGG5_edz7HoLACBz7=1nEjwPGWiiB2SYYw@mail.gmail.com>

Hello maintainers,

We have a wiki page describing our coding style:

http://sourceforge.net/apps/trac/gar/wiki/GarCodingStyle

I know that Dago used to prefer the by-phase grouping (he wrote the
guide), has anything changed in that regard?  Most maintainers are in
practice gravitating towards a different style, where we group code by
packages, and not by GAR phases.

Should we update the coding guideline to reflect this, or do we need
more discussion?

Maciej

From bwalton at opencsw.org  Sat Sep  3 20:00:09 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Sat, 03 Sep 2011 14:00:09 -0400
Subject: [csw-maintainers] GAR coding style
In-Reply-To: <CALtRa-62mp5HcXPhKGG5_edz7HoLACBz7=1nEjwPGWiiB2SYYw@mail.gmail.com>
References: <CALtRa-62mp5HcXPhKGG5_edz7HoLACBz7=1nEjwPGWiiB2SYYw@mail.gmail.com>
Message-ID: <1315072642-sup-9501@pinkfloyd.chass.utoronto.ca>

Excerpts from Maciej Blizi?ski's message of Sat Sep 03 12:06:33 -0400 2011:

Hi Maciej,

> http://sourceforge.net/apps/trac/gar/wiki/GarCodingStyle

> Should we update the coding guideline to reflect this, or do we need
> more discussion?

I am in the group that has started lumping package describing things
together although I typically still follow the overall flow of the
described style.  I think that if #9 were blended into #3 that it
would fairly closely match my preferred pattern.  I'd be happy to
support this (fairly minor, imo) change.

Do you see larger changes needed to fit what we're seeing in practice?

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From maciej at opencsw.org  Sat Sep  3 23:49:42 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=)
Date: Sat, 3 Sep 2011 22:49:42 +0100
Subject: [csw-maintainers] GAR coding style
In-Reply-To: <1315072642-sup-9501@pinkfloyd.chass.utoronto.ca>
References: <CALtRa-62mp5HcXPhKGG5_edz7HoLACBz7=1nEjwPGWiiB2SYYw@mail.gmail.com>
	<1315072642-sup-9501@pinkfloyd.chass.utoronto.ca>
Message-ID: <CALtRa-76raPzoCbn+OpehsY4zdixKNOf+n4=2mngLVudg7_SRQ@mail.gmail.com>

2011/9/3 Ben Walton <bwalton at opencsw.org>:
> Excerpts from Maciej Blizi?ski's message of Sat Sep 03 12:06:33 -0400 2011:
>
> Hi Maciej,
>
>> http://sourceforge.net/apps/trac/gar/wiki/GarCodingStyle
>
>> Should we update the coding guideline to reflect this, or do we need
>> more discussion?
>
> I am in the group that has started lumping package describing things
> together although I typically still follow the overall flow of the
> described style. ?I think that if #9 were blended into #3 that it
> would fairly closely match my preferred pattern. ?I'd be happy to
> support this (fairly minor, imo) change.
>
> Do you see larger changes needed to fit what we're seeing in practice?

Nothing larger, your paragraph summarizes it well.  I'd move PACKAGES
and SPKG_DESC from #3 to #9, and indicate that PACKAGES would use +=
and have one entry per package.  I also thought that we could show an
example, an example may be easier to understand than a description.

Maciej

From maciej at opencsw.org  Sun Sep  4 09:40:41 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=)
Date: Sun, 4 Sep 2011 08:40:41 +0100
Subject: [csw-maintainers] catalog fun
In-Reply-To: <1314931865-sup-91@pinkfloyd.chass.utoronto.ca>
References: <1314931865-sup-91@pinkfloyd.chass.utoronto.ca>
Message-ID: <CALtRa-7mPmf=2q5w4PCdvX4Dkd45sch9JkRkBbVX-EmEayK9pg@mail.gmail.com>

2011/9/2 Ben Walton <bwalton at opencsw.org>:
> Old catalog:
>
> perl/CSWperl
> pm_dbd_sqlite/CSWpm-dbd-sqlite -> CSWperl, CSWpmdbi
> pm_dbi_stub/CSWpmdbi -> CSWperl, CSWpm-dbi
> pm_dbi/CSWpm-dbi -> CSWperl
>
> New catalog:
>
> perl/CSWperl
> pm_dbd_sqlite/CSWpm-dbd-sqlite -> CSWperl,CSWpmdbi
> pm_dbi2/CSWpmdbi -> CSWperl, CSWpm-dbi

Right, this in fact has become "pm_dbi2" while it was "pm_dbi_stub".

> pm_dbi/CSWpm-dbi -> CSWperl
>
> This is a technically valid catalog as all dependencies are met
> (chkcat should be happy). ?I'm currently detecting this as a "Silent
> Name Change." ?This is an instance of 'un-stubbing' which I think
> should be considered an error. ?What do others think?

In general, is catalogname change with no pkgname change an error?

> In this specific case, was the name change intentional? ?It looks a
> bit funny to me to start calling CSWpmdbi pm_dbi2 (version number is
> 1.616) all of a sudden after stubbing it out. ?Can someone provide
> insight on this?

I vaguely remember that a more complicated rename case required you to
change the catalogname where you didn't want to, and that the number 2
was used.  I don't recall the specifics, it was something like two
renames of the same package.

Maciej

From dam at opencsw.org  Sun Sep  4 17:07:07 2011
From: dam at opencsw.org (Dagobert Michelsen)
Date: Sun, 4 Sep 2011 17:07:07 +0200
Subject: [csw-maintainers] GAR coding style
In-Reply-To: <CALtRa-76raPzoCbn+OpehsY4zdixKNOf+n4=2mngLVudg7_SRQ@mail.gmail.com>
References: <CALtRa-62mp5HcXPhKGG5_edz7HoLACBz7=1nEjwPGWiiB2SYYw@mail.gmail.com>
	<1315072642-sup-9501@pinkfloyd.chass.utoronto.ca>
	<CALtRa-76raPzoCbn+OpehsY4zdixKNOf+n4=2mngLVudg7_SRQ@mail.gmail.com>
Message-ID: <0D44CE17-05C9-470A-A1A3-6B010F625021@opencsw.org>

Hi Maciej,

Am 03.09.2011 um 23:49 schrieb Maciej Blizi?ski:
> 2011/9/3 Ben Walton <bwalton at opencsw.org>:
>> Excerpts from Maciej Blizi?ski's message of Sat Sep 03 12:06:33 -0400 2011:
>>> http://sourceforge.net/apps/trac/gar/wiki/GarCodingStyle
>> 
>>> Should we update the coding guideline to reflect this, or do we need
>>> more discussion?
>> 
>> I am in the group that has started lumping package describing things
>> together although I typically still follow the overall flow of the
>> described style.  I think that if #9 were blended into #3 that it
>> would fairly closely match my preferred pattern.  I'd be happy to
>> support this (fairly minor, imo) change.
>> 
>> Do you see larger changes needed to fit what we're seeing in practice?
> 
> Nothing larger, your paragraph summarizes it well.  I'd move PACKAGES
> and SPKG_DESC from #3 to #9, and indicate that PACKAGES would use +=
> and have one entry per package.  I also thought that we could show an
> example, an example may be easier to understand than a description.

This is exactly how I write it now. Additionally, I would recommend not
setting defaults like package catalog name unless it is needed to make
something explicitly clear or change the defaults.


Best regards

  -- Dago

From bwalton at opencsw.org  Sun Sep  4 17:23:24 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Sun, 04 Sep 2011 11:23:24 -0400
Subject: [csw-maintainers] dropping support for solaris 9?
Message-ID: <1315149086-sup-7658@pinkfloyd.chass.utoronto.ca>


Hi All,

The premier support of Solaris 9 ends in October[1] of this year.  How
do people feel about dropping build support for it and moving to
Solaris 10 and 11 only?

My thinking is that we should drop it on the same date as Oracle to
avoid the situation we had with Solaris 8 where we were building
packages for it _way_ after the 'best before' date.

What do others think?

(I added this as a dicussion item for the Kiel Summercamp too.)

Thanks
-Ben

[1] Page 30 of: http://www.oracle.com/us/support/library/lifetime-support-hardware-os-337182.pdf
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From bwalton at opencsw.org  Sun Sep  4 19:18:05 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Sun, 04 Sep 2011 13:18:05 -0400
Subject: [csw-maintainers] Catalog layout
In-Reply-To: <CALtRa-79EXWEJ6CGWb9OU_NUXfH96mQP0TXDFiC8s7Z2kCgUFw@mail.gmail.com>
References: <CALtRa-79EXWEJ6CGWb9OU_NUXfH96mQP0TXDFiC8s7Z2kCgUFw@mail.gmail.com>
Message-ID: <1315156495-sup-906@pinkfloyd.chass.utoronto.ca>

Excerpts from Maciej Blizi?ski's message of Sat Sep 03 06:00:44 -0400 2011:

Hi Maciej,

> http://mirror.opencsw.org/opencsw-future/snapshots/

I think the one benefit these could provide is a mechanism to gather a
bit of historical information for stats purposes.  It would be 'gappy'
as it relies on the interval.  The shorter the interval, the heavier
the weight of keeping the snapshots.

I think that statistical info is better handled by William's tools, so
I'm not sure that the snapshots are useful.

Is there another intended use for them?

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From ja at opencsw.org  Sun Sep  4 19:45:22 2011
From: ja at opencsw.org (Juergen Arndt)
Date: Sun, 4 Sep 2011 19:45:22 +0200
Subject: [csw-maintainers] catalog name does not match pkg name
Message-ID: <CC598E25-7D4B-40AB-8329-FA8D06BD0312@opencsw.org>

Hi all,

while rebuilding and updating the munin packages, checkpkg gives back the error "catalogname-does-not-match-pkgname" because the catalog name contains an underscore and the package name doesn't:  munin_master <--> CSWmuninmaster

I think, the best solution is to change the catalog name to "muninmaster" ("muninnode" and "munincommon" too). How this could be done? The other solution would be to override these errors in the gar recipe.

(The packages are not ready yet, so there is no urgent action needed)

Regards,
Juergen

-- 
Juergen Arndt


From bwalton at opencsw.org  Sun Sep  4 19:59:01 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Sun, 04 Sep 2011 13:59:01 -0400
Subject: [csw-maintainers] catalog name does not match pkg name
In-Reply-To: <CC598E25-7D4B-40AB-8329-FA8D06BD0312@opencsw.org>
References: <CC598E25-7D4B-40AB-8329-FA8D06BD0312@opencsw.org>
Message-ID: <1315158805-sup-4307@pinkfloyd.chass.utoronto.ca>

Excerpts from Juergen Arndt's message of Sun Sep 04 13:45:22 -0400 2011:

Hi Juergen

> while rebuilding and updating the munin packages, checkpkg gives
> back the error "catalogname-does-not-match-pkgname" because the
> catalog name contains an underscore and the package name doesn't:
> munin_master <--> CSWmuninmaster

I think the nicer (human consumable) names are
munin_master/CSWmunin-master, etc.  To reach this goal, you could
rename all of the package and catalog items in the GAR recipe and then
add things like:

OBSOLETED_BY_CSWmunin-master = CSWmuninmaster
SPKG_CATALOG_NAME_CSWmuninmaster = munin_master_stub

The second line ensures that the _stub name will be $old_catalog_name
+ _stub which we agreed was the requirement a while back.

These lines in your recipe will see an empty package
munin_master_stub/CSWmuninmaster created that depends on
munin_master/CSWmunin-master.  The benefit to the user is that the
catalog name they are used to using stays the same.  The dependencies
ensure that anyone with CSWmuninmaster will get the new (stub) package
and also the new (real) CSWmunin-master.

You can do this for the other packages to sanitize the names as well.

(Note that my preference is to use _ and - to separate the name parts
but that doesn't mean you have to do it that way if you prefer
muninmaster/munincommon, etc.)

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From jesse at opencsw.org  Mon Sep  5 01:39:49 2011
From: jesse at opencsw.org (Jesse Reynolds)
Date: Mon, 5 Sep 2011 09:09:49 +0930
Subject: [csw-maintainers] dropping support for solaris 9?
In-Reply-To: <1315149086-sup-7658@pinkfloyd.chass.utoronto.ca>
References: <1315149086-sup-7658@pinkfloyd.chass.utoronto.ca>
Message-ID: <CAHiP+x_JAdvU+cvhY6rXmJqchXnp2J82uL-eRyrh-HQ=PUGeDg@mail.gmail.com>

Are there any stats on how widely OpenCSW is used? And what proportion on
Solaris 9?

Personally, I think it makes sense to drop support for Solaris 9 when Oracle
do. But the Solaris 9 frozen package archive should remain online, and easy
instructions given on the website of how to point your solaris 9 boxes at it
(though with warnings that there's going to be no maintenance for them,
other than DIY).

On 5 September 2011 00:53, Ben Walton <bwalton at opencsw.org> wrote:

>
> Hi All,
>
> The premier support of Solaris 9 ends in October[1] of this year.  How
> do people feel about dropping build support for it and moving to
> Solaris 10 and 11 only?
>
> My thinking is that we should drop it on the same date as Oracle to
> avoid the situation we had with Solaris 8 where we were building
> packages for it _way_ after the 'best before' date.
>
> What do others think?
>
> (I added this as a dicussion item for the Kiel Summercamp too.)
>
> Thanks
> -Ben
>
> [1] Page 30 of:
> http://www.oracle.com/us/support/library/lifetime-support-hardware-os-337182.pdf
> --
> Ben Walton
> Systems Programmer - CHASS
> University of Toronto
> C:416.407.5610 | W:416.978.4302
>
> _______________________________________________
> maintainers mailing list
> maintainers at lists.opencsw.org
> https://lists.opencsw.org/mailman/listinfo/maintainers
> .:: This mailing list's archive is public. ::.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20110905/c2820eff/attachment-0001.html>

From maciej at opencsw.org  Mon Sep  5 01:44:43 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=)
Date: Mon, 5 Sep 2011 00:44:43 +0100
Subject: [csw-maintainers] Catalog layout
In-Reply-To: <1315156495-sup-906@pinkfloyd.chass.utoronto.ca>
References: <CALtRa-79EXWEJ6CGWb9OU_NUXfH96mQP0TXDFiC8s7Z2kCgUFw@mail.gmail.com>
	<1315156495-sup-906@pinkfloyd.chass.utoronto.ca>
Message-ID: <CALtRa-7KzSpGJmNL4QsgZDYNDDxpyo9PSHqBxZyhF8EjOqhv=Q@mail.gmail.com>

2011/9/4 Ben Walton <bwalton at opencsw.org>:
> Excerpts from Maciej Blizi?ski's message of Sat Sep 03 06:00:44 -0400 2011:
>
> Hi Maciej,
>
>> http://mirror.opencsw.org/opencsw-future/snapshots/
>
> I think the one benefit these could provide is a mechanism to gather a
> bit of historical information for stats purposes. ?It would be 'gappy'
> as it relies on the interval. ?The shorter the interval, the heavier
> the weight of keeping the snapshots.
>
> I think that statistical info is better handled by William's tools, so
> I'm not sure that the snapshots are useful.

Having to look at an older version of a catalog is rather an
exceptional usage.  For that, a separate space on mirror.opencsw.org,
not propagated to other mirrors, should be enough.

> Is there another intended use for them?

I wouldn't plan any.  Snapshots don't play any role in the release
process, because they've been replaced by named releases.

Maciej

From jesse at opencsw.org  Mon Sep  5 01:48:55 2011
From: jesse at opencsw.org (Jesse Reynolds)
Date: Mon, 5 Sep 2011 09:18:55 +0930
Subject: [csw-maintainers] Catalog layout
In-Reply-To: <CALtRa-79EXWEJ6CGWb9OU_NUXfH96mQP0TXDFiC8s7Z2kCgUFw@mail.gmail.com>
References: <CALtRa-79EXWEJ6CGWb9OU_NUXfH96mQP0TXDFiC8s7Z2kCgUFw@mail.gmail.com>
Message-ID: <CAHiP+x-p7bZ9xs7Zcu6LGHEzc244s+Tu-ZjK9dm4HD8jA9V6+Q@mail.gmail.com>

2011/9/3 Maciej Blizi?ski <maciej at opencsw.org>


> eventually promoted to stable.  But we've come up with the idea of
> named releases, which I think is a much better one.
>
>
Roughly how often will the named releases be made?

I like how pkgsrc do quarterly releases, named like "2011Q3". So you can set
up a machine against one of these releases and later on add more packages
from it without upgrading dependencies that you're now relying on. Quarterly
seems like a good kind of schedule.

Jesse
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20110905/3000d053/attachment.html>

From maciej at opencsw.org  Mon Sep  5 09:04:56 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=)
Date: Mon, 5 Sep 2011 08:04:56 +0100
Subject: [csw-maintainers] Catalog layout
In-Reply-To: <CAHiP+x-p7bZ9xs7Zcu6LGHEzc244s+Tu-ZjK9dm4HD8jA9V6+Q@mail.gmail.com>
References: <CALtRa-79EXWEJ6CGWb9OU_NUXfH96mQP0TXDFiC8s7Z2kCgUFw@mail.gmail.com>
	<CAHiP+x-p7bZ9xs7Zcu6LGHEzc244s+Tu-ZjK9dm4HD8jA9V6+Q@mail.gmail.com>
Message-ID: <CALtRa-6P=svjWYVeOxrJnsFeRV=BZrBnZQK9GycSUEom63eGGg@mail.gmail.com>

2011/9/5 Jesse Reynolds <jesse at opencsw.org>:
>
>
> 2011/9/3 Maciej Blizi?ski <maciej at opencsw.org>
>
>>
>> eventually promoted to stable. ?But we've come up with the idea of
>> named releases, which I think is a much better one.
>>
>
> Roughly how often will the named releases be made?
> I like how pkgsrc do quarterly releases, named like "2011Q3". So you can set
> up a machine against one of these releases and later on add more packages
> from it without upgrading dependencies that you're now relying on. Quarterly
> seems like a good kind of schedule.

We were planning on aligning releases with summer and wintercamps,
which gives us one release every 6 months.

Maciej

From jesse at opencsw.org  Mon Sep  5 09:16:30 2011
From: jesse at opencsw.org (Jesse Reynolds)
Date: Mon, 5 Sep 2011 16:46:30 +0930
Subject: [csw-maintainers] Catalog layout
In-Reply-To: <CALtRa-6P=svjWYVeOxrJnsFeRV=BZrBnZQK9GycSUEom63eGGg@mail.gmail.com>
References: <CALtRa-79EXWEJ6CGWb9OU_NUXfH96mQP0TXDFiC8s7Z2kCgUFw@mail.gmail.com>
	<CAHiP+x-p7bZ9xs7Zcu6LGHEzc244s+Tu-ZjK9dm4HD8jA9V6+Q@mail.gmail.com>
	<CALtRa-6P=svjWYVeOxrJnsFeRV=BZrBnZQK9GycSUEom63eGGg@mail.gmail.com>
Message-ID: <CAHiP+x89g_q5xA96y+-h2N8zg+21-zXqvggMhZ48zLLqWdzSMg@mail.gmail.com>

2011/9/5 Maciej Blizi?ski <maciej at opencsw.org>

> > Roughly how often will the named releases be made?
> > I like how pkgsrc do quarterly releases, named like "2011Q3". So you can
> set
> > up a machine against one of these releases and later on add more packages
> > from it without upgrading dependencies that you're now relying on.
> Quarterly
> > seems like a good kind of schedule.
>
> We were planning on aligning releases with summer and wintercamps,
> which gives us one release every 6 months.
>

Makes sense, sounds good.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20110905/761adfe0/attachment.html>

From bwalton at opencsw.org  Mon Sep  5 15:12:51 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Mon, 05 Sep 2011 09:12:51 -0400
Subject: [csw-maintainers] dropping support for solaris 9?
In-Reply-To: <CAHiP+x_JAdvU+cvhY6rXmJqchXnp2J82uL-eRyrh-HQ=PUGeDg@mail.gmail.com>
References: <1315149086-sup-7658@pinkfloyd.chass.utoronto.ca>
	<CAHiP+x_JAdvU+cvhY6rXmJqchXnp2J82uL-eRyrh-HQ=PUGeDg@mail.gmail.com>
Message-ID: <1315227818-sup-2205@pinkfloyd.chass.utoronto.ca>

Excerpts from Jesse Reynolds's message of Sun Sep 04 19:39:49 -0400 2011:

Hi Jesse,

> Are there any stats on how widely OpenCSW is used? And what
> proportion on Solaris 9?

We don't have good mirror stats that I'm aware of.  We used to get
stats from ibiblio but after being moved into the 'high volume' area
we lost that.

> Personally, I think it makes sense to drop support for Solaris 9
> when Oracle do. But the Solaris 9 frozen package archive should
> remain online, and easy instructions given on the website of how to
> point your solaris 9 boxes at it (though with warnings that there's
> going to be no maintenance for them, other than DIY).

This is the approach we took for dropping Solaris 8.  We didn't remove
the archive (and still have no plans to do so) so that anyone wishing
to[1] can still fetch packages from it.  We'd certainly do this with
9.  There is no benefit to be gained from dropping the package archives.

Also, dropping official support does not preclude building packages
for it at need/want.  Most people will abandon 9 for builds when we
mark it unsupported, but a few packages will likely still be built for
it.  I think Peter B still builds pkgutil packages for 8.  The key is
that you, as a maintainer, are no longer bound to build for it doing
10-only packages in edge cases.

We skipped from 8 to 10 here with 0 deployments of 9 and my impression
is that the many sites did it this way.  This leads me to think that
dropping 9 will have less impact than when we dropped 8 (even a year
after EOL).  I have no numbers to back this up though.

Thanks
-Ben

[1] I recently added mutt to a legacy box for a colleague.
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From bwalton at opencsw.org  Mon Sep  5 15:14:53 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Mon, 05 Sep 2011 09:14:53 -0400
Subject: [csw-maintainers] [offtopic] git survey
Message-ID: <1315228428-sup-2956@pinkfloyd.chass.utoronto.ca>


Hi All,

As many of you are git users, you may be interested in completing the
yearly survey: https://git.wiki.kernel.org/index.php/GitSurvey2011

The intent is to help the developers focus on areas that users
indicate as painful or lacking.

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From bonivart at opencsw.org  Mon Sep  5 16:14:51 2011
From: bonivart at opencsw.org (Peter Bonivart)
Date: Mon, 5 Sep 2011 16:14:51 +0200
Subject: [csw-maintainers] dropping support for solaris 9?
In-Reply-To: <1315227818-sup-2205@pinkfloyd.chass.utoronto.ca>
References: <1315149086-sup-7658@pinkfloyd.chass.utoronto.ca>
	<CAHiP+x_JAdvU+cvhY6rXmJqchXnp2J82uL-eRyrh-HQ=PUGeDg@mail.gmail.com>
	<1315227818-sup-2205@pinkfloyd.chass.utoronto.ca>
Message-ID: <CABY0g1WncU+Hn-5GDSYTqEHrLcRFBZvfrkt_RHdf1ohiCu+bSw@mail.gmail.com>

On Mon, Sep 5, 2011 at 3:12 PM, Ben Walton <bwalton at opencsw.org> wrote:
> Also, dropping official support does not preclude building packages
> for it at need/want. ?Most people will abandon 9 for builds when we
> mark it unsupported, but a few packages will likely still be built for
> it. ?I think Peter B still builds pkgutil packages for 8. ?The key is
> that you, as a maintainer, are no longer bound to build for it doing
> 10-only packages in edge cases.

The build hosts may be available yet but it's much harder to build
packages for Solaris 8 now than it used to be since we also dropped
support for Solaris 8 in our own tool chain. It's impossible to run
modern GAR/checkpkg on the Solaris 8 build hosts. Also I have failed
in more ways than I can count to upload Solaris 8 packages to our
catalogs.

If we are to support Solaris 9 (and maybe even 8) in a limited way
there should still be a way to get those packages to our users in a
way that is not totally exhausting. Some verified documentation should
exist on how to proceed.

In general I'm all for dropping Solaris 9 after October though.

/peter

From bwalton at opencsw.org  Mon Sep  5 19:13:40 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Mon, 05 Sep 2011 13:13:40 -0400
Subject: [csw-maintainers] the future of pkg-get...
Message-ID: <1315241773-sup-2057@pinkfloyd.chass.utoronto.ca>


Hi All,

We noticed the following tweet in the irc ceeswi feed today and it
started a discussion about what to do with pkg-get:

--snip--
opencsw at twitter: Solaris joys. I'd forgotten than OpenCSW can screw
itself in the middle of an upgrade by removing wget/ssl.  Guess how I
was reminded :(
--snip--

As this is a problem that would affect pkg-get, but not pkgutil due to
the operations ordering, we started discussing options.  Some of the
options are:


1. Provide a new pkg_get package that bails with a 'Please install
   pkgutil' message unless the arguments are '-i pkgutil'
2. Provide a new pkg_get package that bails in every case with a
   'Please install pkgutil' message.
3. Have pkgutil provide pkg_get_stub/CSWpkgget thus obsoleting pkg_get
   in favour of pkgutil.
4. Leave it as is.

My preference would be either 1 or 2 as I think that people hitting
issues like those in the tweet do more harm than good to OpenCSW's
reputation.  Both of these options could be implemented with a wrapper
around pkg-get.real to allow a determined site to continue using
pkg-get if they want.

The third option, while superficially attractive, would leave people
without anything responding to pkg-get and shouldn't be considered
seriously in my opinion.  (I guess CSWpkgutil could provide a
replacement for pkg-get...implementing option 1 or 2, but I still
don't think this is the best path.)

The fourth option is status quo and harmful to users in the long run,
in my opinion.

What do you folks think?  Are there other better options?

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From dam at opencsw.org  Mon Sep  5 22:00:01 2011
From: dam at opencsw.org (Dagobert Michelsen)
Date: Mon, 5 Sep 2011 22:00:01 +0200
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <1315241773-sup-2057@pinkfloyd.chass.utoronto.ca>
References: <1315241773-sup-2057@pinkfloyd.chass.utoronto.ca>
Message-ID: <C8F1AF98-2F15-4F74-9221-72D67BB8DB72@opencsw.org>

Hi Ben,

Am 05.09.2011 um 19:13 schrieb Ben Walton:
> We noticed the following tweet in the irc ceeswi feed today and it
> started a discussion about what to do with pkg-get:
> 
> --snip--
> opencsw at twitter: Solaris joys. I'd forgotten than OpenCSW can screw
> itself in the middle of an upgrade by removing wget/ssl.  Guess how I
> was reminded :(
> --snip--
> 
> As this is a problem that would affect pkg-get, but not pkgutil due to
> the operations ordering, we started discussing options.  Some of the
> options are:
> 
> 
> 1. Provide a new pkg_get package that bails with a 'Please install
>   pkgutil' message unless the arguments are '-i pkgutil'
> 2. Provide a new pkg_get package that bails in every case with a
>   'Please install pkgutil' message.

And that it is deprecated.

> 3. Have pkgutil provide pkg_get_stub/CSWpkgget thus obsoleting pkg_get
>   in favour of pkgutil.
> 4. Leave it as is.
> 
> My preference would be either 1 or 2 as I think that people hitting
> issues like those in the tweet do more harm than good to OpenCSW's
> reputation.  Both of these options could be implemented with a wrapper
> around pkg-get.real to allow a determined site to continue using
> pkg-get if they want.
> 
> The third option, while superficially attractive, would leave people
> without anything responding to pkg-get and shouldn't be considered
> seriously in my opinion.  (I guess CSWpkgutil could provide a
> replacement for pkg-get...implementing option 1 or 2, but I still
> don't think this is the best path.)

pkg_get_stub could provide a message of the type "2".

> The fourth option is status quo and harmful to users in the long run,
> in my opinion.
> 
> What do you folks think?  Are there other better options?

I would go with a combination of 2 and 3.


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


From bwalton at opencsw.org  Mon Sep  5 22:12:10 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Mon, 05 Sep 2011 16:12:10 -0400
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <C8F1AF98-2F15-4F74-9221-72D67BB8DB72@opencsw.org>
References: <1315241773-sup-2057@pinkfloyd.chass.utoronto.ca>
	<C8F1AF98-2F15-4F74-9221-72D67BB8DB72@opencsw.org>
Message-ID: <1315253472-sup-9970@pinkfloyd.chass.utoronto.ca>

Excerpts from Dagobert Michelsen's message of Mon Sep 05 16:00:01 -0400 2011:
> Hi Ben,

> pkg_get_stub could provide a message of the type "2".

Wouldn't this be too easy to miss in the output?  Or are you saying
that the _stub package should deliver a single file with a script
capable of dumping this message in addition to pulling in pkgutil?

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From dam at opencsw.org  Mon Sep  5 22:14:03 2011
From: dam at opencsw.org (Dagobert Michelsen)
Date: Mon, 5 Sep 2011 22:14:03 +0200
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <1315253472-sup-9970@pinkfloyd.chass.utoronto.ca>
References: <1315241773-sup-2057@pinkfloyd.chass.utoronto.ca>
	<C8F1AF98-2F15-4F74-9221-72D67BB8DB72@opencsw.org>
	<1315253472-sup-9970@pinkfloyd.chass.utoronto.ca>
Message-ID: <73328001-D783-4032-9FF9-FA81A41B4F9F@opencsw.org>

Hi Ben,

Am 05.09.2011 um 22:12 schrieb Ben Walton:
> Excerpts from Dagobert Michelsen's message of Mon Sep 05 16:00:01 -0400 2011:
>> Hi Ben,
> 
>> pkg_get_stub could provide a message of the type "2".
> 
> Wouldn't this be too easy to miss in the output?  Or are you saying
> that the _stub package should deliver a single file with a script
> capable of dumping this message in addition to pulling in pkgutil?

Yes, pkg_get_stub has a file /opt/csw/bin/pkg-get which does

#!/bin/sh

echo <<EOF
The use of pkg-get is deprecated. Please use pkgutil(1) instead.
EOF

exit 1


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


From bwalton at opencsw.org  Mon Sep  5 22:20:12 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Mon, 05 Sep 2011 16:20:12 -0400
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <73328001-D783-4032-9FF9-FA81A41B4F9F@opencsw.org>
References: <1315241773-sup-2057@pinkfloyd.chass.utoronto.ca>
	<C8F1AF98-2F15-4F74-9221-72D67BB8DB72@opencsw.org>
	<1315253472-sup-9970@pinkfloyd.chass.utoronto.ca>
	<73328001-D783-4032-9FF9-FA81A41B4F9F@opencsw.org>
Message-ID: <1315253759-sup-2517@pinkfloyd.chass.utoronto.ca>

Excerpts from Dagobert Michelsen's message of Mon Sep 05 16:14:03 -0400 2011:

Hi Dago,

> >> pkg_get_stub could provide a message of the type "2".
> > 
> > Wouldn't this be too easy to miss in the output?  Or are you
> > saying that the _stub package should deliver a single file with a
> > script capable of dumping this message in addition to pulling in
> > pkgutil?
> 
> Yes, pkg_get_stub has a file /opt/csw/bin/pkg-get which does
> 
> #!/bin/sh
> 
> echo <<EOF
> The use of pkg-get is deprecated. Please use pkgutil(1) instead.
> EOF
> 
> exit 1

Well, this would meet my expectations for full deprecation without
leaving the user without any explanation.  It's slightly abnormal to
ship a _stub with 'real' content, but I think it only enhances the
experience in this case so I'm ok with it.

Anyone else?

Thanks
-Ben

--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From bwalton at opencsw.org  Tue Sep  6 01:42:19 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Mon, 05 Sep 2011 19:42:19 -0400
Subject: [csw-maintainers] catalog fun
In-Reply-To: <CALtRa-7mPmf=2q5w4PCdvX4Dkd45sch9JkRkBbVX-EmEayK9pg@mail.gmail.com>
References: <1314931865-sup-91@pinkfloyd.chass.utoronto.ca>
	<CALtRa-7mPmf=2q5w4PCdvX4Dkd45sch9JkRkBbVX-EmEayK9pg@mail.gmail.com>
Message-ID: <1315265150-sup-3348@pinkfloyd.chass.utoronto.ca>

Excerpts from Maciej Blizi?ski's message of Sun Sep 04 03:40:41 -0400 2011:

> > This is a technically valid catalog as all dependencies are met
> > (chkcat should be happy). ?I'm currently detecting this as a "Silent
> > Name Change." ?This is an instance of 'un-stubbing' which I think
> > should be considered an error. ?What do others think?
> 
> In general, is catalogname change with no pkgname change an error?

I think we've generally treated this as an error condition.  A package
name change was (and is) worse since that is what Solaris itself cares
about, but we've tried to avoid catalog name changes.

> > In this specific case, was the name change intentional? ?It looks a
> > bit funny to me to start calling CSWpmdbi pm_dbi2 (version number is
> > 1.616) all of a sudden after stubbing it out. ?Can someone provide
> > insight on this?
> 
> I vaguely remember that a more complicated rename case required you
> to change the catalogname where you didn't want to, and that the
> number 2 was used.  I don't recall the specifics, it was something
> like two renames of the same package.

In cases where we do want to allow this, the tool will need an 'ignore
errors on foo' option so that it can be driven manually.  As most
errors will halt the mirror push, this would allow us to register
changes in the catalog, cache this catalog and then have the rest of
the job re-run.

Thanks
-Ben

--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From maciej at opencsw.org  Tue Sep  6 18:48:55 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=)
Date: Tue, 6 Sep 2011 17:48:55 +0100
Subject: [csw-maintainers] GCC 4.6 progress
In-Reply-To: <CALtRa-6Vb0u34sE7NHX1Ca4mDBMY3kyt3CfnGWpQO37GV-d5-w@mail.gmail.com>
References: <CALtRa-6Ho-vowyruOnhysuY4njq5CE98Hr3_WgyHDBUM2tKPEg@mail.gmail.com>
	<CALtRa-7i5B1APocaBRRLe8C-BMGwpzRJEHMSVP=_voOUmHqmsw@mail.gmail.com>
	<CALtRa-6K7FFdhKHfm1eK-vcz9xY=ek-g_9UYQ93UoNd05YXvQQ@mail.gmail.com>
	<CALtRa-7kNA7wUhjJLwgsid7+W4Kx1esXuyag=9yibdyvCayPBg@mail.gmail.com>
	<CALtRa-7xzHQBv6ZHM=iwXONDLGJeWebGjdS9dTbNZYCZ-c_KEA@mail.gmail.com>
	<x6aabak74x.fsf@opencsw.org>
	<CALtRa-6xLfut0JtQEtP=kZHL371X7JDX5jUkJiezwWXj7Kvf7w@mail.gmail.com>
	<x662lyk0ds.fsf@opencsw.org>
	<CALtRa-6X6mJYy9wWpx-mmpO5X+rRY35+eN4+zM53_MFJ6KA7fQ@mail.gmail.com>
	<CALtRa-70hROnmkr-TTyrTbt54xFzaRn54jCOn8PSpS3fwLEJJA@mail.gmail.com>
	<CALtRa-5bPYfprBKH++cW8wN+q8e08WZ7eH5e6OGaD_eQ6-t_fA@mail.gmail.com>
	<DE8738C4-7BC7-4597-A1BF-BDB097FEECC6@opencsw.org>
	<CALtRa-6Vb0u34sE7NHX1Ca4mDBMY3kyt3CfnGWpQO37GV-d5-w@mail.gmail.com>
Message-ID: <CALtRa-57epz9gHyfNVzAGELa-7Km_Jxab2cRAYu0mWm5sBdKQw@mail.gmail.com>

I'm currently stuck.  The problem is that the gcc build does not pass
the -R/opt/csw/lib flag when linking libstdc++.so.6, and in effect
libstdc++.so.6 is not able (on its own) find libgcc_s.so.1. The same
problem applies to many other shared libraries.

One way of going about it would be to override the errors.  GCC
developers say that everything that depends on libstdc++.so.6 also
depends on libgcc_s.so.1, so libstdc++.so.6 will be always found.  But
this means that this library is found by coincidence, and I don't want
our dynamic linking depend on coincidences.

When I talked to gcc-help, they told me I'm nuts[1], but they also
provided some information[2].  However, they didn't provide a solution
that would be satisfactory for me.  What I'm looking for is passing
-R/opt/csw/lib when linking shared libraries.  Unfortunately, the gcc
build system is quite complex, where there are multiple subinvocations
of ./configure inside subdirectories during a single phase, and there
are three building phases.  It's quite hard to figure out what exact
inputs influence the outcome.

To facilitate looking for the problem, I created a special branch
which only has c and c++ frontends enabled (for quicker compilation).
If you check out the code and build it, you'll see soname-not-found
errors from checkpkg.  When you run /usr/ccs/bin/dump -Lv against the
libstdc++.so.6 file, you'll see that RPATH is missing. We need to put
it there.

I've already tried using LDFLAGS, --with-boot-ldflags,
LDFLAGS_FOR_TARGET and LD_OPTIONS, nothing worked.

If there's anyone with good knowledge of the GCC build system, I would
greatly appreciate any help. To get started:

svn co https://gar.svn.sourceforge.net/svnroot/gar/csw/mgar/pkg/gcc4/branches/ldflags-problem
cd ldflags-problem
mgar package

Maciej

[1] http://gcc.gnu.org/ml/gcc-help/2011-09/msg00028.html
[2] http://gcc.gnu.org/ml/gcc-help/2011-09/msg00038.html
[3] https://gar.svn.sourceforge.net/svnroot/gar/csw/mgar/pkg/gcc4/branches/ldflags-problem/

From bwalton at opencsw.org  Wed Sep  7 04:27:06 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Tue, 06 Sep 2011 22:27:06 -0400
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <1315253759-sup-2517@pinkfloyd.chass.utoronto.ca>
References: <1315241773-sup-2057@pinkfloyd.chass.utoronto.ca>
	<C8F1AF98-2F15-4F74-9221-72D67BB8DB72@opencsw.org>
	<1315253472-sup-9970@pinkfloyd.chass.utoronto.ca>
	<73328001-D783-4032-9FF9-FA81A41B4F9F@opencsw.org>
	<1315253759-sup-2517@pinkfloyd.chass.utoronto.ca>
Message-ID: <1315362400-sup-2443@pinkfloyd.chass.utoronto.ca>

Excerpts from Ben Walton's message of Mon Sep 05 16:20:12 -0400 2011:

> Well, this would meet my expectations for full deprecation without
> leaving the user without any explanation.  It's slightly abnormal to
> ship a _stub with 'real' content, but I think it only enhances the
> experience in this case so I'm ok with it.

See: http://buildfarm.opencsw.org/experimental.html#pkgget

I've tested an update using pkg-get and it does pull in the stub
properly.  Shall we announce and release this?

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From dam at opencsw.org  Wed Sep  7 16:42:00 2011
From: dam at opencsw.org (Dagobert Michelsen)
Date: Wed, 7 Sep 2011 16:42:00 +0200
Subject: [csw-maintainers] Housekeeping Summercamp in Kiel
Message-ID: <F1A6BF7E-0842-4062-AFAF-1AB7DF07370F@opencsw.org>

Hi folks,

summercamp is nearing and I have a couple of things to organize:

1. Shirts - who wants one?

2. Touristic program: If we want to visit the computer museum or GetDigital I need to book
   a tour some time in advance. We could also just wait up and see if there is enough time
   left, but I can't guarantee a guided tour then.


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


From maciej at opencsw.org  Wed Sep  7 17:29:46 2011
From: maciej at opencsw.org (Maciej (Matchek) Blizinski)
Date: Wed, 7 Sep 2011 16:29:46 +0100
Subject: [csw-maintainers] RFC: idea to unify 32/64 bit headers
In-Reply-To: <8DB9CB2C-0B8E-44B5-86F2-CE2568CA53CA@opencsw.org>
References: <F4E16D0A-4251-4270-954A-112D0BDF0AFE@baltic-online.de>
	<8DB9CB2C-0B8E-44B5-86F2-CE2568CA53CA@opencsw.org>
Message-ID: <CADHRADCjjpf2yQBx=xNE_c+n48KH=3AUvuz3jHm7Tza_4UXKXw@mail.gmail.com>

No dia 23 de Agosto de 2010 20:49, Dagobert Michelsen
<dam at opencsw.org> escreveu:
> If you do
> ?diff -D __amd64 curlbuild-32.h curlbuild-64.h
> It will generate an include file where the differences only in the second
> file will be shielded by C preprocessor ifdefs with the string after the -D.
> I like this that much that I am really thinking of making this fully
> automatic: On merge GAR currently just copies over the default (32 bit)
> modulation. I could just merge over the diff'ed 32/64 between the
> default 32 bit ISA and 64 bit ISA easily making these special things
> obsolete.
>
> Thoughts?

I'm definitely for it.  Our libgmp build can serve as a testbed.  I'd
be also willing to write some code to facilitate this.  How would you
envision the implementation, Dago?

Maciej

From maciej at opencsw.org  Wed Sep  7 19:47:29 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=)
Date: Wed, 7 Sep 2011 18:47:29 +0100
Subject: [csw-maintainers] Housekeeping Summercamp in Kiel
In-Reply-To: <F1A6BF7E-0842-4062-AFAF-1AB7DF07370F@opencsw.org>
References: <F1A6BF7E-0842-4062-AFAF-1AB7DF07370F@opencsw.org>
Message-ID: <CALtRa-5-1FbywvXU6cYGAruMKvtLz+D8N91DMH9FfroJLBgOoA@mail.gmail.com>

I'm up for both. I want one more t-shirt! When would be the trip to the
museum?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20110907/7770d7a8/attachment.html>

From maciej at opencsw.org  Wed Sep  7 22:41:01 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=)
Date: Wed, 7 Sep 2011 21:41:01 +0100
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <73328001-D783-4032-9FF9-FA81A41B4F9F@opencsw.org>
References: <1315241773-sup-2057@pinkfloyd.chass.utoronto.ca>
	<C8F1AF98-2F15-4F74-9221-72D67BB8DB72@opencsw.org>
	<1315253472-sup-9970@pinkfloyd.chass.utoronto.ca>
	<73328001-D783-4032-9FF9-FA81A41B4F9F@opencsw.org>
Message-ID: <CALtRa-5=fbjVv2wot_pZQEwBbuucxLBXVQghDc9n5M1ib1wqEw@mail.gmail.com>

2011/9/5 Dagobert Michelsen <dam at opencsw.org>:
> Hi Ben,
>
> Am 05.09.2011 um 22:12 schrieb Ben Walton:
>> Excerpts from Dagobert Michelsen's message of Mon Sep 05 16:00:01 -0400 2011:
>>> Hi Ben,
>>
>>> pkg_get_stub could provide a message of the type "2".
>>
>> Wouldn't this be too easy to miss in the output? ?Or are you saying
>> that the _stub package should deliver a single file with a script
>> capable of dumping this message in addition to pulling in pkgutil?
>
> Yes, pkg_get_stub has a file /opt/csw/bin/pkg-get which does
>
> #!/bin/sh
>
> echo <<EOF
> The use of pkg-get is deprecated. Please use pkgutil(1) instead.
> EOF
>
> exit 1

I was thinking about a scenario where alternatives are used.  The
default implementation would be the one cited above, and the second
choice would be the original pkg-get, which you would choose if you
really really wanted to.  This way, we get people to understand what's
going on, but we don't take away the ability to use the tool.

Maciej

From bwalton at opencsw.org  Thu Sep  8 02:46:08 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Wed, 07 Sep 2011 20:46:08 -0400
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <CALtRa-5=fbjVv2wot_pZQEwBbuucxLBXVQghDc9n5M1ib1wqEw@mail.gmail.com>
References: <1315241773-sup-2057@pinkfloyd.chass.utoronto.ca>
	<C8F1AF98-2F15-4F74-9221-72D67BB8DB72@opencsw.org>
	<1315253472-sup-9970@pinkfloyd.chass.utoronto.ca>
	<73328001-D783-4032-9FF9-FA81A41B4F9F@opencsw.org>
	<CALtRa-5=fbjVv2wot_pZQEwBbuucxLBXVQghDc9n5M1ib1wqEw@mail.gmail.com>
Message-ID: <1315442673-sup-4404@pinkfloyd.chass.utoronto.ca>

Excerpts from Maciej Blizi?ski's message of Wed Sep 07 16:41:01 -0400 2011:

> I was thinking about a scenario where alternatives are used.  The
> default implementation would be the one cited above, and the second
> choice would be the original pkg-get, which you would choose if you
> really really wanted to.  This way, we get people to understand
> what's going on, but we don't take away the ability to use the tool.

Or we could just place the working tool as
/opt/csw/bin/pkg-get.deprecated (unsupported?) and require people to
use it with that name if they want it still?

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From igalic at opencsw.org  Thu Sep  8 08:23:34 2011
From: igalic at opencsw.org (Igor =?utf-8?Q?Gali=C4=87?=)
Date: Thu, 08 Sep 2011 06:23:34 -0000 (UTC)
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <ae51fa1d-8dbc-4d5c-a597-21022547bb28@iris>
Message-ID: <a3e2ffdb-1dc4-4829-972d-67d419014151@iris>



----- Original Message -----
> Excerpts from Maciej Blizi?ski's message of Wed Sep 07 16:41:01 -0400
> 2011:
>
> > I was thinking about a scenario where alternatives are used.  The
> > default implementation would be the one cited above, and the second
> > choice would be the original pkg-get, which you would choose if you
> > really really wanted to.  This way, we get people to understand
> > what's going on, but we don't take away the ability to use the
> > tool.
>
> Or we could just place the working tool as
> /opt/csw/bin/pkg-get.deprecated (unsupported?) and require people to
> use it with that name if they want it still?

Would this option still include a pkg_get_stub ?

> Thanks
> -Ben
> --
> Ben Walton
> Systems Programmer - CHASS
> University of Toronto
> C:416.407.5610 | W:416.978.4302

i

--
Igor Gali?

Tel: +43 (0) 664 886 22 883
Mail: i.galic at brainsware.org
URL: http://brainsware.org/
GPG: 571B 8B8A FC97 266D BDA3  EF6F 43AD 80A4 5779 3257

From igalic at opencsw.org  Thu Sep  8 08:24:10 2011
From: igalic at opencsw.org (Igor =?utf-8?Q?Gali=C4=87?=)
Date: Thu, 08 Sep 2011 06:24:10 -0000 (UTC)
Subject: [csw-maintainers] RFC: idea to unify 32/64 bit headers
In-Reply-To: <c49b02b5-c4e0-46df-8111-026346ea9565@iris>
Message-ID: <5b1893f0-736c-4705-8b6c-aa93b69c481a@iris>



----- Original Message -----
> No dia 23 de Agosto de 2010 20:49, Dagobert Michelsen
> <dam at opencsw.org> escreveu:
> > If you do
> > ?diff -D __amd64 curlbuild-32.h curlbuild-64.h
> > It will generate an include file where the differences only in the
> > second
> > file will be shielded by C preprocessor ifdefs with the string
> > after the -D.
> > I like this that much that I am really thinking of making this
> > fully
> > automatic: On merge GAR currently just copies over the default (32
> > bit)
> > modulation. I could just merge over the diff'ed 32/64 between the
> > default 32 bit ISA and 64 bit ISA easily making these special
> > things
> > obsolete.
> >
> > Thoughts?

Two thoughts: +1
And: Which headers are currently included?

> I'm definitely for it.  Our libgmp build can serve as a testbed.  I'd
> be also willing to write some code to facilitate this.  How would you
> envision the implementation, Dago?

I just tried this out in the shell..

igalic at unstable10x ...ar/pkg/hwloc/trunk/work/solaris9-i386 % for f in $( find install-isa-i386/opt/csw/include/ -type f ) ; do
x86="${f}"
amd64="${f/install-isa-i386/install-isa-amd64}"
diff -D __amd64 "${x86}" "${amd64}"
done

And found some rather disturbing things

/* Defined to 1 if you have the <stdint.h> header file. */
#ifndef __amd64
/* #  undef HWLOC_HAVE_STDINT_H */
#else /* __amd64 */
#  define HWLOC_HAVE_STDINT_H 1
#endif /* __amd64 */


> Maciej

i

--
Igor Gali?

Tel: +43 (0) 664 886 22 883
Mail: i.galic at brainsware.org
URL: http://brainsware.org/
GPG: 571B 8B8A FC97 266D BDA3  EF6F 43AD 80A4 5779 3257

From bonivart at opencsw.org  Thu Sep  8 09:34:17 2011
From: bonivart at opencsw.org (Peter Bonivart)
Date: Thu, 8 Sep 2011 09:34:17 +0200
Subject: [csw-maintainers] Housekeeping Summercamp in Kiel
In-Reply-To: <F1A6BF7E-0842-4062-AFAF-1AB7DF07370F@opencsw.org>
References: <F1A6BF7E-0842-4062-AFAF-1AB7DF07370F@opencsw.org>
Message-ID: <CABY0g1Wzd=oG3W+FR5T=5=WwE=OWCvZdyRxkArC68UWPFtn_hA@mail.gmail.com>

On Wed, Sep 7, 2011 at 4:42 PM, Dagobert Michelsen <dam at opencsw.org> wrote:
> Hi folks,
>
> summercamp is nearing and I have a couple of things to organize:
>
> 1. Shirts - who wants one?

One large for me please. :)

> 2. Touristic program: If we want to visit the computer museum or GetDigital I need to book
> ? a tour some time in advance. We could also just wait up and see if there is enough time
> ? left, but I can't guarantee a guided tour then.

I see this on the wiki already, cool!

/peter

From bwalton at opencsw.org  Thu Sep  8 12:26:06 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Thu, 08 Sep 2011 06:26:06 -0400
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <a3e2ffdb-1dc4-4829-972d-67d419014151@iris>
References: <a3e2ffdb-1dc4-4829-972d-67d419014151@iris>
Message-ID: <472d8e31-144d-40ae-b467-8f2a2afe3a3c@email.android.com>

If it will deliver working functionality (and the man page) I don't think it should be named stub.

So: alternatives, no alternatives but working functionality or stub with deprecation notice binary?

Thanks
-Ben

"Igor Gali?" <igalic at opencsw.org> wrote:



----- Original Message -----
> Excerpts from Maciej Blizi?ski's message of Wed Sep 07 16:41:01 -0400
> 2011:
>
> > I was thinking about a scenario where alternatives are used. The
> > default implementation would be the one cited above, and the second
> > choice would be the original pkg-get, which you would choose if you
> > really really wanted to. This way, we get people to understand
> > what's going on, but we don't take away the ability to use the
> > tool.
>
> Or we could just place the working tool as
> /opt/csw/bin/pkg-get.deprecated (unsupported?) and require people to
> use it with that name if they want it still?

Would this option still include a pkg_get_stub ?

> Thanks
> -Ben
> --
> Ben Walton
> Systems Programmer - CHASS
> University of Toronto
> C:416.407.5610 | W:416.978.4302

i

--
Igor Gali?

Tel: +43 (0) 664 886 22 883
Mail: i.galic at brainsware.org
URL: http://brainsware.org/
GPG: 571B 8B8A FC97 266D BDA3 EF6F 43AD 80A4 5779 3257
_____________________________________________

maintainers mailing list
maintainers at lists.opencsw.org
https://lists.opencsw.org/mailman/listinfo/maintainers
.:: This mailing list's archive is public. ::.

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

From bonivart at opencsw.org  Thu Sep  8 13:40:46 2011
From: bonivart at opencsw.org (Peter Bonivart)
Date: Thu, 8 Sep 2011 13:40:46 +0200
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <472d8e31-144d-40ae-b467-8f2a2afe3a3c@email.android.com>
References: <a3e2ffdb-1dc4-4829-972d-67d419014151@iris>
	<472d8e31-144d-40ae-b467-8f2a2afe3a3c@email.android.com>
Message-ID: <CABY0g1VtY3SezofmfVZuhFKETMEk9jK8MWsW9omJ6ygvQzz8Mw@mail.gmail.com>

On Thu, Sep 8, 2011 at 12:26 PM, Ben Walton <bwalton at opencsw.org> wrote:
> If it will deliver working functionality (and the man page) I don't think it
> should be named stub.
>
> So: alternatives, no alternatives but working functionality or stub with
> deprecation notice binary?

How about this:

CSWpkgget/pkg_get:
   /opt/csw/bin/pkg-get -> deprecation notice
   /opt/csw/bin/pkg-get.deprecated -> the real pkg-get script

Make the package depend on CSWpkgutil to go with the deprecation
notice. This should make it almost painless for users, they will
already have pkgutil on the system, they just have to start using it.
And if they want to keep using pkg-get they can without jumping
through hoops too much. The only problem would be if they are using
pkg-get in some automated scripts, then alternatives would be safer.

/peter

From bwalton at opencsw.org  Thu Sep  8 13:46:09 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Thu, 08 Sep 2011 07:46:09 -0400
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <CABY0g1VtY3SezofmfVZuhFKETMEk9jK8MWsW9omJ6ygvQzz8Mw@mail.gmail.com>
References: <a3e2ffdb-1dc4-4829-972d-67d419014151@iris>
	<472d8e31-144d-40ae-b467-8f2a2afe3a3c@email.android.com>
	<CABY0g1VtY3SezofmfVZuhFKETMEk9jK8MWsW9omJ6ygvQzz8Mw@mail.gmail.com>
Message-ID: <9f53450b-55ff-4db0-baec-d45278c814f4@email.android.com>

If we use alternatives, presumably we'd set the deprecated version as higher priority. Sites would then need to change scripts or run a command to switch the alternative.

I think the key its that whatever we choose needs to be advertised well...and well in advance of delivering the new package.

Thanks
-Ben

Peter Bonivart <bonivart at opencsw.org> wrote:

On Thu, Sep 8, 2011 at 12:26 PM, Ben Walton <bwalton at opencsw.org> wrote:
> If it will deliver working functionality (and the man page) I don't think it
> should be named stub.
>
> So: alternatives, no alternatives but working functionality or stub with
> deprecation notice binary?

How about this:

CSWpkgget/pkg_get:
/opt/csw/bin/pkg-get -> deprecation notice
/opt/csw/bin/pkg-get.deprecated -> the real pkg-get script

Make the package depend on CSWpkgutil to go with the deprecation
notice. This should make it almost painless for users, they will
already have pkgutil on the system, they just have to start using it.
And if they want to keep using pkg-get they can without jumping
through hoops too much. The only problem would be if they are using
pkg-get in some automated scripts, then alternatives would be safer.

/peter
_____________________________________________

maintainers mailing list
maintainers at lists.opencsw.org
https://lists.opencsw.org/mailman/listinfo/maintainers
.:: This mailing list's archive is public. ::.

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

From maciej at opencsw.org  Thu Sep  8 23:53:10 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=)
Date: Thu, 8 Sep 2011 22:53:10 +0100
Subject: [csw-maintainers] GCC 4.6 progress
In-Reply-To: <CALtRa-57epz9gHyfNVzAGELa-7Km_Jxab2cRAYu0mWm5sBdKQw@mail.gmail.com>
References: <CALtRa-6Ho-vowyruOnhysuY4njq5CE98Hr3_WgyHDBUM2tKPEg@mail.gmail.com>
	<CALtRa-7i5B1APocaBRRLe8C-BMGwpzRJEHMSVP=_voOUmHqmsw@mail.gmail.com>
	<CALtRa-6K7FFdhKHfm1eK-vcz9xY=ek-g_9UYQ93UoNd05YXvQQ@mail.gmail.com>
	<CALtRa-7kNA7wUhjJLwgsid7+W4Kx1esXuyag=9yibdyvCayPBg@mail.gmail.com>
	<CALtRa-7xzHQBv6ZHM=iwXONDLGJeWebGjdS9dTbNZYCZ-c_KEA@mail.gmail.com>
	<x6aabak74x.fsf@opencsw.org>
	<CALtRa-6xLfut0JtQEtP=kZHL371X7JDX5jUkJiezwWXj7Kvf7w@mail.gmail.com>
	<x662lyk0ds.fsf@opencsw.org>
	<CALtRa-6X6mJYy9wWpx-mmpO5X+rRY35+eN4+zM53_MFJ6KA7fQ@mail.gmail.com>
	<CALtRa-70hROnmkr-TTyrTbt54xFzaRn54jCOn8PSpS3fwLEJJA@mail.gmail.com>
	<CALtRa-5bPYfprBKH++cW8wN+q8e08WZ7eH5e6OGaD_eQ6-t_fA@mail.gmail.com>
	<DE8738C4-7BC7-4597-A1BF-BDB097FEECC6@opencsw.org>
	<CALtRa-6Vb0u34sE7NHX1Ca4mDBMY3kyt3CfnGWpQO37GV-d5-w@mail.gmail.com>
	<CALtRa-57epz9gHyfNVzAGELa-7Km_Jxab2cRAYu0mWm5sBdKQw@mail.gmail.com>
Message-ID: <CALtRa-7VDgk7Rc7JRbbR_1bheHFe0hC6yoRW7up5ZOe0eZsVMQ@mail.gmail.com>

2011/9/6 Maciej Blizi?ski <maciej at opencsw.org>:
> I've already tried using LDFLAGS, --with-boot-ldflags,
> LDFLAGS_FOR_TARGET and LD_OPTIONS, nothing worked.

I made some experiments (it's like doing natural sciences with two
large, opaque objects) and established that I can, after all,
influence the build by setting LD_OPTIONS.

https://sourceforge.net/apps/trac/gar/changeset/15573

I'm running a full build again, to verify that my solution in fact
works.  I'll then proceed with testing.

I also pushed to unstable two Ada's dependencies: PPL and cloog.  When
I get a working set of packages without Ada, I'll add it to the
configured list of languages and fire the build off again. For now,
I'm focusing on getting the base set of languages (C, C++, Fortran,
Objc, Java) working.

Maciej

From maciej at opencsw.org  Fri Sep  9 09:31:13 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=)
Date: Fri, 9 Sep 2011 08:31:13 +0100
Subject: [csw-maintainers] RFC: idea to unify 32/64 bit headers
In-Reply-To: <5b1893f0-736c-4705-8b6c-aa93b69c481a@iris>
References: <c49b02b5-c4e0-46df-8111-026346ea9565@iris>
	<5b1893f0-736c-4705-8b6c-aa93b69c481a@iris>
Message-ID: <CALtRa-6TTrqYJw01zX--7Rukmdms_0yn+sRqLEDMZ0soZLj_kg@mail.gmail.com>

2011/9/8 Igor Gali? <igalic at opencsw.org>:
>
>
> ----- Original Message -----
>> No dia 23 de Agosto de 2010 20:49, Dagobert Michelsen
>> <dam at opencsw.org> escreveu:
>> > If you do
>> > ?diff -D __amd64 curlbuild-32.h curlbuild-64.h
>> > It will generate an include file where the differences only in the
>> > second
>> > file will be shielded by C preprocessor ifdefs with the string
>> > after the -D.
>> > I like this that much that I am really thinking of making this
>> > fully
>> > automatic: On merge GAR currently just copies over the default (32
>> > bit)
>> > modulation. I could just merge over the diff'ed 32/64 between the
>> > default 32 bit ISA and 64 bit ISA easily making these special
>> > things
>> > obsolete.
>> >
>> > Thoughts?
>
> Two thoughts: +1
> And: Which headers are currently included?

The first modulation, which is 32-bit.

>> I'm definitely for it. ?Our libgmp build can serve as a testbed. ?I'd
>> be also willing to write some code to facilitate this. ?How would you
>> envision the implementation, Dago?
>
> I just tried this out in the shell..
>
> igalic at unstable10x ...ar/pkg/hwloc/trunk/work/solaris9-i386 % for f in $( find install-isa-i386/opt/csw/include/ -type f ) ; do
> x86="${f}"
> amd64="${f/install-isa-i386/install-isa-amd64}"
> diff -D __amd64 "${x86}" "${amd64}"
> done
>
> And found some rather disturbing things
>
> /* Defined to 1 if you have the <stdint.h> header file. */
> #ifndef __amd64
> /* # ?undef HWLOC_HAVE_STDINT_H */
> #else /* __amd64 */
> # ?define HWLOC_HAVE_STDINT_H 1
> #endif /* __amd64 */

That might be related to Solaris Studio magic.

From dam at opencsw.org  Fri Sep  9 09:36:28 2011
From: dam at opencsw.org (Dagobert Michelsen)
Date: Fri, 9 Sep 2011 09:36:28 +0200
Subject: [csw-maintainers] RFC: idea to unify 32/64 bit headers
In-Reply-To: <CALtRa-6TTrqYJw01zX--7Rukmdms_0yn+sRqLEDMZ0soZLj_kg@mail.gmail.com>
References: <c49b02b5-c4e0-46df-8111-026346ea9565@iris>
	<5b1893f0-736c-4705-8b6c-aa93b69c481a@iris>
	<CALtRa-6TTrqYJw01zX--7Rukmdms_0yn+sRqLEDMZ0soZLj_kg@mail.gmail.com>
Message-ID: <94163912-8DC8-4106-96E9-6A6BE74AD325@opencsw.org>

Hi Maciej,

Am 09.09.2011 um 09:31 schrieb Maciej Blizi?ski:
>>> I'm definitely for it.  Our libgmp build can serve as a testbed.  I'd
>>> be also willing to write some code to facilitate this.  How would you
>>> envision the implementation, Dago?
>> 
>> I just tried this out in the shell..
>> 
>> igalic at unstable10x ...ar/pkg/hwloc/trunk/work/solaris9-i386 % for f in $( find install-isa-i386/opt/csw/include/ -type f ) ; do
>> x86="${f}"
>> amd64="${f/install-isa-i386/install-isa-amd64}"
>> diff -D __amd64 "${x86}" "${amd64}"
>> done
>> 
>> And found some rather disturbing things
>> 
>> /* Defined to 1 if you have the <stdint.h> header file. */
>> #ifndef __amd64
>> /* #  undef HWLOC_HAVE_STDINT_H */
>> #else /* __amd64 */
>> #  define HWLOC_HAVE_STDINT_H 1
>> #endif /* __amd64 */
> 
> That might be related to Solaris Studio magic.

What is the problem with that? From my understanding the above headers should have never
been made it to the installed files. Apart from that it looks good to me. However, I use
a slightly different thing to accomodate for a more complex conditional:
  http://sourceforge.net/apps/trac/gar/browser/csw/mgar/pkg/libcurl4/trunk/Makefile#L157
In a GAR built-in definition I would separate the amd64 and sparcv9 conditionals to the
respective GARCH of course.


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


From maciej at opencsw.org  Fri Sep  9 10:44:23 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=)
Date: Fri, 9 Sep 2011 09:44:23 +0100
Subject: [csw-maintainers] mgar makepatch for more than one patch
Message-ID: <CALtRa-4Hc_7HCqgq9BBxpCFLbdeN-XdMbt6kdsqdGGZn5NVSCg@mail.gmail.com>

Hi Ben,

Let's say you have made a couple edits to the sources and you want to
make patches for GAR, but you don't want to make one big patch.
Instead, you want a series of patches that you could individually
offer upstream.  How would you do that in GAR+git?  What sequence of
commands would you use?

Maciej

From bwalton at opencsw.org  Fri Sep  9 15:11:01 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Fri, 09 Sep 2011 09:11:01 -0400
Subject: [csw-maintainers] mgar makepatch for more than one patch
In-Reply-To: <CALtRa-4Hc_7HCqgq9BBxpCFLbdeN-XdMbt6kdsqdGGZn5NVSCg@mail.gmail.com>
References: <CALtRa-4Hc_7HCqgq9BBxpCFLbdeN-XdMbt6kdsqdGGZn5NVSCg@mail.gmail.com>
Message-ID: <1315571190-sup-1432@pinkfloyd.chass.utoronto.ca>

Excerpts from Maciej Blizi?ski's message of Fri Sep 09 04:44:23 -0400 2011:

> Let's say you have made a couple edits to the sources and you want
> to make patches for GAR, but you don't want to make one big patch.
> Instead, you want a series of patches that you could individually
> offer upstream.  How would you do that in GAR+git?  What sequence of
> commands would you use?

The built in stuff is setup to slurp up all changes so that it's a
single easy command.  On pristine sources with no patches, the result
in $(WORKSRC) after the mgar patch run is a master branch that is
equivalent to the end of the mgar extract (typically upstream tarball,
but could be combination of multiple tarballs [eg: docbook]).  We
create a tag here called upstream-$(GARVERSION).  There is then a
branch called csw created and each existing patch is applied to this
branch.  After patches are applied, on the csw branch, we tag the top
of the currently known patch stack as csw-$(GARVERSION).

For a pristine project with no patches you'll have:

o
^
|
\- {master,tag:upstream-$v,csw,tag:csw-$v}

For a project with patches, you'll have:

o
^\--p1--p2--p3--new
|           ^
|           |
|           \-{csw,csw-$v}
|
\-{master,upstream-$v}

If you then modify the $(WORKSRC) and want to generate patches
manually, you can do cd $(WORKSRC); git add -p, etc.  To generate your
new patches, do: git format-patch csw-$(GARVERSION).

I could likely make the makepatch target capable of being run multiple
times and allow people to pass extra flags to git add (git stage) so
that those who want, can set GITPATCH_ADD_ARGS = -p in their .garrc or
something.  I wouldn't want to make this the default though.

Does this help?  Would re-runnable makepatch be worth the effort?

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From maciej at opencsw.org  Fri Sep  9 15:38:35 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=)
Date: Fri, 9 Sep 2011 14:38:35 +0100
Subject: [csw-maintainers] mgar makepatch for more than one patch
In-Reply-To: <1315571190-sup-1432@pinkfloyd.chass.utoronto.ca>
References: <CALtRa-4Hc_7HCqgq9BBxpCFLbdeN-XdMbt6kdsqdGGZn5NVSCg@mail.gmail.com>
	<1315571190-sup-1432@pinkfloyd.chass.utoronto.ca>
Message-ID: <CALtRa-53SNthct_YSKbxpPgD9YcCfFvLf3jn8cGQ29n4APXyyg@mail.gmail.com>

2011/9/9 Ben Walton <bwalton at opencsw.org>:
> Does this help? ?Would re-runnable makepatch be worth the effort?

How about splitting makepatch in two parts:

mgar stagepatch
mgar makepatch

The first would run git stage -p + git commit.  You would run it a
number of times until all changes would be committed.  You'd then run
mgar makepatch to generate the patch files, update the Makefile, and
then go "mgar clean package" to test whether the build recipe works.

Maciej

From bwalton at opencsw.org  Fri Sep  9 15:47:04 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Fri, 09 Sep 2011 09:47:04 -0400
Subject: [csw-maintainers] mgar makepatch for more than one patch
In-Reply-To: <CALtRa-53SNthct_YSKbxpPgD9YcCfFvLf3jn8cGQ29n4APXyyg@mail.gmail.com>
References: <CALtRa-4Hc_7HCqgq9BBxpCFLbdeN-XdMbt6kdsqdGGZn5NVSCg@mail.gmail.com>
	<1315571190-sup-1432@pinkfloyd.chass.utoronto.ca>
	<CALtRa-53SNthct_YSKbxpPgD9YcCfFvLf3jn8cGQ29n4APXyyg@mail.gmail.com>
Message-ID: <1315575863-sup-2542@pinkfloyd.chass.utoronto.ca>

Excerpts from Maciej Blizi?ski's message of Fri Sep 09 09:38:35 -0400 2011:

> How about splitting makepatch in two parts:
> 
> mgar stagepatch
> mgar makepatch
> 
> The first would run git stage -p + git commit.  You would run it a
> number of times until all changes would be committed.  You'd then run
> mgar makepatch to generate the patch files, update the Makefile, and
> then go "mgar clean package" to test whether the build recipe works.

Well, I'm not sure I want to expose stage -p by default.  For people
not comfortable with git, this could be a very bad introduction to the
power feature.  If however we left makepatch the way it is[1] but
introduced a new target (stagepatch) to allow those that wanted the
ability to use it without affecting those that don't want it, I could
live with that.

Would that suit your needs?  Do you think this is better than a
re-runnable makepatch target?

Thanks
-Ben

[1] I might need to change internal behaviour, but I'd leave the user
    facing experience the same.
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From maciej at opencsw.org  Fri Sep  9 16:02:40 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=)
Date: Fri, 9 Sep 2011 15:02:40 +0100
Subject: [csw-maintainers] mgar makepatch for more than one patch
In-Reply-To: <1315575863-sup-2542@pinkfloyd.chass.utoronto.ca>
References: <CALtRa-4Hc_7HCqgq9BBxpCFLbdeN-XdMbt6kdsqdGGZn5NVSCg@mail.gmail.com>
	<1315571190-sup-1432@pinkfloyd.chass.utoronto.ca>
	<CALtRa-53SNthct_YSKbxpPgD9YcCfFvLf3jn8cGQ29n4APXyyg@mail.gmail.com>
	<1315575863-sup-2542@pinkfloyd.chass.utoronto.ca>
Message-ID: <CALtRa-6+Q0eXqykWAjJ6pw+aBaxRRtZs-ycyHXK1sdfg-H+FBg@mail.gmail.com>

2011/9/9 Ben Walton <bwalton at opencsw.org>:
> Well, I'm not sure I want to expose stage -p by default. ?For people
> not comfortable with git, this could be a very bad introduction to the
> power feature. ?If however we left makepatch the way it is[1] but
> introduced a new target (stagepatch) to allow those that wanted the
> ability to use it without affecting those that don't want it, I could
> live with that.
>
> Would that suit your needs? ?Do you think this is better than a
> re-runnable makepatch target?

That's what I was thinking.  The makepatch target turns every commit
into a patch, which is fine. The only thing missing is an easy way to
make multiple commits using git stage -p.

Maciej

From bwalton at opencsw.org  Fri Sep  9 16:07:41 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Fri, 09 Sep 2011 10:07:41 -0400
Subject: [csw-maintainers] mgar makepatch for more than one patch
In-Reply-To: <CALtRa-6+Q0eXqykWAjJ6pw+aBaxRRtZs-ycyHXK1sdfg-H+FBg@mail.gmail.com>
References: <CALtRa-4Hc_7HCqgq9BBxpCFLbdeN-XdMbt6kdsqdGGZn5NVSCg@mail.gmail.com>
	<1315571190-sup-1432@pinkfloyd.chass.utoronto.ca>
	<CALtRa-53SNthct_YSKbxpPgD9YcCfFvLf3jn8cGQ29n4APXyyg@mail.gmail.com>
	<1315575863-sup-2542@pinkfloyd.chass.utoronto.ca>
	<CALtRa-6+Q0eXqykWAjJ6pw+aBaxRRtZs-ycyHXK1sdfg-H+FBg@mail.gmail.com>
Message-ID: <1315577193-sup-6371@pinkfloyd.chass.utoronto.ca>

Excerpts from Maciej Blizi?ski's message of Fri Sep 09 10:02:40 -0400 2011:

> That's what I was thinking.  The makepatch target turns every commit
> into a patch, which is fine. The only thing missing is an easy way
> to make multiple commits using git stage -p.

Ok, I'll need to change the makepatch target to look for differences
between git describe HEAD and git descibe csw-$(GARVERSION) before
doing it's thing then.  Should be easy enough.  I'll work on this over
the weekend.

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From jcraig at opencsw.org  Sat Sep 10 01:08:25 2011
From: jcraig at opencsw.org (Jonathan Craig)
Date: Fri, 9 Sep 2011 19:08:25 -0400
Subject: [csw-maintainers] Repository Woos
Message-ID: <CAH40YU+urH35hhYXXBY2uZxDHhMh8hmLCLRn=OD+cu0DOXTBcw@mail.gmail.com>

Just curious if anyone else is rsync'ing a local copy of the
repository.  At some point my rsync messed up and broke my hard links
which caused a dramatic increase in storage requirements.  Did anyone
else experience this?  Also, I wondered about re-swizzling the links
so actual files are always stored in "allpackages" and everything else
would use symlinks.  The problem is once rsync breaks your hard links
you have to manually go through and recreate them.

Thanks, Jon

From maciej at opencsw.org  Sat Sep 10 13:39:11 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=)
Date: Sat, 10 Sep 2011 12:39:11 +0100
Subject: [csw-maintainers] Repository Woos
In-Reply-To: <CAH40YU+urH35hhYXXBY2uZxDHhMh8hmLCLRn=OD+cu0DOXTBcw@mail.gmail.com>
References: <CAH40YU+urH35hhYXXBY2uZxDHhMh8hmLCLRn=OD+cu0DOXTBcw@mail.gmail.com>
Message-ID: <CALtRa-7TBT2Q=kyGRAeOmiYCKkOYA5DgnytQMOMcKjXZEO=mdA@mail.gmail.com>

2011/9/10 Jonathan Craig <jcraig at opencsw.org>:
> Just curious if anyone else is rsync'ing a local copy of the
> repository. ?At some point my rsync messed up and broke my hard links
> which caused a dramatic increase in storage requirements. ?Did anyone
> else experience this? ?Also, I wondered about re-swizzling the links
> so actual files are always stored in "allpackages" and everything else
> would use symlinks. ?The problem is once rsync breaks your hard links
> you have to manually go through and recreate them.

I personally didn't investigate this issue yet.  All the new packages
are uploaded to allpkgs and then hardlinked, so the "one physical copy
of each file" rule should hold for anything new.  But I didn't write
any checks to verify this is actually the case.  Would you be willing
to develop / provide some sort of diagnostic and/or fixing tool for
the catalog?

Maciej

From jcraig at opencsw.org  Sat Sep 10 14:25:05 2011
From: jcraig at opencsw.org (Jonathan Craig)
Date: Sat, 10 Sep 2011 08:25:05 -0400
Subject: [csw-maintainers] Repository Woos
In-Reply-To: <CALtRa-7TBT2Q=kyGRAeOmiYCKkOYA5DgnytQMOMcKjXZEO=mdA@mail.gmail.com>
References: <CAH40YU+urH35hhYXXBY2uZxDHhMh8hmLCLRn=OD+cu0DOXTBcw@mail.gmail.com>
	<CALtRa-7TBT2Q=kyGRAeOmiYCKkOYA5DgnytQMOMcKjXZEO=mdA@mail.gmail.com>
Message-ID: <CAH40YUL_Uf7ptkOiLd_+G+mJ2B_bGNG0DfWwFNrga+oY+8UPcw@mail.gmail.com>

No problem.  Can you point me to anything that will get me started
understanding the existing process and will I need any additional
privileges (access to the master repository, etc.).  I worked up a
quick and dirty perl script to fix my repository that I should be able
to rework for the master. If the repository is held on a zfs
filesystem on another box it would be nice to have access to that box
to setup and run the process (use of zfs snaphots makes me a lot less
nervous about linking/unlinking a large number of files).

Jon

2011/9/10 Maciej Blizi?ski <maciej at opencsw.org>:
> 2011/9/10 Jonathan Craig <jcraig at opencsw.org>:
>> Just curious if anyone else is rsync'ing a local copy of the
>> repository. ?At some point my rsync messed up and broke my hard links
>> which caused a dramatic increase in storage requirements. ?Did anyone
>> else experience this? ?Also, I wondered about re-swizzling the links
>> so actual files are always stored in "allpackages" and everything else
>> would use symlinks. ?The problem is once rsync breaks your hard links
>> you have to manually go through and recreate them.
>
> I personally didn't investigate this issue yet. ?All the new packages
> are uploaded to allpkgs and then hardlinked, so the "one physical copy
> of each file" rule should hold for anything new. ?But I didn't write
> any checks to verify this is actually the case. ?Would you be willing
> to develop / provide some sort of diagnostic and/or fixing tool for
> the catalog?
>
> Maciej
> _______________________________________________
> maintainers mailing list
> maintainers at lists.opencsw.org
> https://lists.opencsw.org/mailman/listinfo/maintainers
> .:: This mailing list's archive is public. ::.

From dam at opencsw.org  Sat Sep 10 14:34:32 2011
From: dam at opencsw.org (Dagobert Michelsen)
Date: Sat, 10 Sep 2011 14:34:32 +0200
Subject: [csw-maintainers] Repository Woos
In-Reply-To: <CAH40YUL_Uf7ptkOiLd_+G+mJ2B_bGNG0DfWwFNrga+oY+8UPcw@mail.gmail.com>
References: <CAH40YU+urH35hhYXXBY2uZxDHhMh8hmLCLRn=OD+cu0DOXTBcw@mail.gmail.com>
	<CALtRa-7TBT2Q=kyGRAeOmiYCKkOYA5DgnytQMOMcKjXZEO=mdA@mail.gmail.com>
	<CAH40YUL_Uf7ptkOiLd_+G+mJ2B_bGNG0DfWwFNrga+oY+8UPcw@mail.gmail.com>
Message-ID: <8E9215FD-8DC9-432C-9BF2-E70B93C7CC84@opencsw.org>

Hi,

Am 10.09.2011 um 14:25 schrieb Jonathan Craig <jcraig at opencsw.org>:

> No problem.  Can you point me to anything that will get me started
> understanding the existing process and will I need any additional
> privileges (access to the master repository, etc.).  I worked up a
> quick and dirty perl script to fix my repository that I should be able
> to rework for the master. If the repository is held on a zfs
> filesystem on another box it would be nice to have access to that box
> to setup and run the process (use of zfs snaphots makes me a lot less
> nervous about linking/unlinking a large number of files).

There is already dist-hardlinkify on web which generates a shell script to fix doubles.

Best regards

  -- Dago

> 
> Jon
> 
> 2011/9/10 Maciej Blizi?ski <maciej at opencsw.org>:
>> 2011/9/10 Jonathan Craig <jcraig at opencsw.org>:
>>> Just curious if anyone else is rsync'ing a local copy of the
>>> repository.  At some point my rsync messed up and broke my hard links
>>> which caused a dramatic increase in storage requirements.  Did anyone
>>> else experience this?  Also, I wondered about re-swizzling the links
>>> so actual files are always stored in "allpackages" and everything else
>>> would use symlinks.  The problem is once rsync breaks your hard links
>>> you have to manually go through and recreate them.
>> 
>> I personally didn't investigate this issue yet.  All the new packages
>> are uploaded to allpkgs and then hardlinked, so the "one physical copy
>> of each file" rule should hold for anything new.  But I didn't write
>> any checks to verify this is actually the case.  Would you be willing
>> to develop / provide some sort of diagnostic and/or fixing tool for
>> the catalog?
>> 
>> Maciej
>> _______________________________________________
>> maintainers mailing list
>> maintainers at lists.opencsw.org
>> https://lists.opencsw.org/mailman/listinfo/maintainers
>> .:: This mailing list's archive is public. ::.
> _______________________________________________
> maintainers mailing list
> maintainers at lists.opencsw.org
> https://lists.opencsw.org/mailman/listinfo/maintainers
> .:: This mailing list's archive is public. ::.

From maciej at opencsw.org  Sat Sep 10 18:39:00 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sat, 10 Sep 2011 17:39:00 +0100
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <9f53450b-55ff-4db0-baec-d45278c814f4@email.android.com>
References: <a3e2ffdb-1dc4-4829-972d-67d419014151@iris>
	<472d8e31-144d-40ae-b467-8f2a2afe3a3c@email.android.com>
	<CABY0g1VtY3SezofmfVZuhFKETMEk9jK8MWsW9omJ6ygvQzz8Mw@mail.gmail.com>
	<9f53450b-55ff-4db0-baec-d45278c814f4@email.android.com>
Message-ID: <CALtRa-5H_FtK32J1NABzgDFCvUG86Nvv0ocDZUSQSoZUYs7Jiw@mail.gmail.com>

2011/9/8 Ben Walton <bwalton at opencsw.org>:
> If we use alternatives, presumably we'd set the deprecated version as higher
> priority. Sites would then need to change scripts or run a command to switch
> the alternative.

Yes, exactly.  This way you learn that this version is deprecated, but
you have the option of still using the tool, if you really want to.

> I think the key its that whatever we choose needs to be advertised
> well...and well in advance of delivering the new package.

Yes, we need to be very clear about what's going to happen and when.

Maciej

From maciej at opencsw.org  Sat Sep 10 18:58:15 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sat, 10 Sep 2011 17:58:15 +0100
Subject: [csw-maintainers] catalog fun
In-Reply-To: <1315265150-sup-3348@pinkfloyd.chass.utoronto.ca>
References: <1314931865-sup-91@pinkfloyd.chass.utoronto.ca>
	<CALtRa-7mPmf=2q5w4PCdvX4Dkd45sch9JkRkBbVX-EmEayK9pg@mail.gmail.com>
	<1315265150-sup-3348@pinkfloyd.chass.utoronto.ca>
Message-ID: <CALtRa-6fb7KLGRgviL34QbSg8UA=nWxeNVfty3q6PGncyi3_Xg@mail.gmail.com>

2011/9/6 Ben Walton <bwalton at opencsw.org>:
> In cases where we do want to allow this, the tool will need an 'ignore
> errors on foo' option so that it can be driven manually. ?As most
> errors will halt the mirror push, this would allow us to register
> changes in the catalog, cache this catalog and then have the rest of
> the job re-run.

You can always remove all the packages first -- there are no checks
for removals (by design).  After removals, you submit one batch of
packages that bring the catalog to a working state.

From maciej at opencsw.org  Sat Sep 10 18:59:40 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sat, 10 Sep 2011 17:59:40 +0100
Subject: [csw-maintainers] dropping support for solaris 9?
In-Reply-To: <CABY0g1WncU+Hn-5GDSYTqEHrLcRFBZvfrkt_RHdf1ohiCu+bSw@mail.gmail.com>
References: <1315149086-sup-7658@pinkfloyd.chass.utoronto.ca>
	<CAHiP+x_JAdvU+cvhY6rXmJqchXnp2J82uL-eRyrh-HQ=PUGeDg@mail.gmail.com>
	<1315227818-sup-2205@pinkfloyd.chass.utoronto.ca>
	<CABY0g1WncU+Hn-5GDSYTqEHrLcRFBZvfrkt_RHdf1ohiCu+bSw@mail.gmail.com>
Message-ID: <CALtRa-5LheyeK4-thUfSwnFQ3MnpbPsGnkJq-NeEWd-36cEjQA@mail.gmail.com>

2011/9/5 Peter Bonivart <bonivart at opencsw.org>:
> On Mon, Sep 5, 2011 at 3:12 PM, Ben Walton <bwalton at opencsw.org> wrote:
>> Also, dropping official support does not preclude building packages
>> for it at need/want. ?Most people will abandon 9 for builds when we
>> mark it unsupported, but a few packages will likely still be built for
>> it. ?I think Peter B still builds pkgutil packages for 8. ?The key is
>> that you, as a maintainer, are no longer bound to build for it doing
>> 10-only packages in edge cases.
>
> The build hosts may be available yet but it's much harder to build
> packages for Solaris 8 now than it used to be since we also dropped
> support for Solaris 8 in our own tool chain. It's impossible to run
> modern GAR/checkpkg on the Solaris 8 build hosts. Also I have failed
> in more ways than I can count to upload Solaris 8 packages to our
> catalogs.

It can be done manually, but the more low-level pkgdb tool.

> If we are to support Solaris 9 (and maybe even 8) in a limited way
> there should still be a way to get those packages to our users in a
> way that is not totally exhausting. Some verified documentation should
> exist on how to proceed.
>
> In general I'm all for dropping Solaris 9 after October though.

We could ask users whether there's any interest in Solaris 9, and if
so, which packages are used on Solaris 9.  If it's something like,
say, openssh and coreutils, we could keep on updating these two.

Maciej

From maciej at opencsw.org  Sat Sep 10 20:55:33 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sat, 10 Sep 2011 19:55:33 +0100
Subject: [csw-maintainers] Retiring old versions of GCC
In-Reply-To: <1314537998-sup-2689@pinkfloyd.chass.utoronto.ca>
References: <CALtRa-6rcYAfUZamMdGFH3da7bAiBW3OEWsefpabEYxqF5m98Q@mail.gmail.com>
	<x6pqjpsn14.fsf@opencsw.org>
	<1314537998-sup-2689@pinkfloyd.chass.utoronto.ca>
Message-ID: <CALtRa-6RxGjFpNTbxjMgOWEOw0jKe-o0Ty7qqiqyxjch-8RJ+w@mail.gmail.com>

2011/8/28 Ben Walton <bwalton at opencsw.org>:
>> I don't have any objection toward its removal. However, is there a
>> conflict with the current or future gcc releases? If there is no
>> conflict don't remove it.
>
> I think we need to retain the *rt packages though...either that or
> also drop the few things that depend on them. ?I don't have any
> comment on whether or not that is good/bad as I don't use those
> packages. ?In this case, I'd likely err toward leaving the *rt
> packages around.

The rt packages need to stay as long as other packages depend on them.
 I hope that with time we will rebuild or remove dependent packages.

Maciej

From dam at opencsw.org  Sat Sep 10 22:01:06 2011
From: dam at opencsw.org (Dagobert Michelsen)
Date: Sat, 10 Sep 2011 22:01:06 +0200
Subject: [csw-maintainers] Repository Woos
In-Reply-To: <8E9215FD-8DC9-432C-9BF2-E70B93C7CC84@opencsw.org>
References: <CAH40YU+urH35hhYXXBY2uZxDHhMh8hmLCLRn=OD+cu0DOXTBcw@mail.gmail.com>
	<CALtRa-7TBT2Q=kyGRAeOmiYCKkOYA5DgnytQMOMcKjXZEO=mdA@mail.gmail.com>
	<CAH40YUL_Uf7ptkOiLd_+G+mJ2B_bGNG0DfWwFNrga+oY+8UPcw@mail.gmail.com>
	<8E9215FD-8DC9-432C-9BF2-E70B93C7CC84@opencsw.org>
Message-ID: <90A57A10-6D70-41E7-8DB0-32E66C9DD9A2@opencsw.org>

Hi,

Am 10.09.2011 um 14:34 schrieb Dagobert Michelsen:
> Am 10.09.2011 um 14:25 schrieb Jonathan Craig <jcraig at opencsw.org>:
>> No problem.  Can you point me to anything that will get me started
>> understanding the existing process and will I need any additional
>> privileges (access to the master repository, etc.).  I worked up a
>> quick and dirty perl script to fix my repository that I should be able
>> to rework for the master. If the repository is held on a zfs
>> filesystem on another box it would be nice to have access to that box
>> to setup and run the process (use of zfs snaphots makes me a lot less
>> nervous about linking/unlinking a large number of files).
> 
> There is already dist-hardlinkify on web which generates a shell script to fix doubles.

I adjusted the script to work on the current mirror layout:
  http://opencsw.svn.sourceforge.net/viewvc/opencsw/buildfarm/bin/dist-hardlinkify?view=markup

There really are *a lot* of not-hardlinked files. Especially "legacy" does not seem to
be linked properly. I now fixed around 10000 files with the result of that script.


Best regards

  -- Dago

BTW: We even have a package to find dupes:
  http://www.opencsw.org/packages/samefile/

From maciej at opencsw.org  Sat Sep 10 23:14:26 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sat, 10 Sep 2011 22:14:26 +0100
Subject: [csw-maintainers] progress report
In-Reply-To: <1313975389-sup-4471@pinkfloyd.chass.utoronto.ca>
References: <1313975389-sup-4471@pinkfloyd.chass.utoronto.ca>
Message-ID: <CALtRa-7Nvsps6cStZmvF6OpvyUaYPDro=P2DYSbOS7EwQhKsxQ@mail.gmail.com>

2011/8/22 Ben Walton <bwalton at opencsw.org>:
> A short check in on the web and mantis integration automation. ?I now
> have code that can take an old catalog and a new one and then generate
> a list of high level steps required to make our browseable web
> interface and mantis 'line up' with the catalog state. ?I've also
> trudged through the old ksh code and I think I have a list of sql
> statements required to turn high level action to low level
> implementation.

If I wanted to look at the code, where would I look?

How is it going?

Maciej

From maciej at opencsw.org  Sun Sep 11 01:18:54 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sun, 11 Sep 2011 00:18:54 +0100
Subject: [csw-maintainers] Repository Woos
In-Reply-To: <90A57A10-6D70-41E7-8DB0-32E66C9DD9A2@opencsw.org>
References: <CAH40YU+urH35hhYXXBY2uZxDHhMh8hmLCLRn=OD+cu0DOXTBcw@mail.gmail.com>
	<CALtRa-7TBT2Q=kyGRAeOmiYCKkOYA5DgnytQMOMcKjXZEO=mdA@mail.gmail.com>
	<CAH40YUL_Uf7ptkOiLd_+G+mJ2B_bGNG0DfWwFNrga+oY+8UPcw@mail.gmail.com>
	<8E9215FD-8DC9-432C-9BF2-E70B93C7CC84@opencsw.org>
	<90A57A10-6D70-41E7-8DB0-32E66C9DD9A2@opencsw.org>
Message-ID: <CALtRa-63wi0E=YPv49KwZJJt5PFOcwod27rKUBARmsW-Mqm3_A@mail.gmail.com>

2011/9/10 Dagobert Michelsen <dam at opencsw.org>:
> I adjusted the script to work on the current mirror layout:
> ?http://opencsw.svn.sourceforge.net/viewvc/opencsw/buildfarm/bin/dist-hardlinkify?view=markup
>
> There really are *a lot* of not-hardlinked files. Especially "legacy" does not seem to
> be linked properly. I now fixed around 10000 files with the result of that script.

What about garbage collecting? There are files in allpkgs which aren't
referenced by any catalogs.

Maciej

From bwalton at opencsw.org  Sun Sep 11 02:13:28 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Sat, 10 Sep 2011 20:13:28 -0400
Subject: [csw-maintainers] progress report
In-Reply-To: <CALtRa-7Nvsps6cStZmvF6OpvyUaYPDro=P2DYSbOS7EwQhKsxQ@mail.gmail.com>
References: <1313975389-sup-4471@pinkfloyd.chass.utoronto.ca>
	<CALtRa-7Nvsps6cStZmvF6OpvyUaYPDro=P2DYSbOS7EwQhKsxQ@mail.gmail.com>
Message-ID: <1315699661-sup-5642@pinkfloyd.chass.utoronto.ca>

Excerpts from Maciej (Matchek) Blizi?ski's message of Sat Sep 10 17:14:26 -0400 2011:

> If I wanted to look at the code, where would I look?

It's in the opencsw-ruby git repo that I created to house the atom
feed code.  As this new code shares a lot of functionality, I'm simply
expanding the lib/csw/ areas and will fill out appropriate bin/
scripts.

> How is it going?

Slowly right now.  I'm ready to do the database adapter parts but I'm
more and more convinced that sticking with the current db is not a
good idea.  There is just too much cruft there.  And not enough cruft
at the same time.

I think it's time to scrap this database and rewrite the schema from
scratch.  All hard ties in the old process between CSW (the name of
the web db) and mantis_prod should be cut.  The update functionality
should be split so that one process updates the web and another
updates mantis.  This should simplify both pieces of code.

The other _real_ gain here is that the new schema could become
catalog, os release and architecture aware.  That's a big lacking item
in the current browser.  With a properly normalized (including key
constraints) database, we can also wrap it with an ORM.

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From bwalton at opencsw.org  Sun Sep 11 04:42:52 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Sat, 10 Sep 2011 22:42:52 -0400
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <CALtRa-5H_FtK32J1NABzgDFCvUG86Nvv0ocDZUSQSoZUYs7Jiw@mail.gmail.com>
References: <a3e2ffdb-1dc4-4829-972d-67d419014151@iris>
	<472d8e31-144d-40ae-b467-8f2a2afe3a3c@email.android.com>
	<CABY0g1VtY3SezofmfVZuhFKETMEk9jK8MWsW9omJ6ygvQzz8Mw@mail.gmail.com>
	<9f53450b-55ff-4db0-baec-d45278c814f4@email.android.com>
	<CALtRa-5H_FtK32J1NABzgDFCvUG86Nvv0ocDZUSQSoZUYs7Jiw@mail.gmail.com>
Message-ID: <1315708421-sup-2774@pinkfloyd.chass.utoronto.ca>

Excerpts from Maciej (Matchek) Blizi?ski's message of Sat Sep 10 12:39:00 -0400 2011:
> 2011/9/8 Ben Walton <bwalton at opencsw.org>:

> > If we use alternatives, presumably we'd set the deprecated version
> > as higher priority. Sites would then need to change scripts or run
> > a command to switch the alternative.
> 
> Yes, exactly.  This way you learn that this version is deprecated,
> but you have the option of still using the tool, if you really want
> to.

Ironically, as Phil never fixed the bug in his alternatives
implementation, delivering multiple alternatives with the same name in
a single package isn't feasible.  The files are delivered and
registered properly, but switching the alternatives doesn't work.

I've dropped alternatives and opted to simply deliver two binaries,
the normal name being our "switch!" script and pkg-get.deprecated
being the original tool.

How does it look?

http://buildfarm.opencsw.org/experimental.html#pkgget

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From bwalton at opencsw.org  Sun Sep 11 04:57:16 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Sat, 10 Sep 2011 22:57:16 -0400
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <1315708421-sup-2774@pinkfloyd.chass.utoronto.ca>
References: <a3e2ffdb-1dc4-4829-972d-67d419014151@iris>
	<472d8e31-144d-40ae-b467-8f2a2afe3a3c@email.android.com>
	<CABY0g1VtY3SezofmfVZuhFKETMEk9jK8MWsW9omJ6ygvQzz8Mw@mail.gmail.com>
	<9f53450b-55ff-4db0-baec-d45278c814f4@email.android.com>
	<CALtRa-5H_FtK32J1NABzgDFCvUG86Nvv0ocDZUSQSoZUYs7Jiw@mail.gmail.com>
	<1315708421-sup-2774@pinkfloyd.chass.utoronto.ca>
Message-ID: <1315709800-sup-9153@pinkfloyd.chass.utoronto.ca>

Excerpts from Ben Walton's message of Sat Sep 10 22:42:52 -0400 2011:

> I've dropped alternatives and opted to simply deliver two binaries,
> the normal name being our "switch!" script and pkg-get.deprecated
> being the original tool.

I guess I could make a second package that gets pulled in by
pkg_get_stub to deliver the lower priority alternative...

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From maciej at opencsw.org  Sun Sep 11 11:32:06 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sun, 11 Sep 2011 10:32:06 +0100
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <1315708421-sup-2774@pinkfloyd.chass.utoronto.ca>
References: <a3e2ffdb-1dc4-4829-972d-67d419014151@iris>
	<472d8e31-144d-40ae-b467-8f2a2afe3a3c@email.android.com>
	<CABY0g1VtY3SezofmfVZuhFKETMEk9jK8MWsW9omJ6ygvQzz8Mw@mail.gmail.com>
	<9f53450b-55ff-4db0-baec-d45278c814f4@email.android.com>
	<CALtRa-5H_FtK32J1NABzgDFCvUG86Nvv0ocDZUSQSoZUYs7Jiw@mail.gmail.com>
	<1315708421-sup-2774@pinkfloyd.chass.utoronto.ca>
Message-ID: <CALtRa-6LMfpEs17zvHu1nuvUv7rWY+hKpxhpsFMJKQw4P+t0Fg@mail.gmail.com>

2011/9/11 Ben Walton <bwalton at opencsw.org>:
> Excerpts from Maciej (Matchek) Blizi?ski's message of Sat Sep 10 12:39:00 -0400 2011:
>> 2011/9/8 Ben Walton <bwalton at opencsw.org>:
>
>> > If we use alternatives, presumably we'd set the deprecated version
>> > as higher priority. Sites would then need to change scripts or run
>> > a command to switch the alternative.
>>
>> Yes, exactly. ?This way you learn that this version is deprecated,
>> but you have the option of still using the tool, if you really want
>> to.
>
> Ironically, as Phil never fixed the bug in his alternatives
> implementation, delivering multiple alternatives with the same name in
> a single package isn't feasible. ?The files are delivered and
> registered properly, but switching the alternatives doesn't work.

That's unfortunate.

> I've dropped alternatives and opted to simply deliver two binaries,
> the normal name being our "switch!" script and pkg-get.deprecated
> being the original tool.
>
> How does it look?
>
> http://buildfarm.opencsw.org/experimental.html#pkgget

If alternatives don't work for a single package, this scenario sounds
good. You mentioned in the other email that there could be a separate
package with the deprecated pkg-get, but it would be an overkill.  The
version in experimental looks good.

Maciej

From maciej at opencsw.org  Sun Sep 11 11:41:40 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sun, 11 Sep 2011 10:41:40 +0100
Subject: [csw-maintainers] progress report
In-Reply-To: <1315699661-sup-5642@pinkfloyd.chass.utoronto.ca>
References: <1313975389-sup-4471@pinkfloyd.chass.utoronto.ca>
	<CALtRa-7Nvsps6cStZmvF6OpvyUaYPDro=P2DYSbOS7EwQhKsxQ@mail.gmail.com>
	<1315699661-sup-5642@pinkfloyd.chass.utoronto.ca>
Message-ID: <CALtRa-4CwJ4OHvOnEsRYfZ-nECbNm7hPx34FVCEoviRaa7E+ag@mail.gmail.com>

2011/9/11 Ben Walton <bwalton at opencsw.org>:
>> How is it going?
>
> Slowly right now. ?I'm ready to do the database adapter parts but I'm
> more and more convinced that sticking with the current db is not a
> good idea. ?There is just too much cruft there. ?And not enough cruft
> at the same time.
>
> I think it's time to scrap this database and rewrite the schema from
> scratch. ?All hard ties in the old process between CSW (the name of
> the web db) and mantis_prod should be cut. ?The update functionality
> should be split so that one process updates the web and another
> updates mantis. ?This should simplify both pieces of code.

May I suggest using the buildfarm database?  If we only set up
replication from the buildfarm to the web server, we'd be done with
it.  If there's something the schema is lacking, we'd expand it.  When
I'm done with gcc (hopefully soon), I'll be ready to put some time
into coding again.

> The other _real_ gain here is that the new schema could become
> catalog, os release and architecture aware. ?That's a big lacking item
> in the current browser. ?With a properly normalized (including key
> constraints) database, we can also wrap it with an ORM.

The buildfarm database is partly denormalized, but that's done on
purpose.  Look into /etc/opt/csw/checkpkg.ini for credentials and have
a look around the db tables.

Maciej

From maciej at opencsw.org  Sun Sep 11 12:19:35 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sun, 11 Sep 2011 11:19:35 +0100
Subject: [csw-maintainers] Forum Software
In-Reply-To: <4DDE52A3.9020300@inamo.no>
References: <4DDD0E24.6010907@opencsw.org>
	<20110525164348.GG11519@sebastiankayser.de>
	<4DDE52A3.9020300@inamo.no>
Message-ID: <CALtRa-4Eno41c9871C4yA43a4pPkox+svMnj4ySrAN0BYiwm2A@mail.gmail.com>

2011/5/26 Trygve Laugst?l <trygvis at inamo.no>:
> Another option is Shapado [1] which is more or less a stackexchange[2] copy.
> It's a bit different than traditional forums, but has a very nice
> "community" thing to it.

Yes, it looks like a questions and answers kind of thing.  As far as
asking Solaris related questions, the solaris tag at serverfault.com
seems do the job already:

http://serverfault.com/questions/tagged/solaris

Maybe we can take a step back and ask - why do we need a forum?  What
space do we want the forum to fill?

My general thought is that mailing lists are generally not very good
at building user communities.  For developers, they're great, for but
for users, not so much.  Announcement mailing lists, yes.  But for
general interest and involvement, forums seem to be more effective.
The idea would be to lower the entry barrier.  Of course, the same
thing could constitute a different entry barrier for different people.
 One person will see a forum and say: "Cool, this is the kind of forum
I know how to use, so let me join it", while another person will say:
"What? I need to set up yet another account? No way."

I would like there to be something that people are already familiar
with.  Also, if anyone is willing to put the time in it and set up a
forum, I'll be happy with whatever choice they make.

Some additional considerations could be spam prevention (captchas,
etc) and general maintainability, something that phpbb does not excel
at.

Maciej

From maciej at opencsw.org  Sun Sep 11 13:21:59 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sun, 11 Sep 2011 12:21:59 +0100
Subject: [csw-maintainers] GCC 4.6 progress
In-Reply-To: <CALtRa-7VDgk7Rc7JRbbR_1bheHFe0hC6yoRW7up5ZOe0eZsVMQ@mail.gmail.com>
References: <CALtRa-6Ho-vowyruOnhysuY4njq5CE98Hr3_WgyHDBUM2tKPEg@mail.gmail.com>
	<CALtRa-7i5B1APocaBRRLe8C-BMGwpzRJEHMSVP=_voOUmHqmsw@mail.gmail.com>
	<CALtRa-6K7FFdhKHfm1eK-vcz9xY=ek-g_9UYQ93UoNd05YXvQQ@mail.gmail.com>
	<CALtRa-7kNA7wUhjJLwgsid7+W4Kx1esXuyag=9yibdyvCayPBg@mail.gmail.com>
	<CALtRa-7xzHQBv6ZHM=iwXONDLGJeWebGjdS9dTbNZYCZ-c_KEA@mail.gmail.com>
	<x6aabak74x.fsf@opencsw.org>
	<CALtRa-6xLfut0JtQEtP=kZHL371X7JDX5jUkJiezwWXj7Kvf7w@mail.gmail.com>
	<x662lyk0ds.fsf@opencsw.org>
	<CALtRa-6X6mJYy9wWpx-mmpO5X+rRY35+eN4+zM53_MFJ6KA7fQ@mail.gmail.com>
	<CALtRa-70hROnmkr-TTyrTbt54xFzaRn54jCOn8PSpS3fwLEJJA@mail.gmail.com>
	<CALtRa-5bPYfprBKH++cW8wN+q8e08WZ7eH5e6OGaD_eQ6-t_fA@mail.gmail.com>
	<DE8738C4-7BC7-4597-A1BF-BDB097FEECC6@opencsw.org>
	<CALtRa-6Vb0u34sE7NHX1Ca4mDBMY3kyt3CfnGWpQO37GV-d5-w@mail.gmail.com>
	<CALtRa-57epz9gHyfNVzAGELa-7Km_Jxab2cRAYu0mWm5sBdKQw@mail.gmail.com>
	<CALtRa-7VDgk7Rc7JRbbR_1bheHFe0hC6yoRW7up5ZOe0eZsVMQ@mail.gmail.com>
Message-ID: <CALtRa-7Uvy3thSB1Wdf70tuPG5qn1rSNrbmU_4T+2i0TMTLOCw@mail.gmail.com>

Progress!

I got a working gcc-4.6.1 for 3 out of 4 architectures.  The missing
one is amd64, which I cannot build because unstable10x is not
responding.  The rest of the gcc4 packages are already uploaded to
unstable.

Maciej

From bwalton at opencsw.org  Sun Sep 11 14:55:11 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Sun, 11 Sep 2011 08:55:11 -0400
Subject: [csw-maintainers] progress report
In-Reply-To: <CALtRa-4CwJ4OHvOnEsRYfZ-nECbNm7hPx34FVCEoviRaa7E+ag@mail.gmail.com>
References: <1313975389-sup-4471@pinkfloyd.chass.utoronto.ca>
	<CALtRa-7Nvsps6cStZmvF6OpvyUaYPDro=P2DYSbOS7EwQhKsxQ@mail.gmail.com>
	<1315699661-sup-5642@pinkfloyd.chass.utoronto.ca>
	<CALtRa-4CwJ4OHvOnEsRYfZ-nECbNm7hPx34FVCEoviRaa7E+ag@mail.gmail.com>
Message-ID: <1315745612-sup-4977@pinkfloyd.chass.utoronto.ca>

Excerpts from Maciej (Matchek) Blizi?ski's message of Sun Sep 11 05:41:40 -0400 2011:

> May I suggest using the buildfarm database?  If we only set up
> replication from the buildfarm to the web server, we'd be done with
> it.  If there's something the schema is lacking, we'd expand it.
> When I'm done with gcc (hopefully soon), I'll be ready to put some
> time into coding again.

This would certainly reduce the data duplication we currently have, so
I think it's a good choice.

> The buildfarm database is partly denormalized, but that's done on
> purpose.  Look into /etc/opt/csw/checkpkg.ini for credentials and
> have a look around the db tables.

Yes, 100% normalization may not be ideal for this as there would be
several heavily used tables with less than 5 objects stored.

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From bwalton at opencsw.org  Sun Sep 11 14:56:49 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Sun, 11 Sep 2011 08:56:49 -0400
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <CALtRa-6LMfpEs17zvHu1nuvUv7rWY+hKpxhpsFMJKQw4P+t0Fg@mail.gmail.com>
References: <a3e2ffdb-1dc4-4829-972d-67d419014151@iris>
	<472d8e31-144d-40ae-b467-8f2a2afe3a3c@email.android.com>
	<CABY0g1VtY3SezofmfVZuhFKETMEk9jK8MWsW9omJ6ygvQzz8Mw@mail.gmail.com>
	<9f53450b-55ff-4db0-baec-d45278c814f4@email.android.com>
	<CALtRa-5H_FtK32J1NABzgDFCvUG86Nvv0ocDZUSQSoZUYs7Jiw@mail.gmail.com>
	<1315708421-sup-2774@pinkfloyd.chass.utoronto.ca>
	<CALtRa-6LMfpEs17zvHu1nuvUv7rWY+hKpxhpsFMJKQw4P+t0Fg@mail.gmail.com>
Message-ID: <1315745725-sup-7116@pinkfloyd.chass.utoronto.ca>

Excerpts from Maciej (Matchek) Blizi?ski's message of Sun Sep 11 05:32:06 -0400 2011:

> If alternatives don't work for a single package, this scenario
> sounds good. You mentioned in the other email that there could be a
> separate package with the deprecated pkg-get, but it would be an
> overkill.  The version in experimental looks good.

That was my thinking too.  Although it makes the local site have to do
more work to avoid altering scripts, providing two packages to
accommodate this is overkill, I think.  Maybe sites that need to
update scripts will choose to move those scripts to use pkgutil instead?

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From dam at opencsw.org  Sun Sep 11 15:24:32 2011
From: dam at opencsw.org (Dagobert Michelsen)
Date: Sun, 11 Sep 2011 15:24:32 +0200
Subject: [csw-maintainers] Forum Software
In-Reply-To: <CALtRa-4Eno41c9871C4yA43a4pPkox+svMnj4ySrAN0BYiwm2A@mail.gmail.com>
References: <4DDD0E24.6010907@opencsw.org>
	<20110525164348.GG11519@sebastiankayser.de>
	<4DDE52A3.9020300@inamo.no>
	<CALtRa-4Eno41c9871C4yA43a4pPkox+svMnj4ySrAN0BYiwm2A@mail.gmail.com>
Message-ID: <7189C6E2-81B5-4F61-8DD9-13A6FDA6C63E@opencsw.org>

Hi,

Am 11.09.2011 um 12:19 schrieb Maciej (Matchek) Blizi?ski:
> 2011/5/26 Trygve Laugst?l <trygvis at inamo.no>:
>> Another option is Shapado [1] which is more or less a stackexchange[2] copy.
>> It's a bit different than traditional forums, but has a very nice
>> "community" thing to it.
> 
> Yes, it looks like a questions and answers kind of thing.  As far as
> asking Solaris related questions, the solaris tag at serverfault.com
> seems do the job already:
> 
> http://serverfault.com/questions/tagged/solaris
> 
> Maybe we can take a step back and ask - why do we need a forum?  What
> space do we want the forum to fill?
> 
> My general thought is that mailing lists are generally not very good
> at building user communities.  For developers, they're great, for but
> for users, not so much.  Announcement mailing lists, yes.  But for
> general interest and involvement, forums seem to be more effective.
> The idea would be to lower the entry barrier.  Of course, the same
> thing could constitute a different entry barrier for different people.
> One person will see a forum and say: "Cool, this is the kind of forum
> I know how to use, so let me join it", while another person will say:
> "What? I need to set up yet another account? No way."
> 
> I would like there to be something that people are already familiar
> with.  Also, if anyone is willing to put the time in it and set up a
> forum, I'll be happy with whatever choice they make.
> 
> Some additional considerations could be spam prevention (captchas,
> etc) and general maintainability, something that phpbb does not excel
> at.

What I would like to have is a connection of the forum to the package page
so if you browse a package you automaically see he most recent posts or
post topics or so.


Best regards

  -- Dago

From maciej at opencsw.org  Sun Sep 11 15:48:24 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sun, 11 Sep 2011 14:48:24 +0100
Subject: [csw-maintainers] progress report
In-Reply-To: <1315745612-sup-4977@pinkfloyd.chass.utoronto.ca>
References: <1313975389-sup-4471@pinkfloyd.chass.utoronto.ca>
	<CALtRa-7Nvsps6cStZmvF6OpvyUaYPDro=P2DYSbOS7EwQhKsxQ@mail.gmail.com>
	<1315699661-sup-5642@pinkfloyd.chass.utoronto.ca>
	<CALtRa-4CwJ4OHvOnEsRYfZ-nECbNm7hPx34FVCEoviRaa7E+ag@mail.gmail.com>
	<1315745612-sup-4977@pinkfloyd.chass.utoronto.ca>
Message-ID: <CALtRa-47+Y1DynrSggcMTKEubPv5i3iHhJgRPUtcyOR_0exbxQ@mail.gmail.com>

2011/9/11 Ben Walton <bwalton at opencsw.org>:
> Yes, 100% normalization may not be ideal for this as there would be
> several heavily used tables with less than 5 objects stored.

Do you mean dictionary tables?

The main reason for denormalization was this: when William was
designing his package database, he had a number of tables, such as:

- software
- software + version
- software + version + package revision
- software + version + package revision + architecture
- software + version + package revision + architecture + OS release

...and so on.  The more complex the primary key, the more packages in
the table.  To keep this kind of normalized structure, you need to
instantiate a lot of intermediate objects before you can store
information about your svr4 file (I intentionally avoid the term
'package').

In the buildfarm database, the approach is different. There is one
main table with the svr4 files.  Each row has fields: software
version, package revision, architecture, OS release, etc.  There are
indexes for these fields, so if you want to find packages for certain
OS release an architecture, you just specify the right filters in your
SQL query, and lookups should be reasonably fast.

http://paste.pocoo.org/show/474057/

One quirk about the table is that there are two columns referring to
the architecture.  Why is that?  There are two places in a package
that describe the architecture: pkginfo and the file name.  They in
practice do not always agree.  The buildfarm database does not try to
model the perfect world, it aims to reflect the reality, so if
packages in reality sometimes have mismatched information, I want the
database to be able to store that.  Hence, arch_id and
filename_arch_id.

Maciej

From maciej at opencsw.org  Sun Sep 11 15:51:16 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sun, 11 Sep 2011 14:51:16 +0100
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <1315745725-sup-7116@pinkfloyd.chass.utoronto.ca>
References: <a3e2ffdb-1dc4-4829-972d-67d419014151@iris>
	<472d8e31-144d-40ae-b467-8f2a2afe3a3c@email.android.com>
	<CABY0g1VtY3SezofmfVZuhFKETMEk9jK8MWsW9omJ6ygvQzz8Mw@mail.gmail.com>
	<9f53450b-55ff-4db0-baec-d45278c814f4@email.android.com>
	<CALtRa-5H_FtK32J1NABzgDFCvUG86Nvv0ocDZUSQSoZUYs7Jiw@mail.gmail.com>
	<1315708421-sup-2774@pinkfloyd.chass.utoronto.ca>
	<CALtRa-6LMfpEs17zvHu1nuvUv7rWY+hKpxhpsFMJKQw4P+t0Fg@mail.gmail.com>
	<1315745725-sup-7116@pinkfloyd.chass.utoronto.ca>
Message-ID: <CALtRa-6heRRp-uSDb_Ache7kTT0pawYv-U463cU-Q2oFxGh38g@mail.gmail.com>

2011/9/11 Ben Walton <bwalton at opencsw.org>:
> Excerpts from Maciej (Matchek) Blizi?ski's message of Sun Sep 11 05:32:06 -0400 2011:
>
>> If alternatives don't work for a single package, this scenario
>> sounds good. You mentioned in the other email that there could be a
>> separate package with the deprecated pkg-get, but it would be an
>> overkill. ?The version in experimental looks good.
>
> That was my thinking too. ?Although it makes the local site have to do
> more work to avoid altering scripts, providing two packages to
> accommodate this is overkill, I think. ?Maybe sites that need to
> update scripts will choose to move those scripts to use pkgutil instead?

We certainly hope they will.  We also need to make an announcement,
because there might be existing automation systems relying on pkg-get,
and we don't want our users to find out the hard way.

At least the potential consequence will be a broken update system, as
opposed to a broken OpenCSW installation.

Maciej

From maciej at opencsw.org  Sun Sep 11 15:53:28 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sun, 11 Sep 2011 14:53:28 +0100
Subject: [csw-maintainers] Forum Software
In-Reply-To: <7189C6E2-81B5-4F61-8DD9-13A6FDA6C63E@opencsw.org>
References: <4DDD0E24.6010907@opencsw.org>
	<20110525164348.GG11519@sebastiankayser.de>
	<4DDE52A3.9020300@inamo.no>
	<CALtRa-4Eno41c9871C4yA43a4pPkox+svMnj4ySrAN0BYiwm2A@mail.gmail.com>
	<7189C6E2-81B5-4F61-8DD9-13A6FDA6C63E@opencsw.org>
Message-ID: <CALtRa-7HtSMt3tkfFWHbm7SLxpU+9=rHDXKAYvMRsf1DDXdq-A@mail.gmail.com>

2011/9/11 Dagobert Michelsen <dam at opencsw.org>:
> What I would like to have is a connection of the forum to the package page
> so if you browse a package you automaically see he most recent posts or
> post topics or so.

My first thought is: Django commenting system.  There is a plugin for
Django that adds a generic commenting system to any (Django-served)
page.  If such thing exists for php, we could use that.  Of course,
spam prevention would be a major consideration.

Maciej

From i.galic at brainsware.org  Thu Sep  8 07:01:59 2011
From: i.galic at brainsware.org (Igor =?utf-8?Q?Gali=C4=87?=)
Date: Thu, 08 Sep 2011 05:01:59 -0000 (UTC)
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <1315442673-sup-4404@pinkfloyd.chass.utoronto.ca>
Message-ID: <ae51fa1d-8dbc-4d5c-a597-21022547bb28@iris>



----- Original Message -----
> Excerpts from Maciej Blizi?ski's message of Wed Sep 07 16:41:01 -0400
> 2011:
> 
> > I was thinking about a scenario where alternatives are used.  The
> > default implementation would be the one cited above, and the second
> > choice would be the original pkg-get, which you would choose if you
> > really really wanted to.  This way, we get people to understand
> > what's going on, but we don't take away the ability to use the
> > tool.
> 
> Or we could just place the working tool as
> /opt/csw/bin/pkg-get.deprecated (unsupported?) and require people to
> use it with that name if they want it still?

Would this option still include a pkg_get_stub ?

> Thanks
> -Ben
> --
> Ben Walton
> Systems Programmer - CHASS
> University of Toronto
> C:416.407.5610 | W:416.978.4302

i

-- 
Igor Gali?

Tel: +43 (0) 664 886 22 883
Mail: i.galic at brainsware.org
URL: http://brainsware.org/
GPG: 571B 8B8A FC97 266D BDA3  EF6F 43AD 80A4 5779 3257

From i.galic at brainsware.org  Thu Sep  8 07:39:17 2011
From: i.galic at brainsware.org (Igor =?utf-8?Q?Gali=C4=87?=)
Date: Thu, 08 Sep 2011 05:39:17 -0000 (UTC)
Subject: [csw-maintainers] RFC: idea to unify 32/64 bit headers
In-Reply-To: <CADHRADCjjpf2yQBx=xNE_c+n48KH=3AUvuz3jHm7Tza_4UXKXw@mail.gmail.com>
Message-ID: <c49b02b5-c4e0-46df-8111-026346ea9565@iris>



----- Original Message -----
> No dia 23 de Agosto de 2010 20:49, Dagobert Michelsen
> <dam at opencsw.org> escreveu:
> > If you do
> > ?diff -D __amd64 curlbuild-32.h curlbuild-64.h
> > It will generate an include file where the differences only in the
> > second
> > file will be shielded by C preprocessor ifdefs with the string
> > after the -D.
> > I like this that much that I am really thinking of making this
> > fully
> > automatic: On merge GAR currently just copies over the default (32
> > bit)
> > modulation. I could just merge over the diff'ed 32/64 between the
> > default 32 bit ISA and 64 bit ISA easily making these special
> > things
> > obsolete.
> >
> > Thoughts?

Two thoughts: +1
And: Which headers are currently included?

> I'm definitely for it.  Our libgmp build can serve as a testbed.  I'd
> be also willing to write some code to facilitate this.  How would you
> envision the implementation, Dago?

I just tried this out in the shell..

igalic at unstable10x ...ar/pkg/hwloc/trunk/work/solaris9-i386 % for f in $( find install-isa-i386/opt/csw/include/ -type f ) ; do
x86="${f}"
amd64="${f/install-isa-i386/install-isa-amd64}"
diff -D __amd64 "${x86}" "${amd64}"
done

And found some rather disturbing things

/* Defined to 1 if you have the <stdint.h> header file. */
#ifndef __amd64
/* #  undef HWLOC_HAVE_STDINT_H */
#else /* __amd64 */
#  define HWLOC_HAVE_STDINT_H 1
#endif /* __amd64 */


> Maciej

i

-- 
Igor Gali?

Tel: +43 (0) 664 886 22 883
Mail: i.galic at brainsware.org
URL: http://brainsware.org/
GPG: 571B 8B8A FC97 266D BDA3  EF6F 43AD 80A4 5779 3257

From juraj at lutter.sk  Thu Sep  8 13:49:34 2011
From: juraj at lutter.sk (Juraj Lutter)
Date: Thu, 08 Sep 2011 12:49:34 +0100
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <9f53450b-55ff-4db0-baec-d45278c814f4@email.android.com>
References: <a3e2ffdb-1dc4-4829-972d-67d419014151@iris>
	<472d8e31-144d-40ae-b467-8f2a2afe3a3c@email.android.com>
	<CABY0g1VtY3SezofmfVZuhFKETMEk9jK8MWsW9omJ6ygvQzz8Mw@mail.gmail.com>
	<9f53450b-55ff-4db0-baec-d45278c814f4@email.android.com>
Message-ID: <99b8228d3469eebcfe0861fcb5c0e6c3@wilbury.sk>

  

I would go with alternatives. It's elegant and "systematic"
approach. 

On 08.09.2011 12:46, Ben Walton wrote: 

> If we use
alternatives, presumably we'd set the deprecated version as higher
priority. Sites would then need to change scripts or run a command to
switch the alternative.
> 
> I think the key its that whatever we choose
needs to be advertised well...and well in advance of delivering the new
package.
> 
> Thanks
> -Ben

-- 
Juraj Lutter | / ASCII Ribbon
Campaign
otis (at) wilbury (dot) sk | / - NO HTML/RTF in
e-mail
http://www.wilbury.sk/ | / - NO Word docs in e-mail
JID: otis
(at) jabber (dot) vx (dot) sk
!07/11 PDP a ni deppart m'I !pleH
  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20110908/78306c92/attachment-0001.html>

From juraj at lutter.sk  Fri Sep  9 10:47:35 2011
From: juraj at lutter.sk (Juraj Lutter)
Date: Fri, 09 Sep 2011 09:47:35 +0100
Subject: [csw-maintainers] mgar makepatch for more than one patch
In-Reply-To: <CALtRa-4Hc_7HCqgq9BBxpCFLbdeN-XdMbt6kdsqdGGZn5NVSCg@mail.gmail.com>
References: <CALtRa-4Hc_7HCqgq9BBxpCFLbdeN-XdMbt6kdsqdGGZn5NVSCg@mail.gmail.com>
Message-ID: <b1b1840e7f9be8f76f7a5b37f78428a1@wilbury.sk>

On 09.09.2011 09:44, Maciej Blizi?ski wrote:
> Hi Ben,
>
> Let's say you have made a couple edits to the sources and you want to
> make patches for GAR, but you don't want to make one big patch.
> Instead, you want a series of patches that you could individually
> offer upstream.  How would you do that in GAR+git?  What sequence of
> commands would you use?

"gmake makepatch" after patching each particular "functional block."


-- 
Juraj Lutter                            |  /\  ASCII Ribbon Campaign
otis (at) wilbury (dot) sk              |  \/  - NO HTML/RTF in e-mail
http://www.wilbury.sk/                  |  /\  - NO Word docs in e-mail
JID: otis (at) jabber (dot) vx (dot) sk
!07/11 PDP a ni deppart m'I  !pleH

From juraj at lutter.sk  Fri Sep  9 15:43:39 2011
From: juraj at lutter.sk (Juraj Lutter)
Date: Fri, 09 Sep 2011 14:43:39 +0100
Subject: [csw-maintainers] mgar makepatch for more than one patch
In-Reply-To: <CALtRa-53SNthct_YSKbxpPgD9YcCfFvLf3jn8cGQ29n4APXyyg@mail.gmail.com>
References: <CALtRa-4Hc_7HCqgq9BBxpCFLbdeN-XdMbt6kdsqdGGZn5NVSCg@mail.gmail.com>
	<1315571190-sup-1432@pinkfloyd.chass.utoronto.ca>
	<CALtRa-53SNthct_YSKbxpPgD9YcCfFvLf3jn8cGQ29n4APXyyg@mail.gmail.com>
Message-ID: <93e3a2301a57cfba4a275065828e590a@wilbury.sk>

On 09.09.2011 14:38, Maciej Blizi?ski wrote:
> 2011/9/9 Ben Walton <bwalton at opencsw.org>:
>> Does this help? ?Would re-runnable makepatch be worth the effort?
>
> How about splitting makepatch in two parts:
>
> mgar stagepatch
> mgar makepatch
>
> The first would run git stage -p + git commit.  You would run it a
> number of times until all changes would be committed.  You'd then run
> mgar makepatch to generate the patch files, update the Makefile, and
> then go "mgar clean package" to test whether the build recipe works.

How would "make stagepatch" know of all the "areas" or "logical blocks" 
of code
that you have changes in order to generate a patch for each particular 
block?

-- 
Juraj Lutter                            |  /\  ASCII Ribbon Campaign
otis (at) wilbury (dot) sk              |  \/  - NO HTML/RTF in e-mail
http://www.wilbury.sk/                  |  /\  - NO Word docs in e-mail
JID: otis (at) jabber (dot) vx (dot) sk
!07/11 PDP a ni deppart m'I  !pleH

From rupert.thurner at gmail.com  Sun Sep 11 13:21:18 2011
From: rupert.thurner at gmail.com (rupert THURNER)
Date: Sun, 11 Sep 2011 13:21:18 +0200
Subject: [csw-maintainers] alphabetical order of suggestions
Message-ID: <CAJs9aZ8=Q8BtoX1VR7p5+7R5Asgh52=VCoZkROgrv5MRRK66ow@mail.gmail.com>

would it be possible that checkpkg orders its suggestions alphabetical
per package?

From maciej at opencsw.org  Sun Sep 11 22:08:20 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sun, 11 Sep 2011 21:08:20 +0100
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <99b8228d3469eebcfe0861fcb5c0e6c3@wilbury.sk>
References: <a3e2ffdb-1dc4-4829-972d-67d419014151@iris>
	<472d8e31-144d-40ae-b467-8f2a2afe3a3c@email.android.com>
	<CABY0g1VtY3SezofmfVZuhFKETMEk9jK8MWsW9omJ6ygvQzz8Mw@mail.gmail.com>
	<9f53450b-55ff-4db0-baec-d45278c814f4@email.android.com>
	<99b8228d3469eebcfe0861fcb5c0e6c3@wilbury.sk>
Message-ID: <CALtRa-4j=uD0-mGoT+nhipvumsvQMw3sS8ECfgFM2qUzG3dfGQ@mail.gmail.com>

2011/9/8 Juraj Lutter <juraj at lutter.sk>:
> I would go with alternatives. It's elegant and "systematic" approach.

Right.  We tried that and it doesn't work.

http://lists.opencsw.org/pipermail/maintainers/2011-September/015352.html

From maciej at opencsw.org  Mon Sep 12 01:26:34 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Mon, 12 Sep 2011 00:26:34 +0100
Subject: [csw-maintainers] alphabetical order of suggestions
In-Reply-To: <CAJs9aZ8=Q8BtoX1VR7p5+7R5Asgh52=VCoZkROgrv5MRRK66ow@mail.gmail.com>
References: <CAJs9aZ8=Q8BtoX1VR7p5+7R5Asgh52=VCoZkROgrv5MRRK66ow@mail.gmail.com>
Message-ID: <CALtRa-7rskpQwbKxP3KSTQsKnYFuHOb=KdS0NwDtW__wwpU58w@mail.gmail.com>

2011/9/11 rupert THURNER <rupert.thurner at gmail.com>:
> would it be possible that checkpkg orders its suggestions alphabetical
> per package?

Not easily.  There currently exists no abstraction to group
suggestions by package.  It surely can be done, but it's not a
question of simply adding sort() in one place.

Maciej

From bwalton at opencsw.org  Mon Sep 12 15:51:32 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Mon, 12 Sep 2011 09:51:32 -0400
Subject: [csw-maintainers] mgar makepatch for more than one patch
In-Reply-To: <93e3a2301a57cfba4a275065828e590a@wilbury.sk>
References: <CALtRa-4Hc_7HCqgq9BBxpCFLbdeN-XdMbt6kdsqdGGZn5NVSCg@mail.gmail.com>
	<1315571190-sup-1432@pinkfloyd.chass.utoronto.ca>
	<CALtRa-53SNthct_YSKbxpPgD9YcCfFvLf3jn8cGQ29n4APXyyg@mail.gmail.com>
	<93e3a2301a57cfba4a275065828e590a@wilbury.sk>
Message-ID: <1315835458-sup-9278@pinkfloyd.chass.utoronto.ca>

Excerpts from Juraj Lutter's message of Fri Sep 09 09:43:39 -0400 2011:

> How would "make stagepatch" know of all the "areas" or "logical
> blocks" of code that you have changes in order to generate a patch
> for each particular block?

It will drive "git add -p" (equivalent to: git stage -p) so that the
caller gits to pick and choose hunks for inclusion.

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From maciej at opencsw.org  Mon Sep 12 19:11:35 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Mon, 12 Sep 2011 18:11:35 +0100
Subject: [csw-maintainers] GCC temporarily broken on the buildfarm
Message-ID: <CALtRa-7bzaJM07BMLn3CUUMxDTubvH_5KKu4JVAZnq_N2uVpGA@mail.gmail.com>

If you try to compile with GCC on the buildfarm, you'll see:

ld: fatal: library -lgcc_s: not found

It's because of the CSWlibgcc-s1 package from gcc-4.6.1 being in
disagreement with CSWgcc4core form gcc-4.3.3.  But fear not!  I'm just
finishing a gcc-4.6.1 build on the resurrected unstable10x, will
upload it to unstable later today, and we'll update the buildfarm with
the new and shiny gcc-4.6.1.

Maciej

From maciej at opencsw.org  Tue Sep 13 05:12:04 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Tue, 13 Sep 2011 04:12:04 +0100
Subject: [csw-maintainers] GCC temporarily broken on the buildfarm
In-Reply-To: <CALtRa-7bzaJM07BMLn3CUUMxDTubvH_5KKu4JVAZnq_N2uVpGA@mail.gmail.com>
References: <CALtRa-7bzaJM07BMLn3CUUMxDTubvH_5KKu4JVAZnq_N2uVpGA@mail.gmail.com>
Message-ID: <CALtRa-4kzj41qbCjH3NgZFfJEShjUEd8tHyQfvL=1sOUvnLrcg@mail.gmail.com>

2011/9/12 Maciej (Matchek) Blizi?ski <maciej at opencsw.org>:
> It's because of the CSWlibgcc-s1 package from gcc-4.6.1 being in
> disagreement with CSWgcc4core form gcc-4.3.3. ?But fear not! ?I'm just
> finishing a gcc-4.6.1 build on the resurrected unstable10x, will
> upload it to unstable later today, and we'll update the buildfarm with
> the new and shiny gcc-4.6.1.

gcc on the buildfarm has been unbroken.

maciej at unstable9s :~ > gcc --version
gcc (GCC) 4.6.1
Copyright (C) 2011 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

One bigger change is that the gcc binary lives now in /opt/csw/bin
instead of /opt/csw/gcc4/bin.  There is a legacy symlink provided:

maciej at unstable9s :~ > ls -l /opt/csw/gcc4/bin/gcc
lrwxrwxrwx   1 root     other         17 Sep 12 23:14
/opt/csw/gcc4/bin/gcc -> ../../bin/gcc-4.6

Maciej

From maciej at opencsw.org  Tue Sep 13 17:35:27 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Tue, 13 Sep 2011 16:35:27 +0100
Subject: [csw-maintainers] GCC 4.6 progress
In-Reply-To: <CALtRa-7Uvy3thSB1Wdf70tuPG5qn1rSNrbmU_4T+2i0TMTLOCw@mail.gmail.com>
References: <CALtRa-6Ho-vowyruOnhysuY4njq5CE98Hr3_WgyHDBUM2tKPEg@mail.gmail.com>
	<CALtRa-7i5B1APocaBRRLe8C-BMGwpzRJEHMSVP=_voOUmHqmsw@mail.gmail.com>
	<CALtRa-6K7FFdhKHfm1eK-vcz9xY=ek-g_9UYQ93UoNd05YXvQQ@mail.gmail.com>
	<CALtRa-7kNA7wUhjJLwgsid7+W4Kx1esXuyag=9yibdyvCayPBg@mail.gmail.com>
	<CALtRa-7xzHQBv6ZHM=iwXONDLGJeWebGjdS9dTbNZYCZ-c_KEA@mail.gmail.com>
	<x6aabak74x.fsf@opencsw.org>
	<CALtRa-6xLfut0JtQEtP=kZHL371X7JDX5jUkJiezwWXj7Kvf7w@mail.gmail.com>
	<x662lyk0ds.fsf@opencsw.org>
	<CALtRa-6X6mJYy9wWpx-mmpO5X+rRY35+eN4+zM53_MFJ6KA7fQ@mail.gmail.com>
	<CALtRa-70hROnmkr-TTyrTbt54xFzaRn54jCOn8PSpS3fwLEJJA@mail.gmail.com>
	<CALtRa-5bPYfprBKH++cW8wN+q8e08WZ7eH5e6OGaD_eQ6-t_fA@mail.gmail.com>
	<DE8738C4-7BC7-4597-A1BF-BDB097FEECC6@opencsw.org>
	<CALtRa-6Vb0u34sE7NHX1Ca4mDBMY3kyt3CfnGWpQO37GV-d5-w@mail.gmail.com>
	<CALtRa-57epz9gHyfNVzAGELa-7Km_Jxab2cRAYu0mWm5sBdKQw@mail.gmail.com>
	<CALtRa-7VDgk7Rc7JRbbR_1bheHFe0hC6yoRW7up5ZOe0eZsVMQ@mail.gmail.com>
	<CALtRa-7Uvy3thSB1Wdf70tuPG5qn1rSNrbmU_4T+2i0TMTLOCw@mail.gmail.com>
Message-ID: <CALtRa-6cQ+t8vhq2NXNP4V3jPeig2Ds7LxQ+GX55gf2LqEEfUw@mail.gmail.com>

gcc-4.6.1 is already installed on the buildfarm. Has anyone built any
packages with it? If there are any problems, please report them. We need to
test the gcc packages before we push them to dublin.

If you make any successful builds, pkease report them too - it is good to
receive positive feedback as well.

Maciej
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20110913/2b7a26bf/attachment-0001.html>

From skayser at opencsw.org  Tue Sep 13 19:56:31 2011
From: skayser at opencsw.org (Sebastian Kayser)
Date: Tue, 13 Sep 2011 19:56:31 +0200
Subject: [csw-maintainers] GCC 4.6 progress
In-Reply-To: <CALtRa-6cQ+t8vhq2NXNP4V3jPeig2Ds7LxQ+GX55gf2LqEEfUw@mail.gmail.com>
References: <x662lyk0ds.fsf@opencsw.org>
	<CALtRa-6X6mJYy9wWpx-mmpO5X+rRY35+eN4+zM53_MFJ6KA7fQ@mail.gmail.com>
	<CALtRa-70hROnmkr-TTyrTbt54xFzaRn54jCOn8PSpS3fwLEJJA@mail.gmail.com>
	<CALtRa-5bPYfprBKH++cW8wN+q8e08WZ7eH5e6OGaD_eQ6-t_fA@mail.gmail.com>
	<DE8738C4-7BC7-4597-A1BF-BDB097FEECC6@opencsw.org>
	<CALtRa-6Vb0u34sE7NHX1Ca4mDBMY3kyt3CfnGWpQO37GV-d5-w@mail.gmail.com>
	<CALtRa-57epz9gHyfNVzAGELa-7Km_Jxab2cRAYu0mWm5sBdKQw@mail.gmail.com>
	<CALtRa-7VDgk7Rc7JRbbR_1bheHFe0hC6yoRW7up5ZOe0eZsVMQ@mail.gmail.com>
	<CALtRa-7Uvy3thSB1Wdf70tuPG5qn1rSNrbmU_4T+2i0TMTLOCw@mail.gmail.com>
	<CALtRa-6cQ+t8vhq2NXNP4V3jPeig2Ds7LxQ+GX55gf2LqEEfUw@mail.gmail.com>
Message-ID: <20110913175631.GF16203@sebastiankayser.de>

Hi Maciej,

* Maciej (Matchek) Blizi??ski <maciej at opencsw.org> wrote:
>    gcc-4.6.1 is already installed on the buildfarm. Has anyone built any
>    packages with it? If there are any problems, please report them. We need
>    to test the gcc packages before we push them to dublin.
> 
>    If you make any successful builds, pkease report them too - it is good to
>    receive positive feedback as well.

(disclaimer: very shallow build report)

Just built fio [1] with GARCOMPILER = GCC4 (changed from GCC3). build9s
fails to include getopt [2], unstable9s builds just fine [3]. No deeper
investigation or tests yet.

Sebastian

[1] https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/fio/trunk/Makefile
[2] http://paste.pocoo.org/show/475352/
[3] http://paste.pocoo.org/show/475357/

From maciej at opencsw.org  Wed Sep 14 09:01:48 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Wed, 14 Sep 2011 08:01:48 +0100
Subject: [csw-maintainers] GCC 4.6 progress
In-Reply-To: <20110913175631.GF16203@sebastiankayser.de>
References: <x662lyk0ds.fsf@opencsw.org>
	<CALtRa-6X6mJYy9wWpx-mmpO5X+rRY35+eN4+zM53_MFJ6KA7fQ@mail.gmail.com>
	<CALtRa-70hROnmkr-TTyrTbt54xFzaRn54jCOn8PSpS3fwLEJJA@mail.gmail.com>
	<CALtRa-5bPYfprBKH++cW8wN+q8e08WZ7eH5e6OGaD_eQ6-t_fA@mail.gmail.com>
	<DE8738C4-7BC7-4597-A1BF-BDB097FEECC6@opencsw.org>
	<CALtRa-6Vb0u34sE7NHX1Ca4mDBMY3kyt3CfnGWpQO37GV-d5-w@mail.gmail.com>
	<CALtRa-57epz9gHyfNVzAGELa-7Km_Jxab2cRAYu0mWm5sBdKQw@mail.gmail.com>
	<CALtRa-7VDgk7Rc7JRbbR_1bheHFe0hC6yoRW7up5ZOe0eZsVMQ@mail.gmail.com>
	<CALtRa-7Uvy3thSB1Wdf70tuPG5qn1rSNrbmU_4T+2i0TMTLOCw@mail.gmail.com>
	<CALtRa-6cQ+t8vhq2NXNP4V3jPeig2Ds7LxQ+GX55gf2LqEEfUw@mail.gmail.com>
	<20110913175631.GF16203@sebastiankayser.de>
Message-ID: <CALtRa-5_4LtVdtWfafCH+KF0G3T9eypYUe12YK-GY=OdvswFOg@mail.gmail.com>

Em 13/09/2011 19:56, "Sebastian Kayser" <skayser at opencsw.org> escreveu:
>
> Hi Maciej,
>
> * Maciej (Matchek) Blizi??ski <maciej at opencsw.org> wrote:
> >    gcc-4.6.1 is already installed on the buildfarm. Has anyone built any
> >    packages with it? If there are any problems, please report them. We
need
> >    to test the gcc packages before we push them to dublin.
> >
> >    If you make any successful builds, pkease report them too - it is
good to
> >    receive positive feedback as well.
>
> (disclaimer: very shallow build report)
>
> Just built fio [1] with GARCOMPILER = GCC4 (changed from GCC3). build9s
> fails to include getopt [2], unstable9s builds just fine [3]. No deeper
> investigation or tests yet.

Thanks.

I think that the build* hosts don't have the right packages installed. We
build on the unstable* hosts these days.

I'm glad that the compiler passes the smoke test.

I'm out for the rest of the week, so I'll resume the work towards Ada in the
next week.

I also rebuilt gcc-3, but that will require some more work to slice it up to
the right packages. The gcc-4 packages could also use some polishing,
especially in the regex area. For example, there are file conflicts between
gcc4core and gcc4java, simply because it's fiddly to write a set of regexes
that will do the right thing.

But I've spent a month pounding the gcc packages and would like to do
something else now. One large bit to do is the buildfarm database schema
update.

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

From jcraig at opencsw.org  Wed Sep 14 13:42:33 2011
From: jcraig at opencsw.org (Jonathan Craig)
Date: Wed, 14 Sep 2011 07:42:33 -0400
Subject: [csw-maintainers] GCC 4.6 progress
In-Reply-To: <CALtRa-6cQ+t8vhq2NXNP4V3jPeig2Ds7LxQ+GX55gf2LqEEfUw@mail.gmail.com>
References: <CALtRa-6Ho-vowyruOnhysuY4njq5CE98Hr3_WgyHDBUM2tKPEg@mail.gmail.com>
	<CALtRa-7i5B1APocaBRRLe8C-BMGwpzRJEHMSVP=_voOUmHqmsw@mail.gmail.com>
	<CALtRa-6K7FFdhKHfm1eK-vcz9xY=ek-g_9UYQ93UoNd05YXvQQ@mail.gmail.com>
	<CALtRa-7kNA7wUhjJLwgsid7+W4Kx1esXuyag=9yibdyvCayPBg@mail.gmail.com>
	<CALtRa-7xzHQBv6ZHM=iwXONDLGJeWebGjdS9dTbNZYCZ-c_KEA@mail.gmail.com>
	<x6aabak74x.fsf@opencsw.org>
	<CALtRa-6xLfut0JtQEtP=kZHL371X7JDX5jUkJiezwWXj7Kvf7w@mail.gmail.com>
	<x662lyk0ds.fsf@opencsw.org>
	<CALtRa-6X6mJYy9wWpx-mmpO5X+rRY35+eN4+zM53_MFJ6KA7fQ@mail.gmail.com>
	<CALtRa-70hROnmkr-TTyrTbt54xFzaRn54jCOn8PSpS3fwLEJJA@mail.gmail.com>
	<CALtRa-5bPYfprBKH++cW8wN+q8e08WZ7eH5e6OGaD_eQ6-t_fA@mail.gmail.com>
	<DE8738C4-7BC7-4597-A1BF-BDB097FEECC6@opencsw.org>
	<CALtRa-6Vb0u34sE7NHX1Ca4mDBMY3kyt3CfnGWpQO37GV-d5-w@mail.gmail.com>
	<CALtRa-57epz9gHyfNVzAGELa-7Km_Jxab2cRAYu0mWm5sBdKQw@mail.gmail.com>
	<CALtRa-7VDgk7Rc7JRbbR_1bheHFe0hC6yoRW7up5ZOe0eZsVMQ@mail.gmail.com>
	<CALtRa-7Uvy3thSB1Wdf70tuPG5qn1rSNrbmU_4T+2i0TMTLOCw@mail.gmail.com>
	<CALtRa-6cQ+t8vhq2NXNP4V3jPeig2Ds7LxQ+GX55gf2LqEEfUw@mail.gmail.com>
Message-ID: <CAH40YUKg4BW8n=DL953Kft5pHTk3Rde-Ghd4coKtvYJw+qyqnw@mail.gmail.com>

2011/9/13 Maciej (Matchek) Blizi?ski <maciej at opencsw.org>:
> gcc-4.6.1 is already installed on the buildfarm. Has anyone built any
> packages with it? If there are any problems, please report them. We need to
> test the gcc packages before we push them to dublin.
>
> If you make any successful builds, pkease report them too - it is good to
> receive positive feedback as well.
>

Not sure if this is related but I'm in the middle of a project at work
where a install of ruby gem fastthread succeeds on a box with gcc
4.3.3 and fails on another box with gcc 4.6.1.

4.3.3 host:
/opt/csw/gcc4/bin/gcc -I. -I/opt/csw/lib/ruby/1.8/i386-solaris2.9
-I/opt/csw/lib/ruby/1.8/i386-solaris2.9 -I. -I/opt/csw/include
-D_FILE_OFFSET_BITS=64  -fPIC -mtune=i686 -O2 -pipe -m32 -march=i386
-fPIC  -c fastthread.c

4.6.6 host:
/opt/csw/gcc4/bin/gcc -I. -I/opt/csw/lib/ruby/1.8/i386-solaris2.9
-I/opt/csw/lib/ruby/1.8/i386-solaris2.9 -I. -I/opt/csw/include
-D_FILE_OFFSET_BITS=64  -fPIC -mtune=i686 -O2 -pipe -m32 -march=i386
-fPIC   -c fastthread.c
In file included from fastthread.c:12:0:
/opt/csw/lib/ruby/1.8/i386-solaris2.9/ruby.h:40:21: fatal error:
stdlib.h: No such file or directory
compilation terminated.
make: *** [fastthread.o] Error 1

From opk at opencsw.org  Wed Sep 14 15:04:28 2011
From: opk at opencsw.org (Oliver Kiddle)
Date: Wed, 14 Sep 2011 15:04:28 +0200
Subject: [csw-maintainers] GCC 4.6 progress
In-Reply-To: <CALtRa-6cQ+t8vhq2NXNP4V3jPeig2Ds7LxQ+GX55gf2LqEEfUw@mail.gmail.com>
References: <CALtRa-6Ho-vowyruOnhysuY4njq5CE98Hr3_WgyHDBUM2tKPEg@mail.gmail.com>
	<CALtRa-7i5B1APocaBRRLe8C-BMGwpzRJEHMSVP=_voOUmHqmsw@mail.gmail.com>
	<CALtRa-6K7FFdhKHfm1eK-vcz9xY=ek-g_9UYQ93UoNd05YXvQQ@mail.gmail.com>
	<CALtRa-7kNA7wUhjJLwgsid7+W4Kx1esXuyag=9yibdyvCayPBg@mail.gmail.com>
	<CALtRa-7xzHQBv6ZHM=iwXONDLGJeWebGjdS9dTbNZYCZ-c_KEA@mail.gmail.com>
	<x6aabak74x.fsf@opencsw.org>
	<CALtRa-6xLfut0JtQEtP=kZHL371X7JDX5jUkJiezwWXj7Kvf7w@mail.gmail.com>
	<x662lyk0ds.fsf@opencsw.org>
	<CALtRa-6X6mJYy9wWpx-mmpO5X+rRY35+eN4+zM53_MFJ6KA7fQ@mail.gmail.com>
	<CALtRa-70hROnmkr-TTyrTbt54xFzaRn54jCOn8PSpS3fwLEJJA@mail.gmail.com>
	<CALtRa-5bPYfprBKH++cW8wN+q8e08WZ7eH5e6OGaD_eQ6-t_fA@mail.gmail.com>
	<DE8738C4-7BC7-4597-A1BF-BDB097FEECC6@opencsw.org>
	<CALtRa-6Vb0u34sE7NHX1Ca4mDBMY3kyt3CfnGWpQO37GV-d5-w@mail.gmail.com>
	<CALtRa-57epz9gHyfNVzAGELa-7Km_Jxab2cRAYu0mWm5sBdKQw@mail.gmail.com>
	<CALtRa-7VDgk7Rc7JRbbR_1bheHFe0hC6yoRW7up5ZOe0eZsVMQ@mail.gmail.com>
	<CALtRa-7Uvy3thSB1Wdf70tuPG5qn1rSNrbmU_4T
	+2i0TMTLOCw@mail.gmail.com>
	<CALtRa-6cQ+t8vhq2NXNP4V3jPeig2Ds7LxQ+GX55gf2LqEEfUw@mail.gmail.com>
Message-ID: <7875.1316005468@thecus.kiddle.eu>

Maciej (Matchek) Blizi??ski wrote:
> gcc-4.6.1 is already installed on the buildfarm. Has anyone built any packages
> with it? If there are any problems, please report them. We need to test the gcc
> packages before we push them to dublin.

The C part works ok but I'm having trouble getting g++ to work. With a
simple hello world program, I get:
/usr/ccs/bin/as: "/var/tmp//ccM6Znh2.s", line 144: error: unknown opcode ".weakref"
/usr/ccs/bin/as: "/var/tmp//ccM6Znh2.s", line 144: error: statement syntax

Do I need to to install anything extra?

Oliver

From wilbury at opencsw.org  Wed Sep 14 15:11:39 2011
From: wilbury at opencsw.org (Juraj Lutter)
Date: Wed, 14 Sep 2011 14:11:39 +0100
Subject: [csw-maintainers] GCC 4.6 progress
In-Reply-To: <7875.1316005468@thecus.kiddle.eu>
References: <CALtRa-6Ho-vowyruOnhysuY4njq5CE98Hr3_WgyHDBUM2tKPEg@mail.gmail.com>
	<CALtRa-7i5B1APocaBRRLe8C-BMGwpzRJEHMSVP=_voOUmHqmsw@mail.gmail.com>
	<CALtRa-6K7FFdhKHfm1eK-vcz9xY=ek-g_9UYQ93UoNd05YXvQQ@mail.gmail.com>
	<CALtRa-7kNA7wUhjJLwgsid7+W4Kx1esXuyag=9yibdyvCayPBg@mail.gmail.com>
	<CALtRa-7xzHQBv6ZHM=iwXONDLGJeWebGjdS9dTbNZYCZ-c_KEA@mail.gmail.com>
	<x6aabak74x.fsf@opencsw.org>
	<CALtRa-6xLfut0JtQEtP=kZHL371X7JDX5jUkJiezwWXj7Kvf7w@mail.gmail.com>
	<x662lyk0ds.fsf@opencsw.org>
	<CALtRa-6X6mJYy9wWpx-mmpO5X+rRY35+eN4+zM53_MFJ6KA7fQ@mail.gmail.com>
	<CALtRa-70hROnmkr-TTyrTbt54xFzaRn54jCOn8PSpS3fwLEJJA@mail.gmail.com>
	<CALtRa-5bPYfprBKH++cW8wN+q8e08WZ7eH5e6OGaD_eQ6-t_fA@mail.gmail.com>
	<DE8738C4-7BC7-4597-A1BF-BDB097FEECC6@opencsw.org>
	<CALtRa-6Vb0u34sE7NHX1Ca4mDBMY3kyt3CfnGWpQO37GV-d5-w@mail.gmail.com>
	<CALtRa-57epz9gHyfNVzAGELa-7Km_Jxab2cRAYu0mWm5sBdKQw@mail.gmail.com>
	<CALtRa-7VDgk7Rc7JRbbR_1bheHFe0hC6yoRW7up5ZOe0eZsVMQ@mail.gmail.com>
	<CALtRa-7Uvy3thSB1Wdf70tuPG5qn1rSNrbmU_4T +2i0TMTLOCw@mail.gmail.com>
	<CALtRa-6cQ+t8vhq2NXNP4V3jPeig2Ds7LxQ+GX55gf2LqEEfUw@mail.gmail.com>
	<7875.1316005468@thecus.kiddle.eu>
Message-ID: <19ae49c21bb51c03d89c05400f00f9b6@wilbury.sk>

On 2011-09-14 14:04, Oliver Kiddle wrote:
> The C part works ok but I'm having trouble getting g++ to work. With 
> a
> simple hello world program, I get:
> /usr/ccs/bin/as: "/var/tmp//ccM6Znh2.s", line 144: error: unknown
> opcode ".weakref"
> /usr/ccs/bin/as: "/var/tmp//ccM6Znh2.s", line 144: error: statement 
> syntax
>

The compiler should be built with-gnu-gas.


--
Juraj Lutter <wilbury at opencsw.org>

From maciej at opencsw.org  Wed Sep 14 20:14:25 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Wed, 14 Sep 2011 19:14:25 +0100
Subject: [csw-maintainers] GCC 4.6 progress
In-Reply-To: <7875.1316005468@thecus.kiddle.eu>
References: <CALtRa-6Ho-vowyruOnhysuY4njq5CE98Hr3_WgyHDBUM2tKPEg@mail.gmail.com>
	<CALtRa-7i5B1APocaBRRLe8C-BMGwpzRJEHMSVP=_voOUmHqmsw@mail.gmail.com>
	<CALtRa-6K7FFdhKHfm1eK-vcz9xY=ek-g_9UYQ93UoNd05YXvQQ@mail.gmail.com>
	<CALtRa-7kNA7wUhjJLwgsid7+W4Kx1esXuyag=9yibdyvCayPBg@mail.gmail.com>
	<CALtRa-7xzHQBv6ZHM=iwXONDLGJeWebGjdS9dTbNZYCZ-c_KEA@mail.gmail.com>
	<x6aabak74x.fsf@opencsw.org>
	<CALtRa-6xLfut0JtQEtP=kZHL371X7JDX5jUkJiezwWXj7Kvf7w@mail.gmail.com>
	<x662lyk0ds.fsf@opencsw.org>
	<CALtRa-6X6mJYy9wWpx-mmpO5X+rRY35+eN4+zM53_MFJ6KA7fQ@mail.gmail.com>
	<CALtRa-70hROnmkr-TTyrTbt54xFzaRn54jCOn8PSpS3fwLEJJA@mail.gmail.com>
	<CALtRa-5bPYfprBKH++cW8wN+q8e08WZ7eH5e6OGaD_eQ6-t_fA@mail.gmail.com>
	<DE8738C4-7BC7-4597-A1BF-BDB097FEECC6@opencsw.org>
	<CALtRa-6Vb0u34sE7NHX1Ca4mDBMY3kyt3CfnGWpQO37GV-d5-w@mail.gmail.com>
	<CALtRa-57epz9gHyfNVzAGELa-7Km_Jxab2cRAYu0mWm5sBdKQw@mail.gmail.com>
	<CALtRa-7VDgk7Rc7JRbbR_1bheHFe0hC6yoRW7up5ZOe0eZsVMQ@mail.gmail.com>
	<CALtRa-6cQ+t8vhq2NXNP4V3jPeig2Ds7LxQ+GX55gf2LqEEfUw@mail.gmail.com>
	<7875.1316005468@thecus.kiddle.eu>
Message-ID: <CALtRa-5PcCZRFHX8y0su0nhhFg-fWB8_G+7-yjSk964evHw8Vg@mail.gmail.com>

2011/9/14 Oliver Kiddle <opk at opencsw.org>:
> Maciej (Matchek) Blizi?ski wrote:
>> gcc-4.6.1 is already installed on the buildfarm. Has anyone built any packages
>> with it? If there are any problems, please report them. We need to test the gcc
>> packages before we push them to dublin.
>
> The C part works ok but I'm having trouble getting g++ to work. With a
> simple hello world program, I get:
> /usr/ccs/bin/as: "/var/tmp//ccM6Znh2.s", line 144: error: unknown opcode ".weakref"
> /usr/ccs/bin/as: "/var/tmp//ccM6Znh2.s", line 144: error: statement syntax
>
> Do I need to to install anything extra?

If you type "gcc -v", it will print the options it has been built
with.  Part of them are:

--with-gnu-as --with-as=/opt/csw/bin/gas

I'm not sure why is it trying to use /usr/ccs/bin/as.  Do you have
/opt/csw/bin/gas in the filesystem?  If not, then CSWgcc4core needs to
depend on CSWbinutils.

From maciej at opencsw.org  Wed Sep 14 20:25:10 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Wed, 14 Sep 2011 19:25:10 +0100
Subject: [csw-maintainers] GCC 4.6 progress
In-Reply-To: <CAH40YUKg4BW8n=DL953Kft5pHTk3Rde-Ghd4coKtvYJw+qyqnw@mail.gmail.com>
References: <CALtRa-6Ho-vowyruOnhysuY4njq5CE98Hr3_WgyHDBUM2tKPEg@mail.gmail.com>
	<CALtRa-7i5B1APocaBRRLe8C-BMGwpzRJEHMSVP=_voOUmHqmsw@mail.gmail.com>
	<CALtRa-6K7FFdhKHfm1eK-vcz9xY=ek-g_9UYQ93UoNd05YXvQQ@mail.gmail.com>
	<CALtRa-7kNA7wUhjJLwgsid7+W4Kx1esXuyag=9yibdyvCayPBg@mail.gmail.com>
	<CALtRa-7xzHQBv6ZHM=iwXONDLGJeWebGjdS9dTbNZYCZ-c_KEA@mail.gmail.com>
	<x6aabak74x.fsf@opencsw.org>
	<CALtRa-6xLfut0JtQEtP=kZHL371X7JDX5jUkJiezwWXj7Kvf7w@mail.gmail.com>
	<x662lyk0ds.fsf@opencsw.org>
	<CALtRa-6X6mJYy9wWpx-mmpO5X+rRY35+eN4+zM53_MFJ6KA7fQ@mail.gmail.com>
	<CALtRa-70hROnmkr-TTyrTbt54xFzaRn54jCOn8PSpS3fwLEJJA@mail.gmail.com>
	<CALtRa-5bPYfprBKH++cW8wN+q8e08WZ7eH5e6OGaD_eQ6-t_fA@mail.gmail.com>
	<DE8738C4-7BC7-4597-A1BF-BDB097FEECC6@opencsw.org>
	<CALtRa-6Vb0u34sE7NHX1Ca4mDBMY3kyt3CfnGWpQO37GV-d5-w@mail.gmail.com>
	<CALtRa-57epz9gHyfNVzAGELa-7Km_Jxab2cRAYu0mWm5sBdKQw@mail.gmail.com>
	<CALtRa-7VDgk7Rc7JRbbR_1bheHFe0hC6yoRW7up5ZOe0eZsVMQ@mail.gmail.com>
	<CALtRa-7Uvy3thSB1Wdf70tuPG5qn1rSNrbmU_4T+2i0TMTLOCw@mail.gmail.com>
	<CALtRa-6cQ+t8vhq2NXNP4V3jPeig2Ds7LxQ+GX55gf2LqEEfUw@mail.gmail.com>
	<CAH40YUKg4BW8n=DL953Kft5pHTk3Rde-Ghd4coKtvYJw+qyqnw@mail.gmail.com>
Message-ID: <CALtRa-5LH3JUjZCqypJKBy-_hephp2EK3_wqszD3sKgZX2iu2g@mail.gmail.com>

2011/9/14 Jonathan Craig <jcraig at opencsw.org>:
> 2011/9/13 Maciej (Matchek) Blizi?ski <maciej at opencsw.org>:
>> gcc-4.6.1 is already installed on the buildfarm. Has anyone built any
>> packages with it? If there are any problems, please report them. We need to
>> test the gcc packages before we push them to dublin.
>>
>> If you make any successful builds, pkease report them too - it is good to
>> receive positive feedback as well.
>>
>
> Not sure if this is related but I'm in the middle of a project at work
> where a install of ruby gem fastthread succeeds on a box with gcc
> 4.3.3 and fails on another box with gcc 4.6.1.
>
> 4.3.3 host:
> /opt/csw/gcc4/bin/gcc -I. -I/opt/csw/lib/ruby/1.8/i386-solaris2.9
> -I/opt/csw/lib/ruby/1.8/i386-solaris2.9 -I. -I/opt/csw/include
> -D_FILE_OFFSET_BITS=64 ?-fPIC -mtune=i686 -O2 -pipe -m32 -march=i386
> -fPIC ?-c fastthread.c
>
> 4.6.6 host:
> /opt/csw/gcc4/bin/gcc -I. -I/opt/csw/lib/ruby/1.8/i386-solaris2.9
> -I/opt/csw/lib/ruby/1.8/i386-solaris2.9 -I. -I/opt/csw/include
> -D_FILE_OFFSET_BITS=64 ?-fPIC -mtune=i686 -O2 -pipe -m32 -march=i386
> -fPIC ? -c fastthread.c
> In file included from fastthread.c:12:0:
> /opt/csw/lib/ruby/1.8/i386-solaris2.9/ruby.h:40:21: fatal error:
> stdlib.h: No such file or directory
> compilation terminated.
> make: *** [fastthread.o] Error 1

Can you truss the compiler (with -f to also monitor its children) to
see what files it tries to open?  One guess would be is that it tries
to open stdlib.h from the 4.3.3 installation.

Maciej

From pfelecan at opencsw.org  Thu Sep 15 09:36:37 2011
From: pfelecan at opencsw.org (Peter FELECAN)
Date: Thu, 15 Sep 2011 09:36:37 +0200
Subject: [csw-maintainers] GCC 4.6 progress
In-Reply-To: <CALtRa-5_4LtVdtWfafCH+KF0G3T9eypYUe12YK-GY=OdvswFOg@mail.gmail.com>
	("Maciej (Matchek) =?utf-8?Q?Blizi=C5=84ski=22's?= message of "Wed,
	14 Sep 2011 08:01:48 +0100")
References: <x662lyk0ds.fsf@opencsw.org>
	<CALtRa-6X6mJYy9wWpx-mmpO5X+rRY35+eN4+zM53_MFJ6KA7fQ@mail.gmail.com>
	<CALtRa-70hROnmkr-TTyrTbt54xFzaRn54jCOn8PSpS3fwLEJJA@mail.gmail.com>
	<CALtRa-5bPYfprBKH++cW8wN+q8e08WZ7eH5e6OGaD_eQ6-t_fA@mail.gmail.com>
	<DE8738C4-7BC7-4597-A1BF-BDB097FEECC6@opencsw.org>
	<CALtRa-6Vb0u34sE7NHX1Ca4mDBMY3kyt3CfnGWpQO37GV-d5-w@mail.gmail.com>
	<CALtRa-57epz9gHyfNVzAGELa-7Km_Jxab2cRAYu0mWm5sBdKQw@mail.gmail.com>
	<CALtRa-7VDgk7Rc7JRbbR_1bheHFe0hC6yoRW7up5ZOe0eZsVMQ@mail.gmail.com>
	<CALtRa-7Uvy3thSB1Wdf70tuPG5qn1rSNrbmU_4T+2i0TMTLOCw@mail.gmail.com>
	<CALtRa-6cQ+t8vhq2NXNP4V3jPeig2Ds7LxQ+GX55gf2LqEEfUw@mail.gmail.com>
	<20110913175631.GF16203@sebastiankayser.de>
	<CALtRa-5_4LtVdtWfafCH+KF0G3T9eypYUe12YK-GY=OdvswFOg@mail.gmail.com>
Message-ID: <x6fwjygsu2.fsf@opencsw.org>

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

> But I've spent a month pounding the gcc packages and would like to do
> something else now. One large bit to do is the buildfarm database schema
> update.

And you're not at the end of your pains... Welcome to the club.
-- 
Peter

From pfelecan at opencsw.org  Thu Sep 15 09:37:38 2011
From: pfelecan at opencsw.org (Peter FELECAN)
Date: Thu, 15 Sep 2011 09:37:38 +0200
Subject: [csw-maintainers] GCC 4.6 progress
In-Reply-To: <CALtRa-5PcCZRFHX8y0su0nhhFg-fWB8_G+7-yjSk964evHw8Vg@mail.gmail.com>
	("Maciej (Matchek) =?utf-8?Q?Blizi=C5=84ski=22's?= message of "Wed,
	14 Sep 2011 19:14:25 +0100")
References: <CALtRa-6Ho-vowyruOnhysuY4njq5CE98Hr3_WgyHDBUM2tKPEg@mail.gmail.com>
	<CALtRa-7i5B1APocaBRRLe8C-BMGwpzRJEHMSVP=_voOUmHqmsw@mail.gmail.com>
	<CALtRa-6K7FFdhKHfm1eK-vcz9xY=ek-g_9UYQ93UoNd05YXvQQ@mail.gmail.com>
	<CALtRa-7kNA7wUhjJLwgsid7+W4Kx1esXuyag=9yibdyvCayPBg@mail.gmail.com>
	<CALtRa-7xzHQBv6ZHM=iwXONDLGJeWebGjdS9dTbNZYCZ-c_KEA@mail.gmail.com>
	<x6aabak74x.fsf@opencsw.org>
	<CALtRa-6xLfut0JtQEtP=kZHL371X7JDX5jUkJiezwWXj7Kvf7w@mail.gmail.com>
	<x662lyk0ds.fsf@opencsw.org>
	<CALtRa-6X6mJYy9wWpx-mmpO5X+rRY35+eN4+zM53_MFJ6KA7fQ@mail.gmail.com>
	<CALtRa-70hROnmkr-TTyrTbt54xFzaRn54jCOn8PSpS3fwLEJJA@mail.gmail.com>
	<CALtRa-5bPYfprBKH++cW8wN+q8e08WZ7eH5e6OGaD_eQ6-t_fA@mail.gmail.com>
	<DE8738C4-7BC7-4597-A1BF-BDB097FEECC6@opencsw.org>
	<CALtRa-6Vb0u34sE7NHX1Ca4mDBMY3kyt3CfnGWpQO37GV-d5-w@mail.gmail.com>
	<CALtRa-57epz9gHyfNVzAGELa-7Km_Jxab2cRAYu0mWm5sBdKQw@mail.gmail.com>
	<CALtRa-7VDgk7Rc7JRbbR_1bheHFe0hC6yoRW7up5ZOe0eZsVMQ@mail.gmail.com>
	<CALtRa-6cQ+t8vhq2NXNP4V3jPeig2Ds7LxQ+GX55gf2LqEEfUw@mail.gmail.com>
	<7875.1316005468@thecus.kiddle.eu>
	<CALtRa-5PcCZRFHX8y0su0nhhFg-fWB8_G+7-yjSk964evHw8Vg@mail.gmail.com>
Message-ID: <x6boumgssd.fsf@opencsw.org>

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

> I'm not sure why is it trying to use /usr/ccs/bin/as.  Do you have
> /opt/csw/bin/gas in the filesystem?  If not, then CSWgcc4core needs to
> depend on CSWbinutils.

It *must* depend on binutils as the previous i386 packages.
-- 
Peter

From maciej.blizinski at gmail.com  Wed Sep 14 17:53:00 2011
From: maciej.blizinski at gmail.com (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=)
Date: Wed, 14 Sep 2011 16:53:00 +0100
Subject: [csw-maintainers] GCC 4.6 progress
In-Reply-To: <19ae49c21bb51c03d89c05400f00f9b6@wilbury.sk>
References: <CALtRa-6Ho-vowyruOnhysuY4njq5CE98Hr3_WgyHDBUM2tKPEg@mail.gmail.com>
	<CALtRa-7i5B1APocaBRRLe8C-BMGwpzRJEHMSVP=_voOUmHqmsw@mail.gmail.com>
	<CALtRa-6K7FFdhKHfm1eK-vcz9xY=ek-g_9UYQ93UoNd05YXvQQ@mail.gmail.com>
	<CALtRa-7kNA7wUhjJLwgsid7+W4Kx1esXuyag=9yibdyvCayPBg@mail.gmail.com>
	<CALtRa-7xzHQBv6ZHM=iwXONDLGJeWebGjdS9dTbNZYCZ-c_KEA@mail.gmail.com>
	<x6aabak74x.fsf@opencsw.org>
	<CALtRa-6xLfut0JtQEtP=kZHL371X7JDX5jUkJiezwWXj7Kvf7w@mail.gmail.com>
	<x662lyk0ds.fsf@opencsw.org>
	<CALtRa-6X6mJYy9wWpx-mmpO5X+rRY35+eN4+zM53_MFJ6KA7fQ@mail.gmail.com>
	<CALtRa-70hROnmkr-TTyrTbt54xFzaRn54jCOn8PSpS3fwLEJJA@mail.gmail.com>
	<CALtRa-5bPYfprBKH++cW8wN+q8e08WZ7eH5e6OGaD_eQ6-t_fA@mail.gmail.com>
	<DE8738C4-7BC7-4597-A1BF-BDB097FEECC6@opencsw.org>
	<CALtRa-6Vb0u34sE7NHX1Ca4mDBMY3kyt3CfnGWpQO37GV-d5-w@mail.gmail.com>
	<CALtRa-57epz9gHyfNVzAGELa-7Km_Jxab2cRAYu0mWm5sBdKQw@mail.gmail.com>
	<CALtRa-7VDgk7Rc7JRbbR_1bheHFe0hC6yoRW7up5ZOe0eZsVMQ@mail.gmail.com>
	<CALtRa-6cQ+t8vhq2NXNP4V3jPeig2Ds7LxQ+GX55gf2LqEEfUw@mail.gmail.com>
	<7875.1316005468@thecus.kiddle.eu>
	<19ae49c21bb51c03d89c05400f00f9b6@wilbury.sk>
Message-ID: <CALtRa-6+AccMdncsdH-mSr7C99X_aUPudLrndyH6wY4v7eoQXw@mail.gmail.com>

On Sep 14, 2011 3:11 PM, "Juraj Lutter" <wilbury at opencsw.org> wrote:
>
> On 2011-09-14 14:04, Oliver Kiddle wrote:
>>
>> The C part works ok but I'm having trouble getting g++ to work. With a
>> simple hello world program, I get:
>> /usr/ccs/bin/as: "/var/tmp//ccM6Znh2.s", line 144: error: unknown
>> opcode ".weakref"
>> /usr/ccs/bin/as: "/var/tmp//ccM6Znh2.s", line 144: error: statement
syntax
>>
>
> The compiler should be built with-gnu-gas.

Roger that. It will take probably more than 24h to get the new packages in
the catalog.

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

From maciej.blizinski at gmail.com  Wed Sep 14 18:00:49 2011
From: maciej.blizinski at gmail.com (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=)
Date: Wed, 14 Sep 2011 17:00:49 +0100
Subject: [csw-maintainers] GCC 4.6 progress
In-Reply-To: <CALtRa-6+AccMdncsdH-mSr7C99X_aUPudLrndyH6wY4v7eoQXw@mail.gmail.com>
References: <CALtRa-6Ho-vowyruOnhysuY4njq5CE98Hr3_WgyHDBUM2tKPEg@mail.gmail.com>
	<CALtRa-7i5B1APocaBRRLe8C-BMGwpzRJEHMSVP=_voOUmHqmsw@mail.gmail.com>
	<CALtRa-6K7FFdhKHfm1eK-vcz9xY=ek-g_9UYQ93UoNd05YXvQQ@mail.gmail.com>
	<CALtRa-7kNA7wUhjJLwgsid7+W4Kx1esXuyag=9yibdyvCayPBg@mail.gmail.com>
	<CALtRa-7xzHQBv6ZHM=iwXONDLGJeWebGjdS9dTbNZYCZ-c_KEA@mail.gmail.com>
	<x6aabak74x.fsf@opencsw.org>
	<CALtRa-6xLfut0JtQEtP=kZHL371X7JDX5jUkJiezwWXj7Kvf7w@mail.gmail.com>
	<x662lyk0ds.fsf@opencsw.org>
	<CALtRa-6X6mJYy9wWpx-mmpO5X+rRY35+eN4+zM53_MFJ6KA7fQ@mail.gmail.com>
	<CALtRa-70hROnmkr-TTyrTbt54xFzaRn54jCOn8PSpS3fwLEJJA@mail.gmail.com>
	<CALtRa-5bPYfprBKH++cW8wN+q8e08WZ7eH5e6OGaD_eQ6-t_fA@mail.gmail.com>
	<DE8738C4-7BC7-4597-A1BF-BDB097FEECC6@opencsw.org>
	<CALtRa-6Vb0u34sE7NHX1Ca4mDBMY3kyt3CfnGWpQO37GV-d5-w@mail.gmail.com>
	<CALtRa-57epz9gHyfNVzAGELa-7Km_Jxab2cRAYu0mWm5sBdKQw@mail.gmail.com>
	<CALtRa-7VDgk7Rc7JRbbR_1bheHFe0hC6yoRW7up5ZOe0eZsVMQ@mail.gmail.com>
	<CALtRa-6cQ+t8vhq2NXNP4V3jPeig2Ds7LxQ+GX55gf2LqEEfUw@mail.gmail.com>
	<7875.1316005468@thecus.kiddle.eu>
	<19ae49c21bb51c03d89c05400f00f9b6@wilbury.sk>
	<CALtRa-6+AccMdncsdH-mSr7C99X_aUPudLrndyH6wY4v7eoQXw@mail.gmail.com>
Message-ID: <CALtRa-6=mMbH1hYzRA3TZjhaRxb3yVHDgcAq3PADMN0KkFUdXQ@mail.gmail.com>

Hm. This option is in the build recipe already.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20110914/a9f1f85f/attachment.html>

From opk at opencsw.org  Thu Sep 15 19:27:11 2011
From: opk at opencsw.org (Oliver Kiddle)
Date: Thu, 15 Sep 2011 19:27:11 +0200
Subject: [csw-maintainers] GCC 4.6 progress
In-Reply-To: <CALtRa-5PcCZRFHX8y0su0nhhFg-fWB8_G+7-yjSk964evHw8Vg@mail.gmail.com>
References: <CALtRa-6Ho-vowyruOnhysuY4njq5CE98Hr3_WgyHDBUM2tKPEg@mail.gmail.com>
	<CALtRa-7i5B1APocaBRRLe8C-BMGwpzRJEHMSVP=_voOUmHqmsw@mail.gmail.com>
	<CALtRa-6K7FFdhKHfm1eK-vcz9xY=ek-g_9UYQ93UoNd05YXvQQ@mail.gmail.com>
	<CALtRa-7kNA7wUhjJLwgsid7+W4Kx1esXuyag=9yibdyvCayPBg@mail.gmail.com>
	<CALtRa-7xzHQBv6ZHM=iwXONDLGJeWebGjdS9dTbNZYCZ-c_KEA@mail.gmail.com>
	<x6aabak74x.fsf@opencsw.org>
	<CALtRa-6xLfut0JtQEtP=kZHL371X7JDX5jUkJiezwWXj7Kvf7w@mail.gmail.com>
	<x662lyk0ds.fsf@opencsw.org>
	<CALtRa-6X6mJYy9wWpx-mmpO5X+rRY35+eN4+zM53_MFJ6KA7fQ@mail.gmail.com>
	<CALtRa-70hROnmkr-TTyrTbt54xFzaRn54jCOn8PSpS3fwLEJJA@mail.gmail.com>
	<CALtRa-5bPYfprBKH++cW8wN+q8e08WZ7eH5e6OGaD_eQ6-t_fA@mail.gmail.com>
	<DE8738C4-7BC7-4597-A1BF-BDB097FEECC6@opencsw.org>
	<CALtRa-6Vb0u34sE7NHX1Ca4mDBMY3kyt3CfnGWpQO37GV-d5-w@mail.gmail.com>
	<CALtRa-57epz9gHyfNVzAGELa-7Km_Jxab2cRAYu0mWm5sBdKQw@mail.gmail.com>
	<CALtRa-7VDgk7Rc7JRbbR_1bheHFe0hC6yoRW7up5ZOe0eZsVMQ@mail.gmail.com>
	<CALtRa-6cQ+t8vhq2NXNP4V3jPeig2Ds7LxQ+GX5
	5gf2LqEEfUw@mail.gmail.com> <7875.1316005468@thecus.kiddle.eu>
	<CALtRa-5PcCZRFHX8y0su0nhhFg-fWB8_G+7-yjSk964evHw8Vg@mail.gmail.com>
Message-ID: <12089.1316107631@thecus.kiddle.eu>

Maciej (Matchek) Blizi??ski wrote:
> I'm not sure why is it trying to use /usr/ccs/bin/as.  Do you have
> /opt/csw/bin/gas in the filesystem?  If not, then CSWgcc4core needs to
> depend on CSWbinutils.

Ok, that was the problem, I installed CSWbinutils and it now works. So a
dependency is needed.

Thanks, I'll be doing more testing of the C++ compiler.

Oliver

From maciej at opencsw.org  Sat Sep 17 00:10:02 2011
From: maciej at opencsw.org (Maciej =?utf-8?Q?Blizi=C5=84ski?=)
Date: Fri, 16 Sep 2011 23:10:02 +0100
Subject: [csw-maintainers] GCC 4.6 progress
In-Reply-To: <12089.1316107631@thecus.kiddle.eu>
References: <CALtRa-70hROnmkr-TTyrTbt54xFzaRn54jCOn8PSpS3fwLEJJA@mail.gmail.com>
	<CALtRa-5bPYfprBKH++cW8wN+q8e08WZ7eH5e6OGaD_eQ6-t_fA@mail.gmail.com>
	<DE8738C4-7BC7-4597-A1BF-BDB097FEECC6@opencsw.org>
	<CALtRa-6Vb0u34sE7NHX1Ca4mDBMY3kyt3CfnGWpQO37GV-d5-w@mail.gmail.com>
	<CALtRa-57epz9gHyfNVzAGELa-7Km_Jxab2cRAYu0mWm5sBdKQw@mail.gmail.com>
	<CALtRa-7VDgk7Rc7JRbbR_1bheHFe0hC6yoRW7up5ZOe0eZsVMQ@mail.gmail.com>
	<CALtRa-6cQ+t8vhq2NXNP4V3jPeig2Ds7LxQ+GX55gf2LqEEfUw@mail.gmail.com>
	<7875.1316005468@thecus.kiddle.eu>
	<CALtRa-5PcCZRFHX8y0su0nhhFg-fWB8_G+7-yjSk964evHw8Vg@mail.gmail.com>
	<12089.1316107631@thecus.kiddle.eu>
Message-ID: <20110916221002.GA6433@quince.home.blizinski.pl>

Oliver Kiddle wrote:
> Maciej (Matchek) Blizi??ski wrote:
> > I'm not sure why is it trying to use /usr/ccs/bin/as.  Do you have
> > /opt/csw/bin/gas in the filesystem?  If not, then CSWgcc4core needs to
> > depend on CSWbinutils.
> 
> Ok, that was the problem, I installed CSWbinutils and it now works. So a
> dependency is needed.

Cool.  I've modified the build recipe and will reroll the packages.

> Thanks, I'll be doing more testing of the C++ compiler.

The C++ compiler definitely can use more testing.

From maciej at opencsw.org  Sun Sep 18 11:23:41 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sun, 18 Sep 2011 10:23:41 +0100
Subject: [csw-maintainers] GCC 4.6 progress
In-Reply-To: <x6boumgssd.fsf@opencsw.org>
References: <CALtRa-6Ho-vowyruOnhysuY4njq5CE98Hr3_WgyHDBUM2tKPEg@mail.gmail.com>
	<CALtRa-7i5B1APocaBRRLe8C-BMGwpzRJEHMSVP=_voOUmHqmsw@mail.gmail.com>
	<CALtRa-6K7FFdhKHfm1eK-vcz9xY=ek-g_9UYQ93UoNd05YXvQQ@mail.gmail.com>
	<CALtRa-7kNA7wUhjJLwgsid7+W4Kx1esXuyag=9yibdyvCayPBg@mail.gmail.com>
	<CALtRa-7xzHQBv6ZHM=iwXONDLGJeWebGjdS9dTbNZYCZ-c_KEA@mail.gmail.com>
	<x6aabak74x.fsf@opencsw.org>
	<CALtRa-6xLfut0JtQEtP=kZHL371X7JDX5jUkJiezwWXj7Kvf7w@mail.gmail.com>
	<x662lyk0ds.fsf@opencsw.org>
	<CALtRa-6X6mJYy9wWpx-mmpO5X+rRY35+eN4+zM53_MFJ6KA7fQ@mail.gmail.com>
	<CALtRa-70hROnmkr-TTyrTbt54xFzaRn54jCOn8PSpS3fwLEJJA@mail.gmail.com>
	<CALtRa-5bPYfprBKH++cW8wN+q8e08WZ7eH5e6OGaD_eQ6-t_fA@mail.gmail.com>
	<DE8738C4-7BC7-4597-A1BF-BDB097FEECC6@opencsw.org>
	<CALtRa-6Vb0u34sE7NHX1Ca4mDBMY3kyt3CfnGWpQO37GV-d5-w@mail.gmail.com>
	<CALtRa-57epz9gHyfNVzAGELa-7Km_Jxab2cRAYu0mWm5sBdKQw@mail.gmail.com>
	<CALtRa-7VDgk7Rc7JRbbR_1bheHFe0hC6yoRW7up5ZOe0eZsVMQ@mail.gmail.com>
	<CALtRa-6cQ+t8vhq2NXNP4V3jPeig2Ds7LxQ+GX55gf2LqEEfUw@mail.gmail.com>
	<7875.1316005468@thecus.kiddle.eu>
	<CALtRa-5PcCZRFHX8y0su0nhhFg-fWB8_G+7-yjSk964evHw8Vg@mail.gmail.com>
	<x6boumgssd.fsf@opencsw.org>
Message-ID: <CALtRa-7PgdPWpVROapPn8vE8w0T8xg=RWKimWeZ6gTfHQ98BRw@mail.gmail.com>

  I2011/9/15 Peter FELECAN <pfelecan at opencsw.org>:
> "Maciej (Matchek) Blizi?ski" <maciej at opencsw.org> writes:
>
>> I'm not sure why is it trying to use /usr/ccs/bin/as. ?Do you have
>> /opt/csw/bin/gas in the filesystem? ?If not, then CSWgcc4core needs to
>> depend on CSWbinutils.
>
> It *must* depend on binutils as the previous i386 packages.

I've tried rerolling the package, but the libmpfr_dev installation
broke in the meantime, so I have to wait for the buildfarm admins to
reinstall it.

The problem is that the /opt/csw/lib/libmpfr.so symlink disappears,
and you can't link against libmpfr any more.  There is some suspicion
that it is a pkgadd vs zones problem.

Maciej

From maciej at opencsw.org  Sun Sep 18 11:38:59 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sun, 18 Sep 2011 10:38:59 +0100
Subject: [csw-maintainers] Implications of publishing packages to unstable
Message-ID: <CALtRa-4TtZHgQduKbS0TxzXxXAu_JTr67dFPkagEA811f6MGAQ@mail.gmail.com>

Dear maintainers,

I'd like to clarify the implications of publishing packages to unstable.

When you call the csw-upload-pkg tool, certain things happen, and it's
important that you understand what these things are.

1. The .pkg files are uploaded to allpkgs
http://mirror.opencsw.org/opencsw/allpkgs/
2. checkpkg is run against the packages; if the check fails, the procedure stops
3. The packages are added to the unstable catalog
http://mirror.opencsw.org/opencsw/unstable/ - unstable is an official,
signed catalog which gets pushed to mirrors all around the world, and
gets installed by users
4. Packages from unstable are installed on the buildfarm during
periodic manual sync

csw-upload-pkg tool should not be taken lightly.  You must not push
packages that you haven't at least smoke-tested.  If you push broken
packages, you cause grief on the buildfarm.  You can also cause grief
by pushing backward-incompatible packages that are part of the
infrastructure, e.g. any of the CSWgar-dev package dependencies.

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

If you have built packages that you would like to just try out,
unstable is not the right place for that purpose. Use the experimental
catalogs instead, by copying files into /home/experimental/$LOGNAME
and visiting http://buildfarm.opencsw.org/experimental.html

Maciej

From rupert at opencsw.org  Sun Sep 18 13:20:57 2011
From: rupert at opencsw.org (rupert THURNER)
Date: Sun, 18 Sep 2011 13:20:57 +0200
Subject: [csw-maintainers] Implications of publishing packages to
	unstable
In-Reply-To: <CALtRa-4TtZHgQduKbS0TxzXxXAu_JTr67dFPkagEA811f6MGAQ@mail.gmail.com>
References: <CALtRa-4TtZHgQduKbS0TxzXxXAu_JTr67dFPkagEA811f6MGAQ@mail.gmail.com>
Message-ID: <CAJs9aZ813V5JV+MYskjoFAZsN2g84n9JZ5VPum+bo3qhqknqOw@mail.gmail.com>

would it be possible to include an experimental stage to the automated
release process? i.e. have a machine where these packages are
automatically deployed and can be run at least once before promoting
them to unstable.

rupert.


2011/9/18 Maciej (Matchek) Blizi?ski <maciej at opencsw.org>:
> Dear maintainers,
>
> I'd like to clarify the implications of publishing packages to unstable.
>
> When you call the csw-upload-pkg tool, certain things happen, and it's
> important that you understand what these things are.
>
> 1. The .pkg files are uploaded to allpkgs
> http://mirror.opencsw.org/opencsw/allpkgs/
> 2. checkpkg is run against the packages; if the check fails, the procedure stops
> 3. The packages are added to the unstable catalog
> http://mirror.opencsw.org/opencsw/unstable/ - unstable is an official,
> signed catalog which gets pushed to mirrors all around the world, and
> gets installed by users
> 4. Packages from unstable are installed on the buildfarm during
> periodic manual sync
>
> csw-upload-pkg tool should not be taken lightly. ?You must not push
> packages that you haven't at least smoke-tested. ?If you push broken
> packages, you cause grief on the buildfarm. ?You can also cause grief
> by pushing backward-incompatible packages that are part of the
> infrastructure, e.g. any of the CSWgar-dev package dependencies.
>
> http://www.opencsw.org/packages/gar_dev/
>
> If you have built packages that you would like to just try out,
> unstable is not the right place for that purpose. Use the experimental
> catalogs instead, by copying files into /home/experimental/$LOGNAME
> and visiting http://buildfarm.opencsw.org/experimental.html
>
> Maciej
> _______________________________________________
> maintainers mailing list
> maintainers at lists.opencsw.org
> https://lists.opencsw.org/mailman/listinfo/maintainers
> .:: This mailing list's archive is public. ::.
>

From pfelecan at opencsw.org  Sun Sep 18 13:36:12 2011
From: pfelecan at opencsw.org (Peter FELECAN)
Date: Sun, 18 Sep 2011 13:36:12 +0200
Subject: [csw-maintainers] Implications of publishing packages to
	unstable
In-Reply-To: <CAJs9aZ813V5JV+MYskjoFAZsN2g84n9JZ5VPum+bo3qhqknqOw@mail.gmail.com>
	(rupert THURNER's message of "Sun, 18 Sep 2011 13:20:57 +0200")
References: <CALtRa-4TtZHgQduKbS0TxzXxXAu_JTr67dFPkagEA811f6MGAQ@mail.gmail.com>
	<CAJs9aZ813V5JV+MYskjoFAZsN2g84n9JZ5VPum+bo3qhqknqOw@mail.gmail.com>
Message-ID: <x6bouiaxqr.fsf@opencsw.org>

rupert THURNER <rupert at opencsw.org> writes:

> would it be possible to include an experimental stage to the automated
> release process? i.e. have a machine where these packages are
> automatically deployed and can be run at least once before promoting
> them to unstable.

+1 and we agree that the test is manual isn't it?
-- 
Peter

From maciej at opencsw.org  Sun Sep 18 15:06:56 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sun, 18 Sep 2011 14:06:56 +0100
Subject: [csw-maintainers] Implications of publishing packages to
	unstable
In-Reply-To: <CAJs9aZ813V5JV+MYskjoFAZsN2g84n9JZ5VPum+bo3qhqknqOw@mail.gmail.com>
References: <CALtRa-4TtZHgQduKbS0TxzXxXAu_JTr67dFPkagEA811f6MGAQ@mail.gmail.com>
	<CAJs9aZ813V5JV+MYskjoFAZsN2g84n9JZ5VPum+bo3qhqknqOw@mail.gmail.com>
Message-ID: <CALtRa-5yTz0EDoWa60hspa_-9mNmo1mfw8ZtFQYH9O70PL-hmA@mail.gmail.com>

2011/9/18 rupert THURNER <rupert at opencsw.org>:
> would it be possible to include an experimental stage to the automated
> release process? i.e. have a machine where these packages are
> automatically deployed and can be run at least once before promoting
> them to unstable.

Installing automatically from experimental isn't a great idea, because
you might want to watch the packages being installed - imagine you're
debugging a postinstall script. If that installation were automated,
it would be harder for you to get the diagnostic information.

We have the test{9,10}{s,x} hosts on which we can install things to
test.  You log in there, say sudo pkgutil -t ... -y -i foo and you're
set.

Maciej

From sgtmcd at gmail.com  Mon Sep 19 12:32:03 2011
From: sgtmcd at gmail.com (Shawn McDermott)
Date: Mon, 19 Sep 2011 05:32:03 -0500
Subject: [csw-maintainers] erlang package
Message-ID: <98B859EC-1CE8-4AD7-AE38-0FC6146D75C3@gmail.com>

Is Dominique Laigle still around?   

I recently got a maintainer account to start working on some packages.  One of the packages I depend on is erlang(probably devel too).  However, the version you have done is one step behind what I need.  you did 11,REV=2007.12.08_rev=R11B5.  

I need R12B5.  Is there a way I could talk you into doing that version?  If not, do I pull and update it myself?

Regards,
Shawn

From ihsan at opencsw.org  Mon Sep 19 13:25:38 2011
From: ihsan at opencsw.org (=?UTF-8?B?xLBoc2FuIERvxJ9hbg==?=)
Date: Mon, 19 Sep 2011 13:25:38 +0200
Subject: [csw-maintainers] erlang package
In-Reply-To: <98B859EC-1CE8-4AD7-AE38-0FC6146D75C3@gmail.com>
References: <98B859EC-1CE8-4AD7-AE38-0FC6146D75C3@gmail.com>
Message-ID: <4E7726B2.6000907@opencsw.org>

Hello Shawn,

On 09/19/11 12:32 PM, Shawn McDermott wrote:

> Is Dominique Laigle still around?

Unfortunately he is unreachable.

> I recently got a maintainer account to start working on some packages.  One of the packages I depend on is erlang(probably devel too).  However, the version you have done is one step behind what I need.  you did 11,REV=2007.12.08_rev=R11B5.
>
> I need R12B5.  Is there a way I could talk you into doing that version?  If not, do I pull and update it myself?

I would also need a newer version and I've started to work on it and 
I've started to work on it. I've commited my changes just now.

http://gar.svn.sourceforge.net/viewvc/gar?view=revision&revision=15651

If you have time and resources, you are free to work on it and to take 
it over.




Ihsan

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

From ihsan at opencsw.org  Mon Sep 19 13:31:01 2011
From: ihsan at opencsw.org (=?UTF-8?B?xLBoc2FuIERvxJ9hbg==?=)
Date: Mon, 19 Sep 2011 13:31:01 +0200
Subject: [csw-maintainers] Posting on the maintainers list
Message-ID: <4E7727F5.9070502@opencsw.org>

Dear OpenCSW maintainers,

Please use your @opencsw.org address to post on this list. If you post 
by accident with a different address, I would really appreciate it if 
you could delete your post through the Mailman web interface.

Thanks.




Ihsan

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

From skayser at opencsw.org  Mon Sep 19 13:46:24 2011
From: skayser at opencsw.org (Sebastian Kayser)
Date: Mon, 19 Sep 2011 13:46:24 +0200
Subject: [csw-maintainers] Posting on the maintainers list
In-Reply-To: <4E7727F5.9070502@opencsw.org>
References: <4E7727F5.9070502@opencsw.org>
Message-ID: <20110919114624.GR16203@sebastiankayser.de>

Ihsan,

* ??hsan Do??an <ihsan at opencsw.org> wrote:
> Please use your @opencsw.org address to post on this list. If you post 
> by accident with a different address, I would really appreciate it if 
> you could delete your post through the Mailman web interface.

if we stick to the csw-senders-only-policy on maintainers@, how about
simply bouncing mails from non-csw email addresses (and not keeping them
for moderation)? At least if MailMan supports this.

Currently, people who send with a wrong sender address receive the
warning, realize that they got their sender address wrong, and resend
the email with the proper sender address.

With bounces, the workflow would stay the same except that there's no
waiting-for-moderation queue that needs to be taken care of. Neither by
you nor the sender.

Sebastian

From wilbury at opencsw.org  Mon Sep 19 13:49:52 2011
From: wilbury at opencsw.org (Juraj Lutter)
Date: Mon, 19 Sep 2011 12:49:52 +0100
Subject: [csw-maintainers] Posting on the maintainers list
Message-ID: <978673aa52d1747d5623b0c6ca378941@wilbury.sk>

On 2011-09-19 12:46, Sebastian Kayser wrote:
> With bounces, the workflow would stay the same except that there's no
> waiting-for-moderation queue that needs to be taken care of. Neither 
> by
> you nor the sender.
>


Yes. It happened to me at least twice :-)
OBTW. You can leave messages in moderator queue, they will expire
automatically (provided that there is mailman cronjob set up.)

/otis

-- 
Juraj Lutter <wilbury at opencsw.org>

From bwalton at opencsw.org  Mon Sep 19 15:19:44 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Mon, 19 Sep 2011 09:19:44 -0400
Subject: [csw-maintainers] Posting on the maintainers list
In-Reply-To: <20110919114624.GR16203@sebastiankayser.de>
References: <4E7727F5.9070502@opencsw.org>
	<20110919114624.GR16203@sebastiankayser.de>
Message-ID: <1316438327-sup-2566@pinkfloyd.chass.utoronto.ca>

Excerpts from Sebastian Kayser's message of Mon Sep 19 07:46:24 -0400 2011:

> if we stick to the csw-senders-only-policy on maintainers@, how
> about simply bouncing mails from non-csw email addresses (and not
> keeping them for moderation)? At least if MailMan supports this.

+1 for changing 'moderate' to 'reject' as that would solve this
problem while still being visible to the user that sent the message.
(I'm good at sending from the wrong account at least once a month.)

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From dam at opencsw.org  Mon Sep 19 16:19:10 2011
From: dam at opencsw.org (Dagobert Michelsen)
Date: Mon, 19 Sep 2011 16:19:10 +0200
Subject: [csw-maintainers] erlang package
In-Reply-To: <4E7726B2.6000907@opencsw.org>
References: <98B859EC-1CE8-4AD7-AE38-0FC6146D75C3@gmail.com>
	<4E7726B2.6000907@opencsw.org>
Message-ID: <54F13748-AD54-4A36-90C3-D909621FF92E@opencsw.org>

Hi Shawn,

Am 19.09.2011 um 13:25 schrieb ?hsan Do?an:
> On 09/19/11 12:32 PM, Shawn McDermott wrote:
>> I recently got a maintainer account to start working on some packages.  One of the packages I depend on is erlang(probably devel too).  However, the version you have done is one step behind what I need.  you did 11,REV=2007.12.08_rev=R11B5.
>> 
>> I need R12B5.  Is there a way I could talk you into doing that version?  If not, do I pull and update it myself?
> 
> I would also need a newer version and I've started to work on it and I've started to work on it. I've commited my changes just now.
> 
> http://gar.svn.sourceforge.net/viewvc/gar?view=revision&revision=15651
> 
> If you have time and resources, you are free to work on it and to take it over.

I worked on it and committed what I have.


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


From sgtmcd at gmail.com  Mon Sep 19 16:39:04 2011
From: sgtmcd at gmail.com (Shawn McDermott)
Date: Mon, 19 Sep 2011 09:39:04 -0500
Subject: [csw-maintainers] erlang package
In-Reply-To: <54F13748-AD54-4A36-90C3-D909621FF92E@opencsw.org>
References: <98B859EC-1CE8-4AD7-AE38-0FC6146D75C3@gmail.com>
	<4E7726B2.6000907@opencsw.org>
	<54F13748-AD54-4A36-90C3-D909621FF92E@opencsw.org>
Message-ID: <A9D87740-A1A3-4174-9165-FFAD1408F7CB@opencsw.org>

Hi Dago,

I will be at the point I can work on this in a few hours.  Thanks for your efforts!

Shawn

On Sep 19, 2011, at 9:19 AM, Dagobert Michelsen wrote:

> Hi Shawn,
> 
> Am 19.09.2011 um 13:25 schrieb ?hsan Do?an:
>> On 09/19/11 12:32 PM, Shawn McDermott wrote:
>>> I recently got a maintainer account to start working on some packages.  One of the packages I depend on is erlang(probably devel too).  However, the version you have done is one step behind what I need.  you did 11,REV=2007.12.08_rev=R11B5.
>>> 
>>> I need R12B5.  Is there a way I could talk you into doing that version?  If not, do I pull and update it myself?
>> 
>> I would also need a newer version and I've started to work on it and I've started to work on it. I've commited my changes just now.
>> 
>> http://gar.svn.sourceforge.net/viewvc/gar?view=revision&revision=15651
>> 
>> If you have time and resources, you are free to work on it and to take it over.
> 
> I worked on it and committed what I have.
> 
> 
> 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
> 
> _______________________________________________
> maintainers mailing list
> maintainers at lists.opencsw.org
> https://lists.opencsw.org/mailman/listinfo/maintainers
> .:: This mailing list's archive is public. ::.


From skayser at opencsw.org  Mon Sep 19 23:34:43 2011
From: skayser at opencsw.org (Sebastian Kayser)
Date: Mon, 19 Sep 2011 23:34:43 +0200
Subject: [csw-maintainers] Status of svn on the buildfarm (working copy
	upgrade)?
Message-ID: <20110919213443.GV16203@sebastiankayser.de>

Hi,

what's the current status of svn on the buildfarm? I vaguely remember
some people having problem with the working copy upgrade with 1.7pre3.
Is it safe to upgrade by now? Or rather checkout a separate tree?

Sebastian

From maciej at opencsw.org  Mon Sep 19 23:37:37 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Mon, 19 Sep 2011 22:37:37 +0100
Subject: [csw-maintainers] Status of svn on the buildfarm (working copy
	upgrade)?
In-Reply-To: <20110919213443.GV16203@sebastiankayser.de>
References: <20110919213443.GV16203@sebastiankayser.de>
Message-ID: <CALtRa-45EG7_QZruCx=ufpt8FkT8WhfwmzmXZUdcg1k0N7MiwA@mail.gmail.com>

2011/9/19 Sebastian Kayser <skayser at opencsw.org>:
> what's the current status of svn on the buildfarm? I vaguely remember
> some people having problem with the working copy upgrade with 1.7pre3.
> Is it safe to upgrade by now? Or rather checkout a separate tree?

I keep using the half-upgraded tree and waiting for it to explode, but
the explosion didn't happen so far.

Maciej

From wilbury at opencsw.org  Mon Sep 19 23:41:29 2011
From: wilbury at opencsw.org (Juraj Lutter)
Date: Mon, 19 Sep 2011 23:41:29 +0200
Subject: [csw-maintainers] Status of svn on the buildfarm (working copy
 upgrade)?
In-Reply-To: <CALtRa-45EG7_QZruCx=ufpt8FkT8WhfwmzmXZUdcg1k0N7MiwA@mail.gmail.com>
References: <20110919213443.GV16203@sebastiankayser.de>
	<CALtRa-45EG7_QZruCx=ufpt8FkT8WhfwmzmXZUdcg1k0N7MiwA@mail.gmail.com>
Message-ID: <4E77B709.5090804@opencsw.org>

On 09/19/2011 11:37 PM, Maciej (Matchek) Blizi?ski wrote:
> 2011/9/19 Sebastian Kayser <skayser at opencsw.org>:
>> what's the current status of svn on the buildfarm? I vaguely remember
>> some people having problem with the working copy upgrade with 1.7pre3.
>> Is it safe to upgrade by now? Or rather checkout a separate tree?
> 
> I keep using the half-upgraded tree and waiting for it to explode, but
> the explosion didn't happen so far.

I did "svn upgrade" couple of days ago which seemed to went OK for me.

-- 
Juraj Lutter <wilbury at opencsw.org>

From skayser at opencsw.org  Tue Sep 20 00:15:56 2011
From: skayser at opencsw.org (Sebastian Kayser)
Date: Tue, 20 Sep 2011 00:15:56 +0200
Subject: [csw-maintainers] mgar 0.93-rc1 // Changes and call for testing
Message-ID: <20110919221556.GW16203@sebastiankayser.de>

Hi folks,

it's about time to package a new mgar version. Could you guys please
test drive 0.93-rc1. Available from SVN, from my $HOME on the buildfarm,
and from experimental [1,2,3].

Changes since 0.92 (r380):
* NEW command "show-var" to show runtime value of recipe vars (Maciej Blizinski)
* NEW command "grep-buildsys" to facilitate grepping the build system
* NEW command alias "-V" for "version"
* CHANGE added package version to "version" command output
* CHANGE "newpkg" command now runs relative to the build tree (not $PWD)
* CHANGE tweaked error message when running a pkg command in a non-pkg dir
* CHANGE added directions for reporting bugs to --help output
* FIX fail gracefully in case of VCS issues with pkg or build system dirs
* FIX mgar(1) remove reference to mgar(5) while incomplete (Peter Bonivart)

There's now also a bug tracker project for reporting bugs, ideas, and
RFEs (follow bug tracker link @ [4]). Feedback much appreciated!

Sebastian

[1] svn export https://opencsw.svn.sourceforge.net/svnroot/opencsw/gar-wrapper/mgar
[2] ~skayser/bin/mgar-rc
[3] pkgutil -t http://buildfarm.opencsw.org/opencsw/experimental/skayser -u mgar
[4] http://opencsw.org/packages/mgar

From skayser at opencsw.org  Tue Sep 20 00:25:13 2011
From: skayser at opencsw.org (Sebastian Kayser)
Date: Tue, 20 Sep 2011 00:25:13 +0200
Subject: [csw-maintainers] Status of svn on the buildfarm (working copy
	upgrade)?
In-Reply-To: <4E77B709.5090804@opencsw.org>
References: <20110919213443.GV16203@sebastiankayser.de>
	<CALtRa-45EG7_QZruCx=ufpt8FkT8WhfwmzmXZUdcg1k0N7MiwA@mail.gmail.com>
	<4E77B709.5090804@opencsw.org>
Message-ID: <20110919222513.GX16203@sebastiankayser.de>

* Juraj Lutter <wilbury at opencsw.org> wrote:
> On 09/19/2011 11:37 PM, Maciej (Matchek) Blizi?ski wrote:
> > 2011/9/19 Sebastian Kayser <skayser at opencsw.org>:
> >> what's the current status of svn on the buildfarm? I vaguely remember
> >> some people having problem with the working copy upgrade with 1.7pre3.
> >> Is it safe to upgrade by now? Or rather checkout a separate tree?
> > 
> > I keep using the half-upgraded tree and waiting for it to explode, but
> > the explosion didn't happen so far.
> 
> I did "svn upgrade" couple of days ago which seemed to went OK for me.

Thanks, will give it a try too then.

Sebastian

From bwalton at opencsw.org  Tue Sep 20 01:44:41 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Mon, 19 Sep 2011 19:44:41 -0400
Subject: [csw-maintainers] Status of svn on the buildfarm (working copy
	upgrade)?
In-Reply-To: <4E77B709.5090804@opencsw.org>
References: <20110919213443.GV16203@sebastiankayser.de>
	<CALtRa-45EG7_QZruCx=ufpt8FkT8WhfwmzmXZUdcg1k0N7MiwA@mail.gmail.com>
	<4E77B709.5090804@opencsw.org>
Message-ID: <1316475856-sup-2671@pinkfloyd.chass.utoronto.ca>

Excerpts from Juraj Lutter's message of Mon Sep 19 17:41:29 -0400 2011:
> On 09/19/2011 11:37 PM, Maciej (Matchek) Blizi?ski wrote:
> > 2011/9/19 Sebastian Kayser <skayser at opencsw.org>:
> >> what's the current status of svn on the buildfarm? I vaguely remember
> >> some people having problem with the working copy upgrade with 1.7pre3.
> >> Is it safe to upgrade by now? Or rather checkout a separate tree?
> > 
> > I keep using the half-upgraded tree and waiting for it to explode, but
> > the explosion didn't happen so far.
> 
> I did "svn upgrade" couple of days ago which seemed to went OK for me.

I too upgraded my tree a few days back and svn itself works fine.  The
git test suite fails with the new version though for reasons I haven't
tracked down yet.

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From bwalton at opencsw.org  Tue Sep 20 02:45:47 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Mon, 19 Sep 2011 20:45:47 -0400
Subject: [csw-maintainers] experimental rsync version
Message-ID: <1316479454-sup-9407@pinkfloyd.chass.utoronto.ca>


Hi All,

I've been working with the lead rsync developer to get extended
attribute support for Solaris working in rsync.  I have a test package
of the pending rsync 3.1.0 with a few additional patches that allow
the xattr support to work on Solaris 9 as well as 10.  I wouldn't mind
a bit of tire kicking (try --fake-super and inspect with runat) if you
have any possible need for this feature set.

http://buildfarm.opencsw.org/experimental.html#rsync

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From bonivart at opencsw.org  Tue Sep 20 09:17:00 2011
From: bonivart at opencsw.org (Peter Bonivart)
Date: Tue, 20 Sep 2011 09:17:00 +0200
Subject: [csw-maintainers] Status of svn on the buildfarm (working copy
	upgrade)?
In-Reply-To: <20110919213443.GV16203@sebastiankayser.de>
References: <20110919213443.GV16203@sebastiankayser.de>
Message-ID: <CABY0g1Vpk+7QEyXjoSV2Nk6peU6DkwNNLsV4RRzVPX53pqP_WA@mail.gmail.com>

On Mon, Sep 19, 2011 at 11:34 PM, Sebastian Kayser <skayser at opencsw.org> wrote:
> Hi,
>
> what's the current status of svn on the buildfarm? I vaguely remember
> some people having problem with the working copy upgrade with 1.7pre3.
> Is it safe to upgrade by now? Or rather checkout a separate tree?

With the pre-release (!) of 1.7 installed on the unstable build hosts
your local repo will not work without an upgrade or a new checkout.
Expect the upgrade to take an enormous amount of time, at least 12
hours. I don't remember the complete checkout taking more than about 3
hours so I would recommend that.

/peter

From skayser at opencsw.org  Tue Sep 20 10:18:13 2011
From: skayser at opencsw.org (Sebastian Kayser)
Date: Tue, 20 Sep 2011 10:18:13 +0200
Subject: [csw-maintainers] Status of svn on the buildfarm (working copy
	upgrade)?
In-Reply-To: <20110919222513.GX16203@sebastiankayser.de>
References: <20110919213443.GV16203@sebastiankayser.de>
	<CALtRa-45EG7_QZruCx=ufpt8FkT8WhfwmzmXZUdcg1k0N7MiwA@mail.gmail.com>
	<4E77B709.5090804@opencsw.org>
	<20110919222513.GX16203@sebastiankayser.de>
Message-ID: <20110920081813.GA30486@sebastiankayser.de>

* Sebastian Kayser <skayser at opencsw.org> wrote:
> * Juraj Lutter <wilbury at opencsw.org> wrote:
> > On 09/19/2011 11:37 PM, Maciej (Matchek) Blizi?ski wrote:
> > > 2011/9/19 Sebastian Kayser <skayser at opencsw.org>:
> > >> what's the current status of svn on the buildfarm? I vaguely remember
> > >> some people having problem with the working copy upgrade with 1.7pre3.
> > >> Is it safe to upgrade by now? Or rather checkout a separate tree?
> > > 
> > > I keep using the half-upgraded tree and waiting for it to explode, but
> > > the explosion didn't happen so far.
> > 
> > I did "svn upgrade" couple of days ago which seemed to went OK for me.
> 
> Thanks, will give it a try too then.

skayser @ unstable9s ~/mgar/pkg$ time svn upgrade
...
svn: E000013: Can't make directory
'/home/skayser/mgar/pkg/rrdtool/branches/ihsan/gar/.svn/tmp/wcng/.svn':
Permission denied

real    75m38.903s
user    38m37.960s
sys     28m37.153s

Anyone ran into this yet? What would be the best description for the
state of my working copy now? Partially upgrade? All good except for
rrdtool/branches/ihsan?

skayser @ unstable9s ~/mgar/pkg$ svn upgrade
svn: E155019: Can't upgrade '/home/skayser/mgar/pkg' as it is not a
pre-1.7 working copy directory
svn: E150000: Missing default entry

skayser @ unstable9s ~/mgar/pkg$ svn info .
Path: .
Working Copy Root Path: /home/skayser/mgar/pkg
URL: https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg
Repository Root: https://gar.svn.sf.net/svnroot/gar
Repository UUID: d3b55034-1cff-0310-a425-aefe953e1e90
Revision: 15009
Node Kind: directory
Schedule: normal
Last Changed Author: phipsy
Last Changed Rev: 15009
Last Changed Date: 2011-07-08 17:10:09 +0200 (Fri, 08 Jul 2011)

skayser @ unstable9s ~/mgar/pkg$ svn --version | head -1
svn, version 1.7.0-rc2 (Release Candidate 2)

Sebastian

From bonivart at opencsw.org  Tue Sep 20 13:51:53 2011
From: bonivart at opencsw.org (Peter Bonivart)
Date: Tue, 20 Sep 2011 13:51:53 +0200
Subject: [csw-maintainers] Status of svn on the buildfarm (working copy
	upgrade)?
In-Reply-To: <20110920081813.GA30486@sebastiankayser.de>
References: <20110919213443.GV16203@sebastiankayser.de>
	<CALtRa-45EG7_QZruCx=ufpt8FkT8WhfwmzmXZUdcg1k0N7MiwA@mail.gmail.com>
	<4E77B709.5090804@opencsw.org>
	<20110919222513.GX16203@sebastiankayser.de>
	<20110920081813.GA30486@sebastiankayser.de>
Message-ID: <CABY0g1VrA4vdUpmn0wmMGbE0zzRODaGsf_Rjm18RUYh6751EOA@mail.gmail.com>

On Tue, Sep 20, 2011 at 10:18 AM, Sebastian Kayser <skayser at opencsw.org> wrote:
> skayser @ unstable9s ~/mgar/pkg$ time svn upgrade
> ...
> svn: E000013: Can't make directory
> '/home/skayser/mgar/pkg/rrdtool/branches/ihsan/gar/.svn/tmp/wcng/.svn':
> Permission denied
>
> real ? ?75m38.903s
> user ? ?38m37.960s
> sys ? ? 28m37.153s
>
> Anyone ran into this yet? What would be the best description for the
> state of my working copy now? Partially upgrade? All good except for
> rrdtool/branches/ihsan?
>
> skayser @ unstable9s ~/mgar/pkg$ svn upgrade
> svn: E155019: Can't upgrade '/home/skayser/mgar/pkg' as it is not a
> pre-1.7 working copy directory
> svn: E150000: Missing default entry

I think this just means that you're now on 1.7 so you can't upgrade
(you're already upgraded). Try "svn up" to do a normal update (not
upgrade) of the repo.

75 minutes sounds quick, my upgrade took at least 12 hours.

/peter

From skayser at opencsw.org  Tue Sep 20 14:10:13 2011
From: skayser at opencsw.org (Sebastian Kayser)
Date: Tue, 20 Sep 2011 14:10:13 +0200
Subject: [csw-maintainers] Status of svn on the buildfarm (working copy
	upgrade)?
In-Reply-To: <CABY0g1VrA4vdUpmn0wmMGbE0zzRODaGsf_Rjm18RUYh6751EOA@mail.gmail.com>
References: <20110919213443.GV16203@sebastiankayser.de>
	<CALtRa-45EG7_QZruCx=ufpt8FkT8WhfwmzmXZUdcg1k0N7MiwA@mail.gmail.com>
	<4E77B709.5090804@opencsw.org>
	<20110919222513.GX16203@sebastiankayser.de>
	<20110920081813.GA30486@sebastiankayser.de>
	<CABY0g1VrA4vdUpmn0wmMGbE0zzRODaGsf_Rjm18RUYh6751EOA@mail.gmail.com>
Message-ID: <20110920121013.GC30486@sebastiankayser.de>

* Peter Bonivart <bonivart at opencsw.org> wrote:
> On Tue, Sep 20, 2011 at 10:18 AM, Sebastian Kayser <skayser at opencsw.org> wrote:
> > skayser @ unstable9s ~/mgar/pkg$ time svn upgrade
> > ...
> > svn: E000013: Can't make directory
> > '/home/skayser/mgar/pkg/rrdtool/branches/ihsan/gar/.svn/tmp/wcng/.svn':
> > Permission denied
> >
> > real ? ?75m38.903s
> > user ? ?38m37.960s
> > sys ? ? 28m37.153s
> >
> > Anyone ran into this yet? What would be the best description for the
> > state of my working copy now? Partially upgrade? All good except for
> > rrdtool/branches/ihsan?
> >
> > skayser @ unstable9s ~/mgar/pkg$ svn upgrade
> > svn: E155019: Can't upgrade '/home/skayser/mgar/pkg' as it is not a
> > pre-1.7 working copy directory
> > svn: E150000: Missing default entry
> 
> I think this just means that you're now on 1.7 so you can't upgrade
> (you're already upgraded). Try "svn up" to do a normal update (not
> upgrade) of the repo.

Thanks for the advice. svn up finished in about a minute, updated a
couple dozen of files, and didn't complain at all. Subsequent update
attempts didn't complain either. Looks good for now.

Sebastian

From skayser at opencsw.org  Tue Sep 20 14:25:32 2011
From: skayser at opencsw.org (Sebastian Kayser)
Date: Tue, 20 Sep 2011 14:25:32 +0200
Subject: [csw-maintainers] Status of svn on the buildfarm (working copy
	upgrade)?
In-Reply-To: <CABY0g1VrA4vdUpmn0wmMGbE0zzRODaGsf_Rjm18RUYh6751EOA@mail.gmail.com>
References: <20110919213443.GV16203@sebastiankayser.de>
	<CALtRa-45EG7_QZruCx=ufpt8FkT8WhfwmzmXZUdcg1k0N7MiwA@mail.gmail.com>
	<4E77B709.5090804@opencsw.org>
	<20110919222513.GX16203@sebastiankayser.de>
	<20110920081813.GA30486@sebastiankayser.de>
	<CABY0g1VrA4vdUpmn0wmMGbE0zzRODaGsf_Rjm18RUYh6751EOA@mail.gmail.com>
Message-ID: <20110920122532.GD30486@sebastiankayser.de>

* Peter Bonivart <bonivart at opencsw.org> wrote:
> On Tue, Sep 20, 2011 at 10:18 AM, Sebastian Kayser <skayser at opencsw.org> wrote:
> > skayser @ unstable9s ~/mgar/pkg$ time svn upgrade
> > ...
> > real ? ?75m38.903s
> > user ? ?38m37.960s
> > sys ? ? 28m37.153s
> 
> 75 minutes sounds quick, my upgrade took at least 12 hours.

Documenting for the sake of completeness. One speed factor could be IO
performance on our $HOME. $HOME on the *s boxes is lofs mounted, $HOME
on the *x boxes is remotely mounted via NFS. Quoting Dago:

14:16 <@Dagobert> skayser: *s is all on the sparc server, the homes are lofs
14:16 <@Dagobert> on *x it is NFS mounted and sloooow

My 75 minute upgrade attempt above was on one of the *s boxes.

Sebastian

From bonivart at opencsw.org  Tue Sep 20 16:00:22 2011
From: bonivart at opencsw.org (Peter Bonivart)
Date: Tue, 20 Sep 2011 16:00:22 +0200
Subject: [csw-maintainers] Status of svn on the buildfarm (working copy
	upgrade)?
In-Reply-To: <20110920122532.GD30486@sebastiankayser.de>
References: <20110919213443.GV16203@sebastiankayser.de>
	<CALtRa-45EG7_QZruCx=ufpt8FkT8WhfwmzmXZUdcg1k0N7MiwA@mail.gmail.com>
	<4E77B709.5090804@opencsw.org>
	<20110919222513.GX16203@sebastiankayser.de>
	<20110920081813.GA30486@sebastiankayser.de>
	<CABY0g1VrA4vdUpmn0wmMGbE0zzRODaGsf_Rjm18RUYh6751EOA@mail.gmail.com>
	<20110920122532.GD30486@sebastiankayser.de>
Message-ID: <CABY0g1XVNHw0sg+-5pd514EM27WBeRUR3vCDz8FJN94c93SACw@mail.gmail.com>

On Tue, Sep 20, 2011 at 2:25 PM, Sebastian Kayser <skayser at opencsw.org> wrote:
> * Peter Bonivart <bonivart at opencsw.org> wrote:
>> On Tue, Sep 20, 2011 at 10:18 AM, Sebastian Kayser <skayser at opencsw.org> wrote:
>> > skayser @ unstable9s ~/mgar/pkg$ time svn upgrade
>> > ...
>> > real ? ?75m38.903s
>> > user ? ?38m37.960s
>> > sys ? ? 28m37.153s
>>
>> 75 minutes sounds quick, my upgrade took at least 12 hours.
>
> Documenting for the sake of completeness. One speed factor could be IO
> performance on our $HOME. $HOME on the *s boxes is lofs mounted, $HOME
> on the *x boxes is remotely mounted via NFS. Quoting Dago:
>
> 14:16 <@Dagobert> skayser: *s is all on the sparc server, the homes are lofs
> 14:16 <@Dagobert> on *x it is NFS mounted and sloooow
>
> My 75 minute upgrade attempt above was on one of the *s boxes.

And so others know I of course chose i386 since that builds faster. :)

/peter

From pfelecan at opencsw.org  Tue Sep 20 16:01:18 2011
From: pfelecan at opencsw.org (Peter FELECAN)
Date: Tue, 20 Sep 2011 16:01:18 +0200
Subject: [csw-maintainers] Status of svn on the buildfarm (working copy
	upgrade)?
In-Reply-To: <CABY0g1Vpk+7QEyXjoSV2Nk6peU6DkwNNLsV4RRzVPX53pqP_WA@mail.gmail.com>
	(Peter Bonivart's message of "Tue, 20 Sep 2011 09:17:00 +0200")
References: <20110919213443.GV16203@sebastiankayser.de>
	<CABY0g1Vpk+7QEyXjoSV2Nk6peU6DkwNNLsV4RRzVPX53pqP_WA@mail.gmail.com>
Message-ID: <x6fwjr5n4h.fsf@opencsw.org>

Peter Bonivart <bonivart at opencsw.org> writes:

> On Mon, Sep 19, 2011 at 11:34 PM, Sebastian Kayser <skayser at opencsw.org> wrote:
>> Hi,
>>
>> what's the current status of svn on the buildfarm? I vaguely remember
>> some people having problem with the working copy upgrade with 1.7pre3.
>> Is it safe to upgrade by now? Or rather checkout a separate tree?
>
> With the pre-release (!) of 1.7 installed on the unstable build hosts
> your local repo will not work without an upgrade or a new checkout.
> Expect the upgrade to take an enormous amount of time, at least 12
> hours. I don't remember the complete checkout taking more than about 3
> hours so I would recommend that.

I have an issue with this (IMHO its not a svn problem): why is mgar so
huge? Each time I wish to approach gar based packaging I must incur
something as 16 hours of checkout/upgrade/what ever. It's so long that I
always forget what I wanted to do and I lose my motivation. Is not
possible to have a better granularity? Last time I looked there were a
lot of redundancy. Well, sorry if I misunderstood the subject.
-- 
Peter

From bonivart at opencsw.org  Tue Sep 20 16:12:38 2011
From: bonivart at opencsw.org (Peter Bonivart)
Date: Tue, 20 Sep 2011 16:12:38 +0200
Subject: [csw-maintainers] Status of svn on the buildfarm (working copy
	upgrade)?
In-Reply-To: <x6fwjr5n4h.fsf@opencsw.org>
References: <20110919213443.GV16203@sebastiankayser.de>
	<CABY0g1Vpk+7QEyXjoSV2Nk6peU6DkwNNLsV4RRzVPX53pqP_WA@mail.gmail.com>
	<x6fwjr5n4h.fsf@opencsw.org>
Message-ID: <CABY0g1WnWRCKAwx8o5Q1d0obROWa1Xryd3Hf3GzFG9XaKuV_tQ@mail.gmail.com>

On Tue, Sep 20, 2011 at 4:01 PM, Peter FELECAN <pfelecan at opencsw.org> wrote:
> I have an issue with this (IMHO its not a svn problem): why is mgar so
> huge? Each time I wish to approach gar based packaging I must incur
> something as 16 hours of checkout/upgrade/what ever. It's so long that I
> always forget what I wanted to do and I lose my motivation. Is not
> possible to have a better granularity? Last time I looked there were a
> lot of redundancy. Well, sorry if I misunderstood the subject.

This upgrade problem was caused by svn 1.7 requiring it and for some
reason a pre-release package of svn was uploaded to unstable and the
build hosts were upgraded with it. All local repos then had to be
upgraded to the new 1.7 format.

The time to do the upgrade is reasonable if you're on a Sparc host
which I unfortunately wasn't.

I think you're referring to us having the gar build system in every
package trunk which made svn ops much slower. Now with mgar we have
the build system just once and all trunks use that so svn is snappier
when not having to handle that.

Sure, a complete checkout takes a few hours but after that you can
work in your own areas of the repo. I rarely update the root of the
repo and even though people have worked on all kinds of things it's
only like 10 minutes.

/peter

From pfelecan at opencsw.org  Tue Sep 20 16:25:32 2011
From: pfelecan at opencsw.org (Peter FELECAN)
Date: Tue, 20 Sep 2011 16:25:32 +0200
Subject: [csw-maintainers] Status of svn on the buildfarm (working copy
	upgrade)?
In-Reply-To: <CABY0g1WnWRCKAwx8o5Q1d0obROWa1Xryd3Hf3GzFG9XaKuV_tQ@mail.gmail.com>
	(Peter Bonivart's message of "Tue, 20 Sep 2011 16:12:38 +0200")
References: <20110919213443.GV16203@sebastiankayser.de>
	<CABY0g1Vpk+7QEyXjoSV2Nk6peU6DkwNNLsV4RRzVPX53pqP_WA@mail.gmail.com>
	<x6fwjr5n4h.fsf@opencsw.org>
	<CABY0g1WnWRCKAwx8o5Q1d0obROWa1Xryd3Hf3GzFG9XaKuV_tQ@mail.gmail.com>
Message-ID: <x6bouf5m03.fsf@opencsw.org>

Peter Bonivart <bonivart at opencsw.org> writes:

> On Tue, Sep 20, 2011 at 4:01 PM, Peter FELECAN <pfelecan at opencsw.org> wrote:
>> I have an issue with this (IMHO its not a svn problem): why is mgar so
>> huge? Each time I wish to approach gar based packaging I must incur
>> something as 16 hours of checkout/upgrade/what ever. It's so long that I
>> always forget what I wanted to do and I lose my motivation. Is not
>> possible to have a better granularity? Last time I looked there were a
>> lot of redundancy. Well, sorry if I misunderstood the subject.
>
> This upgrade problem was caused by svn 1.7 requiring it and for some
> reason a pre-release package of svn was uploaded to unstable and the
> build hosts were upgraded with it. All local repos then had to be
> upgraded to the new 1.7 format.
>
> The time to do the upgrade is reasonable if you're on a Sparc host
> which I unfortunately wasn't.
>
> I think you're referring to us having the gar build system in every
> package trunk which made svn ops much slower. Now with mgar we have
> the build system just once and all trunks use that so svn is snappier
> when not having to handle that.
>
> Sure, a complete checkout takes a few hours but after that you can
> work in your own areas of the repo. I rarely update the root of the
> repo and even though people have worked on all kinds of things it's
> only like 10 minutes.

Thank you for your answer. Next time that I have the opportunity I will
give it a new try.
-- 
Peter

From bonivart at opencsw.org  Tue Sep 20 16:36:46 2011
From: bonivart at opencsw.org (Peter Bonivart)
Date: Tue, 20 Sep 2011 16:36:46 +0200
Subject: [csw-maintainers] Status of svn on the buildfarm (working copy
	upgrade)?
In-Reply-To: <x6bouf5m03.fsf@opencsw.org>
References: <20110919213443.GV16203@sebastiankayser.de>
	<CABY0g1Vpk+7QEyXjoSV2Nk6peU6DkwNNLsV4RRzVPX53pqP_WA@mail.gmail.com>
	<x6fwjr5n4h.fsf@opencsw.org>
	<CABY0g1WnWRCKAwx8o5Q1d0obROWa1Xryd3Hf3GzFG9XaKuV_tQ@mail.gmail.com>
	<x6bouf5m03.fsf@opencsw.org>
Message-ID: <CABY0g1U32P=UXER6f6vMQtjuh9ix0Do_K5NzSb-Uv=WD0uC7LQ@mail.gmail.com>

On Tue, Sep 20, 2011 at 4:25 PM, Peter FELECAN <pfelecan at opencsw.org> wrote:
> Thank you for your answer. Next time that I have the opportunity I will
> give it a new try.

Please do. Here's a guide to get started with mgar:

http://wiki.opencsw.org/gar-wrapper

/peter

From rupert at opencsw.org  Tue Sep 20 20:54:33 2011
From: rupert at opencsw.org (rupert THURNER)
Date: Tue, 20 Sep 2011 20:54:33 +0200
Subject: [csw-maintainers] svn-1.7-rc2, working copy upgrade fails,
	no restart possible
In-Reply-To: <CAJs9aZ-hZ1ks_P_oNtMWyB9Kex4X0KbhAiySwASCEZ8Y2i4wUA@mail.gmail.com>
References: <ffa91bea-9c8b-4090-93ee-8b0386791889@n40g2000yqb.googlegroups.com>
	<87fwjrr11g.fsf@stat.home.lan>
	<CAJs9aZ-td_dEPpE0kSdonEBDTFVVNf4SREjSt+_WMUj413gsug@mail.gmail.com>
	<87mxdz17aj.fsf@stat.home.lan>
	<CAJs9aZ-hZ1ks_P_oNtMWyB9Kex4X0KbhAiySwASCEZ8Y2i4wUA@mail.gmail.com>
Message-ID: <CAJs9aZ-tw1LoNhX3zW8T8GyexE8kmconUXW7H3YDJo5Zy5+5NQ@mail.gmail.com>

On Sep 20, 2011 8:50 PM, "rupert THURNER" <rupert.thurner at gmail.com> wrote:
> does anybody have a good description how to trigger the upgrade bug some
of
> you faced with rc2?
> On Sep 20, 2011 6:56 PM, "Philip Martin" <philip.martin at wandisco.com>
wrote:
>> rupert THURNER <rupert.thurner at gmail.com> writes:
>>
>>> yes, as multiple users at opencsw got this error using rc2 I wondered if
>>> there is already a fix for this.
>>
>> Is it the same bug? We think it is fixed in rc2. Are you saying the
>> fix doesn't work? Can you describe how to reproduce the bug?
>>
>> This works using rc2:
>>
>> rm -rf repo wc
>> svnadmin create repo
>> svn import -mm repo/format file://`pwd`/repo/f
>> svn1.6 co file://`pwd`/repo wc
>> svn1.6 lock wc/f
>> svn upgrade wc
>>
>> --
>> Philip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20110920/674c2975/attachment.html>

From skayser at opencsw.org  Wed Sep 21 10:49:45 2011
From: skayser at opencsw.org (Sebastian Kayser)
Date: Wed, 21 Sep 2011 10:49:45 +0200
Subject: [csw-maintainers] mgar 0.93-rc1 // Changes and call for testing
In-Reply-To: <20110919221556.GW16203@sebastiankayser.de>
References: <20110919221556.GW16203@sebastiankayser.de>
Message-ID: <20110921084945.GF30486@sebastiankayser.de>

* Sebastian Kayser <skayser at opencsw.org> wrote:
> it's about time to package a new mgar version. Could you guys please
> test drive 0.93-rc1. Available from SVN, from my $HOME on the buildfarm,
> and from experimental [1,2,3].

I just got feedback from Peter Bonivart about a glorious
(non-data-threatening) bug. Will fix this and report back once this is
done. Please hold your horses in the meantime. Thanks.

Sebastian

From skayser at opencsw.org  Wed Sep 21 14:50:38 2011
From: skayser at opencsw.org (Sebastian Kayser)
Date: Wed, 21 Sep 2011 14:50:38 +0200
Subject: [csw-maintainers] mgar 0.93-rc1 // Changes and call for testing
In-Reply-To: <20110921084945.GF30486@sebastiankayser.de>
References: <20110919221556.GW16203@sebastiankayser.de>
	<20110921084945.GF30486@sebastiankayser.de>
Message-ID: <20110921125038.GH30486@sebastiankayser.de>

* Sebastian Kayser <skayser at opencsw.org> wrote:
> * Sebastian Kayser <skayser at opencsw.org> wrote:
> > it's about time to package a new mgar version. Could you guys please
> > test drive 0.93-rc1. Available from SVN, from my $HOME on the buildfarm,
> > and from experimental [1,2,3].
> 
> I just got feedback from Peter Bonivart about a glorious
> (non-data-threatening) bug. Will fix this and report back once this is
> done. Please hold your horses in the meantime. Thanks.

Bug fixed with r542. Further testing and feedback welcome. If you are on
the buildfarm, just do

  alias mgar=~skayser/bin/mgar-rc

and continue your usual work.

Sebastian

--
skayser @ unstable9s ~/mgar/pkg/mgar/trunk$ mgar -V
0.93-rc2 (r542)

From skayser at opencsw.org  Wed Sep 21 23:49:50 2011
From: skayser at opencsw.org (Sebastian Kayser)
Date: Wed, 21 Sep 2011 23:49:50 +0200
Subject: [csw-maintainers] svn-1.7-rc2, working copy upgrade fails,
	no restart possible
In-Reply-To: <CAJs9aZ-tw1LoNhX3zW8T8GyexE8kmconUXW7H3YDJo5Zy5+5NQ@mail.gmail.com>
References: <ffa91bea-9c8b-4090-93ee-8b0386791889@n40g2000yqb.googlegroups.com>
	<87fwjrr11g.fsf@stat.home.lan>
	<CAJs9aZ-td_dEPpE0kSdonEBDTFVVNf4SREjSt+_WMUj413gsug@mail.gmail.com>
	<87mxdz17aj.fsf@stat.home.lan>
	<CAJs9aZ-hZ1ks_P_oNtMWyB9Kex4X0KbhAiySwASCEZ8Y2i4wUA@mail.gmail.com>
	<CAJs9aZ-tw1LoNhX3zW8T8GyexE8kmconUXW7H3YDJo5Zy5+5NQ@mail.gmail.com>
Message-ID: <20110921214950.GJ30486@sebastiankayser.de>

* rupert THURNER <rupert at opencsw.org> wrote:
>    On Sep 20, 2011 8:50 PM, "rupert THURNER" <[1]rupert.thurner at gmail.com>
>    wrote:
>    > does anybody have a good description how to trigger the upgrade bug some
>    of
>    > you faced with rc2?

No idea whether it's reproducable, but in my case that's what happened:
take a build recipe tree that's been checked out with a previous svn
version (most likely 1.6x as my copy stemmed from a not too distant
"mgar init") and run "svn upgrade" from the repository root.

Thinking back I was wondering whether the affected rrdtool branch
directory was also the one where we sporadically had errors during
checkouts in the past (until we fixed it with delete and re-commit), but
looking at the commit logs that doesn't seem to be the case.

Do others remember which directory was affected in their case?

Sebastian

From skayser at opencsw.org  Thu Sep 22 14:27:23 2011
From: skayser at opencsw.org (Sebastian Kayser)
Date: Thu, 22 Sep 2011 14:27:23 +0200
Subject: [csw-maintainers] GAR: EXPANDVARS for autoconf-style expansion in
	DISTFILES
Message-ID: <20110922122723.GN30486@sebastiankayser.de>

Hi folks,

Dago just mentioned a nifty autoconf-style expansion feature in GAR that
at least I wasn't aware of. Now documented in the variable reference
[1]. Usage example would e.g. be the openldap build [2].

EXPANDVARS
    List of files from $(DISTFILES) which should receive autoconf-style
    variable expansion. Such variables are then substituted with
    Makefile variable values (i.e. @NAME@ would be exanded to the value
    of $(NAME)). You can use this to easily adjust custom-shipped init
    scripts or other files which depend on paths in your Makefile (e.g.
    $(sysconfdir)). 

Sebastian

[1] https://sourceforge.net/apps/trac/gar/wiki/GAR%20Variable%20Reference
[2] https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/openldap/trunk/Makefile

From maciej at opencsw.org  Thu Sep 22 16:16:49 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Thu, 22 Sep 2011 15:16:49 +0100
Subject: [csw-maintainers] Videoconferencing during the Summercamp
Message-ID: <CALtRa-4uYSdpS7O+O75y27zrfviKq_LUEuSsntSS-VdxtNAytg@mail.gmail.com>

Hello everyone,

An idea - we could set up some conferencing during the summercamp? I
thought that we could try out the Google+ hangouts for this purpose.
They are easy to set up and can handle a number of VC endpoints.
Also, it can be done in parallel with streaming via ustream.

Are there people interested in videoconferencing - not coming
physically, but interested in participating in the conversation?

Maciej

From ihsan at opencsw.org  Sun Sep 25 00:34:17 2011
From: ihsan at opencsw.org (=?UTF-8?B?xLBoc2FuwqBEb8SfYW4=?=)
Date: Sun, 25 Sep 2011 00:34:17 +0200
Subject: [csw-maintainers] Posting on the maintainers list
In-Reply-To: <1316438327-sup-2566@pinkfloyd.chass.utoronto.ca>
References: <4E7727F5.9070502@opencsw.org>
	<20110919114624.GR16203@sebastiankayser.de>
	<1316438327-sup-2566@pinkfloyd.chass.utoronto.ca>
Message-ID: <4E7E5AE9.304@opencsw.org>

Am 19.09.2011 15:19, schrieb Ben Walton:

>> if we stick to the csw-senders-only-policy on maintainers@, how
>> about simply bouncing mails from non-csw email addresses (and not
>> keeping them for moderation)? At least if MailMan supports this.
> 
> +1 for changing 'moderate' to 'reject' as that would solve this
> problem while still being visible to the user that sent the message.
> (I'm good at sending from the wrong account at least once a month.)

Okay, I'm going to change the policy.



Ihsan

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

From bwalton at opencsw.org  Sun Sep 25 15:21:59 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Sun, 25 Sep 2011 09:21:59 -0400
Subject: [csw-maintainers] status on web/mantis integration
Message-ID: <1316956704-sup-5312@pinkfloyd.chass.utoronto.ca>


Hi All,

Ihsan has made some zone modifications to the web servers this
weekend, so I can now put some pieces in place and proceed toward the
automated integration of catalog changes with the web view and mantis.

Since the last update, there has been a change in direction.  The code
I've written to this point will drive only the mantis changes.  We're
going to talk to the checkpkg db on the buildfarm via rest from the
web pages to obtain always accurate information about catalogs,
packages, etc.

This coming week will be a busy one for me with less evening hacking
than I'd like, but I'm still hopeful that I can get the mantis piece
in place shortly.

My next steps will be to get the environment setup on the devel web
zone and then code the actual db modifications that happen as a result
of catalog changes.

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From dam at opencsw.org  Sun Sep 25 22:05:11 2011
From: dam at opencsw.org (Dagobert Michelsen)
Date: Sun, 25 Sep 2011 22:05:11 +0200
Subject: [csw-maintainers] Pictures of Oslo gone?
Message-ID: <CEC003C7-3580-4DD9-BE32-263F0266150C@opencsw.org>

Hi folks,

there used to be the pictures of Oslo in here:
  http://www.opencsw.org/2009/08/technical-summercamp-oslo-2009/
Is this related to the PHP update?


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


From maciej at opencsw.org  Mon Sep 26 09:28:09 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Mon, 26 Sep 2011 08:28:09 +0100
Subject: [csw-maintainers] GCC 4.6 progress
In-Reply-To: <x6aabak74x.fsf@opencsw.org>
References: <CALtRa-6Ho-vowyruOnhysuY4njq5CE98Hr3_WgyHDBUM2tKPEg@mail.gmail.com>
	<CALtRa-7i5B1APocaBRRLe8C-BMGwpzRJEHMSVP=_voOUmHqmsw@mail.gmail.com>
	<CALtRa-6K7FFdhKHfm1eK-vcz9xY=ek-g_9UYQ93UoNd05YXvQQ@mail.gmail.com>
	<CALtRa-7kNA7wUhjJLwgsid7+W4Kx1esXuyag=9yibdyvCayPBg@mail.gmail.com>
	<CALtRa-7xzHQBv6ZHM=iwXONDLGJeWebGjdS9dTbNZYCZ-c_KEA@mail.gmail.com>
	<x6aabak74x.fsf@opencsw.org>
Message-ID: <CALtRa-4FeOKF_XFNjU8nFVW-36U9biaY=hXSzc36Yo6eEC97Sw@mail.gmail.com>

2011/8/15 Peter FELECAN <pfelecan at opencsw.org>:
> Are you trying to build with Sun's C compiler? (I never succeeded to build
> gcc with that compiler) In the affirmative you'll have a heavy time
> generating the Ada compiler.

This time has just begun!

The story goes like this: I got PPL and Cloog in place and tried
compiling adding Ada to the list of language frontends.  The GCC build
system complained that GNAT is missing.  I thought I would build a
separate package with GNAT, but it turns out that it's built by GCC as
part of Ada, so there is a circular dependency: you need Ada to build
Ada.

I tried to install gcc3ada and use GNAT (gnatmake and gnatlink) from
/opt/csw/gcc3/bin, but it failed:

/opt/csw/gcc3/bin/gcc -c -g -fkeep-inline-functions  -gnatpg -gnata
-gnatwns -nostdinc -I- -I. -Iada
-I/home/maciej/src/opencsw/pkg/gcc4/trunk/work/build-isa-sparcv8/gcc-4.6.1/gcc/ada
-I/home/maciej/src/opencsw/pkg/gcc4/trunk/work/build-isa-sparcv8/gcc-4.6.1/gcc/ada/gcc-interface
/home/maciej/src/opencsw/pkg/gcc4/trunk/work/build-isa-sparcv8/gcc-4.6.1/gcc/ada/butil.adb
-o ada/butil.o
gcc: error: xsnamest.adb: Ada compiler not installed on this system
gnatmake: "xsnamest.adb" compilation error
/bin/bash: ./xsnamest: No such file or directory
gmake[3]: *** [ada/stamp-snames] Error 127
gmake[3]: *** Waiting for unfinished jobs....
gmake[3]: Leaving directory
`/home/maciej/src/opencsw/pkg/gcc4/trunk/work/build-isa-sparcv8/objdir/gcc'

Not sure why it happens, since gcc3 seems to have been built with Ada support.

Looking for a way to break the dependency cycle, I found place that
ships source code for something called "GNAT GPL":

http://libre.adacore.com/libre/download/

I went on to read the README.BUILD file:

"""
--------------------------------------
-- BUILDING GNAT - GENERAL COMMENTS --
--------------------------------------

GNAT being mainly written in Ada, you need GNAT to compile it. So, the
procedures described here presume that you have GCC and the current or the
previous version of GNAT installed -- i.e. the "gcc" command will run GNAT.
"""

So, no cookie.

At this point, it would make the most sense to find out why "Ada
compiler not installed on this system", while gcc3ada is in fact
there.

Any help and/or advice would be appreciated.

Maciej

From maciej at opencsw.org  Mon Sep 26 09:41:43 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Mon, 26 Sep 2011 08:41:43 +0100
Subject: [csw-maintainers] Pictures of Oslo gone?
In-Reply-To: <CEC003C7-3580-4DD9-BE32-263F0266150C@opencsw.org>
References: <CEC003C7-3580-4DD9-BE32-263F0266150C@opencsw.org>
Message-ID: <CALtRa-4P9WMRSCddJrPnvL=PNYpyUDAj484+zzXbd+r18bgGZw@mail.gmail.com>

2011/9/25 Dagobert Michelsen <dam at opencsw.org>:
> there used to be the pictures of Oslo in here:
> ?http://www.opencsw.org/2009/08/technical-summercamp-oslo-2009/
> Is this related to the PHP update?

I still see them there.

From maciej at opencsw.org  Mon Sep 26 11:31:45 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Mon, 26 Sep 2011 10:31:45 +0100
Subject: [csw-maintainers] Information about the OS release inside the
	package
Message-ID: <CALtRa-4FpUhuZ+s5uMRoE4s1sS8=0qgA6WcCO18pUSP6cHYsmg@mail.gmail.com>

Inside a SVR4 package (that is, in things you can read from the
inode), is there any indication as to which OS release has this
package been built for?  There's practically nothing about it in
PKGINFO, except for maybe PSTAMP - if it contains the build host name,
named e.g. "unstable9s", you could infer that it's a package for
SunOS5.9.  Is there anything else that can reliably detect the OS
release?

Maciej

From maciej at opencsw.org  Mon Sep 26 12:21:02 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Mon, 26 Sep 2011 11:21:02 +0100
Subject: [csw-maintainers] status on web/mantis integration
In-Reply-To: <1316956704-sup-5312@pinkfloyd.chass.utoronto.ca>
References: <1316956704-sup-5312@pinkfloyd.chass.utoronto.ca>
Message-ID: <CALtRa-5N6jMFY7vLEzX5TvvhwigoeHuuS1L8vKi3jSfRtALBKw@mail.gmail.com>

2011/9/25 Ben Walton <bwalton at opencsw.org>:
> Since the last update, there has been a change in direction. ?The code
> I've written to this point will drive only the mantis changes. ?We're
> going to talk to the checkpkg db on the buildfarm via rest from the
> web pages to obtain always accurate information about catalogs,
> packages, etc.

Cool.  I still have the REST interface update on my place, but I want
to get the baseline architecture change out the door first.

Maciej

From Joerg.Schilling at fokus.fraunhofer.de  Mon Sep 26 12:51:58 2011
From: Joerg.Schilling at fokus.fraunhofer.de (Joerg Schilling)
Date: Mon, 26 Sep 2011 12:51:58 +0200
Subject: [csw-maintainers] Pictures of Oslo gone?
In-Reply-To: <CALtRa-4P9WMRSCddJrPnvL=PNYpyUDAj484+zzXbd+r18bgGZw@mail.gmail.com>
References: <CEC003C7-3580-4DD9-BE32-263F0266150C@opencsw.org>
	<CALtRa-4P9WMRSCddJrPnvL=PNYpyUDAj484+zzXbd+r18bgGZw@mail.gmail.com>
Message-ID: <4e80594e.z1r1xppy3nCYToeM%Joerg.Schilling@fokus.fraunhofer.de>

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

> 2011/9/25 Dagobert Michelsen <dam at opencsw.org>:
> > there used to be the pictures of Oslo in here:
> > ?http://www.opencsw.org/2009/08/technical-summercamp-oslo-2009/
> > Is this related to the PHP update?
>
> I still see them there.

It may have been a result of the DNS outage last night at BO.

BTW: back home in Berlin since 2:20

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 skayser at opencsw.org  Mon Sep 26 20:45:31 2011
From: skayser at opencsw.org (Sebastian Kayser)
Date: Mon, 26 Sep 2011 20:45:31 +0200
Subject: [csw-maintainers] mgar 0.94-rc1 - changes and call for testing
Message-ID: <20110926184531.GH21825@sebastiankayser.de>

Hi everyone,

after some good feedback during summercamp, mgar 0.94rc1 comes hot on
the heels of 0.93. Most changes revolve around the indexing and
searching, but also include a commit fix that's needed for svn 1.7.

Testing is as easy as:

    alias mgar=~skayser/bin/mgar-rc     # [*]


Changes with 0.94-rc1:
* NEW command "status" to query VCS status (^= svn status)
* NEW command "reindex" to drop and re-build the search index
* NEW command alias "update" for "up"
* NEW added fallback to GARTYPE=v2 if GARTYPE and externals not set
* CHANGE "locate" command output now sorted
* CHANGE "locate" now automatically builds the index (if not present)
* CHANGE "locate" will update the index if it's older than 14 days
* CHANGE "locate" dropped a: prefix, search all recipe lines by default
* CHANGE "locate" use n: prefix instead of g: to search the name field
* FIX "index" now properly encodes file paths with special signs (e.g. '+')
* FIX "init-existing" now properly removes obsolete gar/ symlinks
* FIX ~/.garrc variable assignments couldn't cope with tabs (Rafael Ostertag)
* FIX "commit" didn't include parent when needed #58 (Dagobert Michelsen)
* DROP command "scm", typing "svn <sth>" is shorter than "mgar scm <sth>"


Feedback welcome!

Sebastian

[*] mgar-rc gets updated whenever features/fixes are considered for public
testing. By keeping the above alias you can help to test new mgar versions
and also easily fall back to the official version.

From bonivart at opencsw.org  Mon Sep 26 22:00:07 2011
From: bonivart at opencsw.org (Peter Bonivart)
Date: Mon, 26 Sep 2011 22:00:07 +0200
Subject: [csw-maintainers] Pictures of Oslo gone?
In-Reply-To: <4e80594e.z1r1xppy3nCYToeM%Joerg.Schilling@fokus.fraunhofer.de>
References: <CEC003C7-3580-4DD9-BE32-263F0266150C@opencsw.org>
	<CALtRa-4P9WMRSCddJrPnvL=PNYpyUDAj484+zzXbd+r18bgGZw@mail.gmail.com>
	<4e80594e.z1r1xppy3nCYToeM%Joerg.Schilling@fokus.fraunhofer.de>
Message-ID: <CABY0g1WiVcWbnJnjyrApezpgRttfFRMysbLKYdfNEa9V6YV5cA@mail.gmail.com>

On Mon, Sep 26, 2011 at 12:51 PM, Joerg Schilling
<Joerg.Schilling at fokus.fraunhofer.de> wrote:
> Maciej (Matchek) Blizi??ski <maciej at opencsw.org> wrote:
>
>> 2011/9/25 Dagobert Michelsen <dam at opencsw.org>:
>> > there used to be the pictures of Oslo in here:
>> > ?http://www.opencsw.org/2009/08/technical-summercamp-oslo-2009/
>> > Is this related to the PHP update?
>>
>> I still see them there.
>
> It may have been a result of the DNS outage last night at BO.

Or maybe Dago used his iPad because the extra pictures are shown using
the evil Flash. :)

> BTW: back home in Berlin since 2:20

I just got home now (21.30).


/peter

From bwalton at opencsw.org  Tue Sep 27 03:40:06 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Mon, 26 Sep 2011 21:40:06 -0400
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <99b8228d3469eebcfe0861fcb5c0e6c3@wilbury.sk>
References: <a3e2ffdb-1dc4-4829-972d-67d419014151@iris>
	<472d8e31-144d-40ae-b467-8f2a2afe3a3c@email.android.com>
	<CABY0g1VtY3SezofmfVZuhFKETMEk9jK8MWsW9omJ6ygvQzz8Mw@mail.gmail.com>
	<9f53450b-55ff-4db0-baec-d45278c814f4@email.android.com>
	<99b8228d3469eebcfe0861fcb5c0e6c3@wilbury.sk>
Message-ID: <1317086284-sup-1823@pinkfloyd.chass.utoronto.ca>

Excerpts from Juraj Lutter's message of Thu Sep 08 07:49:34 -0400 2011:

> I would go with alternatives. It's elegant and "systematic"
> approach. 

Having thought more about this, I decided that in order to provide the
best possible user experience, alternatives was better.  I've made the
adjustments required to see two packages generated, each containing an
alternative.

pkg_get_stub/CSWpkgget -> /opt/csw/bin/pkg-get.deprecationnotice
pkgget_deprecated/CSWpkgget-deprecated -> /opt/csw/bin/pkg-get.deprecated

CSWpkgget depends on CSWpkgget-deprecated and CSWpkgutil.
CSWpkgget-deprecated depends on CSWpkgutil.

The deprecation notice printed by
/opt/csw/bin/pkg-get.deprecationnotice contains the command required
to toggle the alternative back to a working version of the tool.

Given this setup, sites using pkg-get and wanting to continue can
either alter their scripts or reconfigure the altneratives
setup...whichever is easiest for their network.

With the catalog changes discussed in Kiel, we'll want to push this
out with lots of notice.

I'd appreciate verification of the updated packages, which are
available at: http://buildfarm.opencsw.org/experimental.html#pkgget

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From maciej at opencsw.org  Tue Sep 27 11:10:11 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Tue, 27 Sep 2011 10:10:11 +0100
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <1317086284-sup-1823@pinkfloyd.chass.utoronto.ca>
References: <a3e2ffdb-1dc4-4829-972d-67d419014151@iris>
	<472d8e31-144d-40ae-b467-8f2a2afe3a3c@email.android.com>
	<CABY0g1VtY3SezofmfVZuhFKETMEk9jK8MWsW9omJ6ygvQzz8Mw@mail.gmail.com>
	<9f53450b-55ff-4db0-baec-d45278c814f4@email.android.com>
	<99b8228d3469eebcfe0861fcb5c0e6c3@wilbury.sk>
	<1317086284-sup-1823@pinkfloyd.chass.utoronto.ca>
Message-ID: <CALtRa-79pz+qrV8FXe+TWYgKwco9+5u=niKkxynut-=FZQm_6Q@mail.gmail.com>

2011/9/27 Ben Walton <bwalton at opencsw.org>:
> I'd appreciate verification of the updated packages, which are
> available at: http://buildfarm.opencsw.org/experimental.html#pkgget

Tested, works as expected, switching alternatives back and forth works too.

Maciej

From skayser at opencsw.org  Tue Sep 27 14:13:55 2011
From: skayser at opencsw.org (Sebastian Kayser)
Date: Tue, 27 Sep 2011 14:13:55 +0200
Subject: [csw-maintainers] the future of pkg-get...
In-Reply-To: <1317086284-sup-1823@pinkfloyd.chass.utoronto.ca>
References: <a3e2ffdb-1dc4-4829-972d-67d419014151@iris>
	<472d8e31-144d-40ae-b467-8f2a2afe3a3c@email.android.com>
	<CABY0g1VtY3SezofmfVZuhFKETMEk9jK8MWsW9omJ6ygvQzz8Mw@mail.gmail.com>
	<9f53450b-55ff-4db0-baec-d45278c814f4@email.android.com>
	<99b8228d3469eebcfe0861fcb5c0e6c3@wilbury.sk>
	<1317086284-sup-1823@pinkfloyd.chass.utoronto.ca>
Message-ID: <20110927121355.GO21825@sebastiankayser.de>

* Ben Walton <bwalton at opencsw.org> wrote:
> Excerpts from Juraj Lutter's message of Thu Sep 08 07:49:34 -0400 2011:
> 
> > I would go with alternatives. It's elegant and "systematic"
> > approach. 
> 
> Having thought more about this, I decided that in order to provide the
> best possible user experience, alternatives was better.  I've made the
> adjustments required to see two packages generated, each containing an
> alternative.
> 
> pkg_get_stub/CSWpkgget -> /opt/csw/bin/pkg-get.deprecationnotice
> pkgget_deprecated/CSWpkgget-deprecated -> /opt/csw/bin/pkg-get.deprecated
> 
> [...]
>
> I'd appreciate verification of the updated packages, which are
> available at: http://buildfarm.opencsw.org/experimental.html#pkgget

Tested in a global zone, installation and switching of alternatives
worked fine. Good approach and nice work. Thoughts:

1) Add some quickstart comments to the deprecation notice? The
referenced pkgutil(1) man page doesn't provide a quickstart as such.
Example:

"Please use pkgutil(1) instead. The CSWpkgutil package should
have been installed at the same time as this CSWpkgget update.
Setting the desired catalog in /etc/opt/csw/pkgutil.conf should
suffice to get you started. Most commands that you are used to
from pkg-get are also available with pkgutil (plus many more).
For usage examples plus reference information see pkgutil(1).

    PAGER='less +/EXAMPLES' man pkgutil
    PAGER='less +/OPTIONS' man pkgutil
    PAGER='less +/CONFIGURATION' man pkgutil

"

Feel free to adapt or reword at will. :)

2) Also add instructions on how to remove CSWpkgget once you've settled
with pkgutil. (pkgrm CSWpkgget; pkgrm CSWpkgget-deprecated)?

3) Has anyone tested the pkg-get upgrade with local zones? What happens
if someone doesn't have alternatives installed yet?

4) Generate an example pkgutil.conf based on settings from pkg-get.conf
and point the user to it? Most pkg-get settings should easily be
mappable to equivalent pkgutil settings.

Sebastian

From ihsan at opencsw.org  Tue Sep 27 14:21:51 2011
From: ihsan at opencsw.org (=?UTF-8?B?xLBoc2FuIERvxJ9hbg==?=)
Date: Tue, 27 Sep 2011 14:21:51 +0200
Subject: [csw-maintainers] HEADS UP: /home/newpkgs is going to be deleted on
	bender.opencsw.org
Message-ID: <4E81BFDF.1000700@opencsw.org>

Hi,

After we moved to the new release system, there is no longer need for 
the /home/newpkgs directory on bender.opencsw.org. Therefore, I'm going 
to delete this directory by the 1st October 2011.

If you would like to release this packages, please release it with the 
new csw-upload-pkg.

Amount of packages per maintainer:
    8 ai
    8 benny
   21 bwalton
    3 dam
    2 gmarler
    2 james
    1 kester
    2 lsw
   13 maciej
    5 markp
    2 opk
   10 phil
    2 prabatty
   26 rupert
    2 yann




Ihsan

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

From skayser at opencsw.org  Tue Sep 27 19:24:55 2011
From: skayser at opencsw.org (Sebastian Kayser)
Date: Tue, 27 Sep 2011 19:24:55 +0200
Subject: [csw-maintainers] checkpkg: check for empty files?
Message-ID: <20110927172455.GQ21825@sebastiankayser.de>

Hi,

what do you guys think about a checkpkg check that throws an error if it
encounters empty files in a package? Are there valid cases for shipping
empty files? Maciej, can you query the pkgdb for empty files?

Background:
stunnel overhauled its autoconf setup with the recent 4.44 release and
as a result, messed up its sample certificate generation. The generated
and packaged sample certificate was empty. A good look at the build
process showed the issue, but this could have also gone unnoticed.

Sebastian

From wilbury at opencsw.org  Tue Sep 27 19:38:23 2011
From: wilbury at opencsw.org (Juraj Lutter)
Date: Tue, 27 Sep 2011 19:38:23 +0200
Subject: [csw-maintainers]
 =?utf-8?q?checkpkg=3A_check_for_empty_files=3F?=
In-Reply-To: <20110927172455.GQ21825@sebastiankayser.de>
References: <20110927172455.GQ21825@sebastiankayser.de>
Message-ID: <96dafdea77e0d70797c6707d90dc1615@wilbury.sk>

On 27.09.2011 19:24, Sebastian Kayser wrote:
> Background:
> stunnel overhauled its autoconf setup with the recent 4.44 release 
> and
> as a result, messed up its sample certificate generation. The 
> generated
> and packaged sample certificate was empty. A good look at the build
> process showed the issue, but this could have also gone unnoticed.

It only should issue a warning instead of error. Or there should be a 
possibility
to override the error.

-- 
Juraj Lutter <wilbury at opencsw.org>

From bonivart at opencsw.org  Tue Sep 27 19:44:48 2011
From: bonivart at opencsw.org (Peter Bonivart)
Date: Tue, 27 Sep 2011 19:44:48 +0200
Subject: [csw-maintainers] checkpkg: check for empty files?
In-Reply-To: <96dafdea77e0d70797c6707d90dc1615@wilbury.sk>
References: <20110927172455.GQ21825@sebastiankayser.de>
	<96dafdea77e0d70797c6707d90dc1615@wilbury.sk>
Message-ID: <CABY0g1UL62Bs04Q6u0QRiH1KmGX7_7KDeb7M6f=ScDV92huuOw@mail.gmail.com>

On Tue, Sep 27, 2011 at 7:38 PM, Juraj Lutter <wilbury at opencsw.org> wrote:
> It only should issue a warning instead of error. Or there should be a
> possibility
> to override the error.

There's only errors, no warnings, but everything can be overridden.
Please put a comment in the Makefile on why you're overriding
something.

/peter

From bwalton at opencsw.org  Tue Sep 27 20:04:32 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Tue, 27 Sep 2011 14:04:32 -0400
Subject: [csw-maintainers] checkpkg: check for empty files?
In-Reply-To: <96dafdea77e0d70797c6707d90dc1615@wilbury.sk>
References: <20110927172455.GQ21825@sebastiankayser.de>
	<96dafdea77e0d70797c6707d90dc1615@wilbury.sk>
Message-ID: <1317146541-sup-1768@pinkfloyd.chass.utoronto.ca>

Excerpts from Juraj Lutter's message of Tue Sep 27 13:38:23 -0400 2011:

> It only should issue a warning instead of error. Or there should be
> a possibility to override the error.

If I understand checkpkg workings correctly, every test that generates
an error automatically has an override available based on the name of
the test.  So yes, it can be a warning that most of the time is valid
and when it's not, the override can be used.

I _think_ this is a sane check in most cases...off the top of my head,
I can't think of a place where I'd want to deliver an empty file.
(Queue 8 people that can!)

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From wilbury at opencsw.org  Tue Sep 27 20:57:40 2011
From: wilbury at opencsw.org (Juraj Lutter)
Date: Tue, 27 Sep 2011 20:57:40 +0200
Subject: [csw-maintainers] checkpkg: check for empty files?
In-Reply-To: <1317146541-sup-1768@pinkfloyd.chass.utoronto.ca>
References: <20110927172455.GQ21825@sebastiankayser.de>	<96dafdea77e0d70797c6707d90dc1615@wilbury.sk>
	<1317146541-sup-1768@pinkfloyd.chass.utoronto.ca>
Message-ID: <4E821CA4.5010000@opencsw.org>

On 09/27/2011 08:04 PM, Ben Walton wrote:
> I _think_ this is a sane check in most cases...off the top of my head,
> I can't think of a place where I'd want to deliver an empty file.
> (Queue 8 people that can!)

Roundcube webmail ships empty index.php in some directories, for example.

-- 
Juraj Lutter <wilbury at opencsw.org>

From bwalton at opencsw.org  Tue Sep 27 21:02:06 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Tue, 27 Sep 2011 15:02:06 -0400
Subject: [csw-maintainers] checkpkg: check for empty files?
In-Reply-To: <4E821CA4.5010000@opencsw.org>
References: <20110927172455.GQ21825@sebastiankayser.de>
	<96dafdea77e0d70797c6707d90dc1615@wilbury.sk>
	<1317146541-sup-1768@pinkfloyd.chass.utoronto.ca>
	<4E821CA4.5010000@opencsw.org>
Message-ID: <1317150100-sup-8384@pinkfloyd.chass.utoronto.ca>

Excerpts from Juraj Lutter's message of Tue Sep 27 14:57:40 -0400 2011:

> Roundcube webmail ships empty index.php in some directories, for example.

1 down, 7 to go! :)  Nice to have an example where this is a valid
item though.

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From skayser at opencsw.org  Tue Sep 27 21:05:07 2011
From: skayser at opencsw.org (Sebastian Kayser)
Date: Tue, 27 Sep 2011 21:05:07 +0200
Subject: [csw-maintainers] checkpkg: check for empty files?
In-Reply-To: <4E821CA4.5010000@opencsw.org>
References: <20110927172455.GQ21825@sebastiankayser.de>
	<96dafdea77e0d70797c6707d90dc1615@wilbury.sk>
	<1317146541-sup-1768@pinkfloyd.chass.utoronto.ca>
	<4E821CA4.5010000@opencsw.org>
Message-ID: <20110927190507.GT21825@sebastiankayser.de>

* Juraj Lutter <wilbury at opencsw.org> wrote:
> On 09/27/2011 08:04 PM, Ben Walton wrote:
> > I _think_ this is a sane check in most cases...off the top of my head,
> > I can't think of a place where I'd want to deliver an empty file.
> > (Queue 8 people that can!)
> 
> Roundcube webmail ships empty index.php in some directories, for example.

Do you happen to know the rationale?

Sebastian

From wilbury at opencsw.org  Tue Sep 27 21:06:47 2011
From: wilbury at opencsw.org (Juraj Lutter)
Date: Tue, 27 Sep 2011 21:06:47 +0200
Subject: [csw-maintainers] checkpkg: check for empty files?
In-Reply-To: <20110927190507.GT21825@sebastiankayser.de>
References: <20110927172455.GQ21825@sebastiankayser.de>	<96dafdea77e0d70797c6707d90dc1615@wilbury.sk>	<1317146541-sup-1768@pinkfloyd.chass.utoronto.ca>	<4E821CA4.5010000@opencsw.org>
	<20110927190507.GT21825@sebastiankayser.de>
Message-ID: <4E821EC7.90306@opencsw.org>

On 09/27/2011 09:05 PM, Sebastian Kayser wrote:
> * Juraj Lutter <wilbury at opencsw.org> wrote:
>> On 09/27/2011 08:04 PM, Ben Walton wrote:
>>> I _think_ this is a sane check in most cases...off the top of my head,
>>> I can't think of a place where I'd want to deliver an empty file.
>>> (Queue 8 people that can!)
>>
>> Roundcube webmail ships empty index.php in some directories, for example.

Yes. To not allow browsing directories in case when Options Indexes is
enabled. It goes
on log dirs, temp dirs and such.

-- 
Juraj Lutter <wilbury at opencsw.org>

From maciej at opencsw.org  Tue Sep 27 21:38:28 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Tue, 27 Sep 2011 20:38:28 +0100
Subject: [csw-maintainers] checkpkg: check for empty files?
In-Reply-To: <1317146541-sup-1768@pinkfloyd.chass.utoronto.ca>
References: <20110927172455.GQ21825@sebastiankayser.de>
	<96dafdea77e0d70797c6707d90dc1615@wilbury.sk>
	<1317146541-sup-1768@pinkfloyd.chass.utoronto.ca>
Message-ID: <CALtRa-63t8JwWXjKsafdzyWN2aiWzdPROyaAii-J7AUUp4kWMw@mail.gmail.com>

2011/9/27 Ben Walton <bwalton at opencsw.org>:
> I _think_ this is a sane check in most cases...off the top of my head,
> I can't think of a place where I'd want to deliver an empty file.
> (Queue 8 people that can!)

We can take an empirical approach.  Implement the test, and run it
against the whole catalog.  Then examine all the cases - how many
there are, which ones seem to be false positives, and which ones seem
to be valid.  Then we can make the decision.  In the past, I usually
did it on my own, but now that more people are interested, we can
review them together.

For those interested, here's the superslow web interface showing error
tags for all the catalogs:

http://buildfarm.opencsw.org/pkgdb/error-tags/

Maciej

From jcraig at opencsw.org  Tue Sep 27 22:08:15 2011
From: jcraig at opencsw.org (Jonathan Craig)
Date: Tue, 27 Sep 2011 16:08:15 -0400
Subject: [csw-maintainers] Website QA Page
Message-ID: <CAH40YUJPmzH71sNFJw9potcG7AHRqpBwatgm6ZGKVX5eR5wLPw@mail.gmail.com>

I've noticed that two of my packages on my QA web page
(http://www.opencsw.org/qa/maintainer/jcraig/) indicate that they are
not "in" GAR.  Both packages were in fact built using GAR so I'm not
sure if this is a problem on my  end or the catalogs end.  Should I
worry or will it resolve itself over time?  This issue dates back to
the old release manager so I'm not sure if the problem is simply a
result of the change in release process.

Thanks,

Jon

From bonivart at opencsw.org  Tue Sep 27 22:28:51 2011
From: bonivart at opencsw.org (Peter Bonivart)
Date: Tue, 27 Sep 2011 22:28:51 +0200
Subject: [csw-maintainers] Website QA Page
In-Reply-To: <CAH40YUJPmzH71sNFJw9potcG7AHRqpBwatgm6ZGKVX5eR5wLPw@mail.gmail.com>
References: <CAH40YUJPmzH71sNFJw9potcG7AHRqpBwatgm6ZGKVX5eR5wLPw@mail.gmail.com>
Message-ID: <CABY0g1Uvbv1eP2B-02vkBKprU_tXW1_kLiGx=M2E+175_VkyFw@mail.gmail.com>

On Tue, Sep 27, 2011 at 10:08 PM, Jonathan Craig <jcraig at opencsw.org> wrote:
> I've noticed that two of my packages on my QA web page
> (http://www.opencsw.org/qa/maintainer/jcraig/) indicate that they are
> not "in" GAR. ?Both packages were in fact built using GAR so I'm not
> sure if this is a problem on my ?end or the catalogs end. ?Should I
> worry or will it resolve itself over time? ?This issue dates back to
> the old release manager so I'm not sure if the problem is simply a
> result of the change in release process.

The package browser is stale since Phil left, he was the one updating
the db. New stuff is in the works.

/peter

From jcraig at opencsw.org  Tue Sep 27 22:31:56 2011
From: jcraig at opencsw.org (Jonathan Craig)
Date: Tue, 27 Sep 2011 16:31:56 -0400
Subject: [csw-maintainers] Website QA Page
In-Reply-To: <CABY0g1Uvbv1eP2B-02vkBKprU_tXW1_kLiGx=M2E+175_VkyFw@mail.gmail.com>
References: <CAH40YUJPmzH71sNFJw9potcG7AHRqpBwatgm6ZGKVX5eR5wLPw@mail.gmail.com>
	<CABY0g1Uvbv1eP2B-02vkBKprU_tXW1_kLiGx=M2E+175_VkyFw@mail.gmail.com>
Message-ID: <CAH40YULfsJ8pmepsy6+QxY-3hzpj6OLKa3tPpfaYE6YK_drZfg@mail.gmail.com>

Thanks, figured that was the case but thought I'd check before adding more
packages.
On Sep 27, 2011 4:29 PM, "Peter Bonivart" <bonivart at opencsw.org> wrote:
> On Tue, Sep 27, 2011 at 10:08 PM, Jonathan Craig <jcraig at opencsw.org>
wrote:
>> I've noticed that two of my packages on my QA web page
>> (http://www.opencsw.org/qa/maintainer/jcraig/) indicate that they are
>> not "in" GAR.  Both packages were in fact built using GAR so I'm not
>> sure if this is a problem on my  end or the catalogs end.  Should I
>> worry or will it resolve itself over time?  This issue dates back to
>> the old release manager so I'm not sure if the problem is simply a
>> result of the change in release process.
>
> The package browser is stale since Phil left, he was the one updating
> the db. New stuff is in the works.
>
> /peter
> _______________________________________________
> maintainers mailing list
> maintainers at lists.opencsw.org
> https://lists.opencsw.org/mailman/listinfo/maintainers
> .:: This mailing list's archive is public. ::.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20110927/adc32b68/attachment-0001.html>

From bonivart at opencsw.org  Tue Sep 27 22:34:20 2011
From: bonivart at opencsw.org (Peter Bonivart)
Date: Tue, 27 Sep 2011 22:34:20 +0200
Subject: [csw-maintainers] Website QA Page
In-Reply-To: <CAH40YULfsJ8pmepsy6+QxY-3hzpj6OLKa3tPpfaYE6YK_drZfg@mail.gmail.com>
References: <CAH40YUJPmzH71sNFJw9potcG7AHRqpBwatgm6ZGKVX5eR5wLPw@mail.gmail.com>
	<CABY0g1Uvbv1eP2B-02vkBKprU_tXW1_kLiGx=M2E+175_VkyFw@mail.gmail.com>
	<CAH40YULfsJ8pmepsy6+QxY-3hzpj6OLKa3tPpfaYE6YK_drZfg@mail.gmail.com>
Message-ID: <CABY0g1V+9zxpe+bzfPe+veueG6cYKxb-NcSJD6rdyPbzWfZ1sQ@mail.gmail.com>

On Tue, Sep 27, 2011 at 10:31 PM, Jonathan Craig <jcraig at opencsw.org> wrote:
> Thanks, figured that was the case but thought I'd check before adding more
> packages.

Please do add more packages. :)

/peter

From dam at opencsw.org  Wed Sep 28 09:36:54 2011
From: dam at opencsw.org (Dagobert Michelsen)
Date: Wed, 28 Sep 2011 09:36:54 +0200
Subject: [csw-maintainers] checkpkg: check for empty files?
In-Reply-To: <20110927172455.GQ21825@sebastiankayser.de>
References: <20110927172455.GQ21825@sebastiankayser.de>
Message-ID: <CBE4C257-3E9C-48C0-B27F-A7C760F3609B@opencsw.org>

Hi,

Am 27.09.2011 um 19:24 schrieb Sebastian Kayser:
> what do you guys think about a checkpkg check that throws an error if it
> encounters empty files in a package? Are there valid cases for shipping
> empty files? Maciej, can you query the pkgdb for empty files?
> 
> Background:
> stunnel overhauled its autoconf setup with the recent 4.44 release and
> as a result, messed up its sample certificate generation. The generated
> and packaged sample certificate was empty. A good look at the build
> process showed the issue, but this could have also gone unnoticed.

This looks like a perfect situation for a plugin where anyone interested
can check for empty files to have a rationale for the real implementation.


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


From maciej at opencsw.org  Wed Sep 28 12:01:08 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Wed, 28 Sep 2011 11:01:08 +0100
Subject: [csw-maintainers] checkpkg: check for empty files?
In-Reply-To: <CBE4C257-3E9C-48C0-B27F-A7C760F3609B@opencsw.org>
References: <20110927172455.GQ21825@sebastiankayser.de>
	<CBE4C257-3E9C-48C0-B27F-A7C760F3609B@opencsw.org>
Message-ID: <CALtRa-5Lir+PnCHTGviQ3=bjFaikTqTKhSJarxrUM=W5brjr2w@mail.gmail.com>

2011/9/28 Dagobert Michelsen <dam at opencsw.org>:
> Hi,
>
> Am 27.09.2011 um 19:24 schrieb Sebastian Kayser:
>> what do you guys think about a checkpkg check that throws an error if it
>> encounters empty files in a package? Are there valid cases for shipping
>> empty files? Maciej, can you query the pkgdb for empty files?
>>
>> Background:
>> stunnel overhauled its autoconf setup with the recent 4.44 release and
>> as a result, messed up its sample certificate generation. The generated
>> and packaged sample certificate was empty. A good look at the build
>> process showed the issue, but this could have also gone unnoticed.
>
> This looks like a perfect situation for a plugin where anyone interested
> can check for empty files to have a rationale for the real implementation.

I'm not that keen on investing time in developing a plugin
infrastructure without evidence that it will be actually used.
I developed a plugin infrastructure once, advocated it[1], and while
the reception of the new functionality was generally good, there was
no interest in plugins.

What I suggest we do now, is this: I will expose the package stats
data via REST.  When someone writes a check using that data, and wants
to include it in the standard checkpkg runs, we'll add some form of
data passing from checkpkg to their code.  Does it sound good?

Maciej

[1] http://lists.opencsw.org/pipermail/maintainers/2010-January/010918.html

From bwalton at opencsw.org  Wed Sep 28 15:09:58 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Wed, 28 Sep 2011 09:09:58 -0400
Subject: [csw-maintainers] checkpkg: check for empty files?
In-Reply-To: <CBE4C257-3E9C-48C0-B27F-A7C760F3609B@opencsw.org>
References: <20110927172455.GQ21825@sebastiankayser.de>
	<CBE4C257-3E9C-48C0-B27F-A7C760F3609B@opencsw.org>
Message-ID: <1317215228-sup-1871@pinkfloyd.chass.utoronto.ca>

Excerpts from Dagobert Michelsen's message of Wed Sep 28 03:36:54 -0400 2011:

Hi Dago,

> This looks like a perfect situation for a plugin where anyone
> interested can check for empty files to have a rationale for the
> real implementation.

I think that the way full checks are implemented now is about[1] as
cheap as a plugin anyway (unless you need to extend a data structure),
so this same benefit could be had by writing the test locally and
submitting it for review if it proves useful.

Thanks
-Ben

[1] With the exception that you need to know which file to
    modify...that is a one time learning cost.
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From bwalton at opencsw.org  Thu Sep 29 17:04:47 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Thu, 29 Sep 2011 11:04:47 -0400
Subject: [csw-maintainers] HEADS UP: /home/newpkgs is going to be
	deleted on bender.opencsw.org
In-Reply-To: <4E81BFDF.1000700@opencsw.org>
References: <4E81BFDF.1000700@opencsw.org>
Message-ID: <1317308671-sup-3619@pinkfloyd.chass.utoronto.ca>

Excerpts from ?hsan Do?an's message of Tue Sep 27 08:21:51 -0400 2011:

>    21 bwalton

Purged.  Thanks for the notice!

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From bwalton at opencsw.org  Thu Sep 29 20:50:52 2011
From: bwalton at opencsw.org (Ben Walton)
Date: Thu, 29 Sep 2011 14:50:52 -0400
Subject: [csw-maintainers] Information about the OS release inside the
	package
In-Reply-To: <CALtRa-4FpUhuZ+s5uMRoE4s1sS8=0qgA6WcCO18pUSP6cHYsmg@mail.gmail.com>
References: <CALtRa-4FpUhuZ+s5uMRoE4s1sS8=0qgA6WcCO18pUSP6cHYsmg@mail.gmail.com>
Message-ID: <1317322205-sup-4442@pinkfloyd.chass.utoronto.ca>

Excerpts from Maciej (Matchek) Blizi?ski's message of Mon Sep 26 05:31:45 -0400 2011:

Hi Maciej,

> SunOS5.9.  Is there anything else that can reliably detect the OS
> release?

Not that I'm aware of, but maybe this would be a good addition to what
GAR stuffs into the pkginfo file?

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302


From maciej at opencsw.org  Fri Sep 30 00:15:14 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Thu, 29 Sep 2011 23:15:14 +0100
Subject: [csw-maintainers] Information about the OS release inside the
	package
In-Reply-To: <1317322205-sup-4442@pinkfloyd.chass.utoronto.ca>
References: <CALtRa-4FpUhuZ+s5uMRoE4s1sS8=0qgA6WcCO18pUSP6cHYsmg@mail.gmail.com>
	<1317322205-sup-4442@pinkfloyd.chass.utoronto.ca>
Message-ID: <CALtRa-4oughPbtnmERHrbBPUi5N7XFV-tx4nHDZPu8SnTKoKqQ@mail.gmail.com>

2011/9/29 Ben Walton <bwalton at opencsw.org>:
> Not that I'm aware of, but maybe this would be a good addition to what
> GAR stuffs into the pkginfo file?

It certainly would not hurt.  It would provide an additional layer of
ensuring that the file name matches the content of the package.

Dago, what do you think about it?

Maciej

From dam at opencsw.org  Fri Sep 30 10:24:21 2011
From: dam at opencsw.org (Dagobert Michelsen)
Date: Fri, 30 Sep 2011 10:24:21 +0200
Subject: [csw-maintainers] Information about the OS release inside the
	package
In-Reply-To: <CALtRa-4oughPbtnmERHrbBPUi5N7XFV-tx4nHDZPu8SnTKoKqQ@mail.gmail.com>
References: <CALtRa-4FpUhuZ+s5uMRoE4s1sS8=0qgA6WcCO18pUSP6cHYsmg@mail.gmail.com>
	<1317322205-sup-4442@pinkfloyd.chass.utoronto.ca>
	<CALtRa-4oughPbtnmERHrbBPUi5N7XFV-tx4nHDZPu8SnTKoKqQ@mail.gmail.com>
Message-ID: <FD9586A4-62F2-41A7-8EA9-14144BE6EE2A@opencsw.org>

Hi Maciej,

Am 30.09.2011 um 00:15 schrieb Maciej (Matchek) Blizi?ski:
> 2011/9/29 Ben Walton <bwalton at opencsw.org>:
>> Not that I'm aware of, but maybe this would be a good addition to what
>> GAR stuffs into the pkginfo file?
> 
> It certainly would not hurt.  It would provide an additional layer of
> ensuring that the file name matches the content of the package.
> 
> Dago, what do you think about it?

Fine with me. Like this?
  OPENCSW_PACKAGED_ON=sparc-5.9

Suggestions welcome.


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


From dam at opencsw.org  Fri Sep 30 10:49:27 2011
From: dam at opencsw.org (Dagobert Michelsen)
Date: Fri, 30 Sep 2011 10:49:27 +0200
Subject: [csw-maintainers] Magic Cookie for catalogs
Message-ID: <B87DAE8C-878A-4329-94A6-AD0EE80241C0@opencsw.org>

Hi,

I am currently fiddling with who mirrors OpenCSW, reaching mirror maintainers and
finding "unauthorized" mirrors. For this it would be more precise if we would introduce
a magic cookie in the catalog features which would help us identifying OpenCSW catalogs.
I could then google for that cookie and find occurrences and match that against what
we already have listed.

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


From maciej at opencsw.org  Fri Sep 30 11:02:03 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Fri, 30 Sep 2011 10:02:03 +0100
Subject: [csw-maintainers] Information about the OS release inside the
	package
In-Reply-To: <FD9586A4-62F2-41A7-8EA9-14144BE6EE2A@opencsw.org>
References: <CALtRa-4FpUhuZ+s5uMRoE4s1sS8=0qgA6WcCO18pUSP6cHYsmg@mail.gmail.com>
	<1317322205-sup-4442@pinkfloyd.chass.utoronto.ca>
	<CALtRa-4oughPbtnmERHrbBPUi5N7XFV-tx4nHDZPu8SnTKoKqQ@mail.gmail.com>
	<FD9586A4-62F2-41A7-8EA9-14144BE6EE2A@opencsw.org>
Message-ID: <CALtRa-6fcvPGO6hdqO8LUM6Ky5FWvan6YiCgpzzSj=HAhbF5LA@mail.gmail.com>

2011/9/30 Dagobert Michelsen <dam at opencsw.org>:
> Fine with me. Like this?
> ?OPENCSW_PACKAGED_ON=sparc-5.9

Variable name suggestions:
- OPENCSW_OS_RELEASE
- OPENCSW_OSREL

Value suggestions:
- SunOS5.9 (I'd prefer this one)
- 5.9

From maciej at opencsw.org  Fri Sep 30 11:06:37 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Fri, 30 Sep 2011 10:06:37 +0100
Subject: [csw-maintainers] Magic Cookie for catalogs
In-Reply-To: <B87DAE8C-878A-4329-94A6-AD0EE80241C0@opencsw.org>
References: <B87DAE8C-878A-4329-94A6-AD0EE80241C0@opencsw.org>
Message-ID: <CALtRa-4JVE3EemGnGwcWvhzzh6iyuNPV+N+80jXW4XSZZp0y5g@mail.gmail.com>

2011/9/30 Dagobert Michelsen <dam at opencsw.org>:
> Hi,
>
> I am currently fiddling with who mirrors OpenCSW, reaching mirror maintainers and
> finding "unauthorized" mirrors. For this it would be more precise if we would introduce
> a magic cookie in the catalog features which would help us identifying OpenCSW catalogs.
> I could then google for that cookie and find occurrences and match that against what
> we already have listed.
>
> Thoughts?

Cool idea!

echo -n OpenCSW | gmd5sum

Currently does not match any documents.  (Not posting the actual value
to prevent list archives from coming up in search results.)

From dam at opencsw.org  Fri Sep 30 14:11:43 2011
From: dam at opencsw.org (Dagobert Michelsen)
Date: Fri, 30 Sep 2011 14:11:43 +0200
Subject: [csw-maintainers] Information about the OS release inside the
	package
In-Reply-To: <CALtRa-6fcvPGO6hdqO8LUM6Ky5FWvan6YiCgpzzSj=HAhbF5LA@mail.gmail.com>
References: <CALtRa-4FpUhuZ+s5uMRoE4s1sS8=0qgA6WcCO18pUSP6cHYsmg@mail.gmail.com>
	<1317322205-sup-4442@pinkfloyd.chass.utoronto.ca>
	<CALtRa-4oughPbtnmERHrbBPUi5N7XFV-tx4nHDZPu8SnTKoKqQ@mail.gmail.com>
	<FD9586A4-62F2-41A7-8EA9-14144BE6EE2A@opencsw.org>
	<CALtRa-6fcvPGO6hdqO8LUM6Ky5FWvan6YiCgpzzSj=HAhbF5LA@mail.gmail.com>
Message-ID: <1B3FABAF-810B-4B7B-8557-F262D3CC55C6@opencsw.org>

Hi Maciej,

Am 30.09.2011 um 11:02 schrieb Maciej (Matchek) Blizi?ski:
> 2011/9/30 Dagobert Michelsen <dam at opencsw.org>:
>> Fine with me. Like this?
>>  OPENCSW_PACKAGED_ON=sparc-5.9
> 
> Variable name suggestions:
> - OPENCSW_OS_RELEASE

> Value suggestions:
> - SunOS5.9 (I'd prefer this one)

Ok, do you also want this?
  OPENCSW_OS_ARCH=sparc


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


From dam at opencsw.org  Fri Sep 30 14:13:17 2011
From: dam at opencsw.org (Dagobert Michelsen)
Date: Fri, 30 Sep 2011 14:13:17 +0200
Subject: [csw-maintainers] Magic Cookie for catalogs
In-Reply-To: <CALtRa-4JVE3EemGnGwcWvhzzh6iyuNPV+N+80jXW4XSZZp0y5g@mail.gmail.com>
References: <B87DAE8C-878A-4329-94A6-AD0EE80241C0@opencsw.org>
	<CALtRa-4JVE3EemGnGwcWvhzzh6iyuNPV+N+80jXW4XSZZp0y5g@mail.gmail.com>
Message-ID: <5FF70CA4-6A97-4D98-8B94-B86945F87685@opencsw.org>

Hi Maciej,

Am 30.09.2011 um 11:06 schrieb Maciej (Matchek) Blizi?ski:
> 2011/9/30 Dagobert Michelsen <dam at opencsw.org>:
>> I am currently fiddling with who mirrors OpenCSW, reaching mirror maintainers and
>> finding "unauthorized" mirrors. For this it would be more precise if we would introduce
>> a magic cookie in the catalog features which would help us identifying OpenCSW catalogs.
>> I could then google for that cookie and find occurrences and match that against what
>> we already have listed.
> 
> Cool idea!
> 
> echo -n OpenCSW | gmd5sum
> 
> Currently does not match any documents.  (Not posting the actual value
> to prevent list archives from coming up in search results.)

Ok, I suggest cycling this on a regular (yearly?) basis like the hash for
  OpenCSW 2011
for really old catalogs to not show up any more.


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


From maciej at opencsw.org  Fri Sep 30 17:29:28 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Fri, 30 Sep 2011 16:29:28 +0100
Subject: [csw-maintainers] Information about the OS release inside the
	package
In-Reply-To: <1B3FABAF-810B-4B7B-8557-F262D3CC55C6@opencsw.org>
References: <CALtRa-4FpUhuZ+s5uMRoE4s1sS8=0qgA6WcCO18pUSP6cHYsmg@mail.gmail.com>
	<1317322205-sup-4442@pinkfloyd.chass.utoronto.ca>
	<CALtRa-4oughPbtnmERHrbBPUi5N7XFV-tx4nHDZPu8SnTKoKqQ@mail.gmail.com>
	<FD9586A4-62F2-41A7-8EA9-14144BE6EE2A@opencsw.org>
	<CALtRa-6fcvPGO6hdqO8LUM6Ky5FWvan6YiCgpzzSj=HAhbF5LA@mail.gmail.com>
	<1B3FABAF-810B-4B7B-8557-F262D3CC55C6@opencsw.org>
Message-ID: <CALtRa-66_Mt97hg-SxyVSoyRVxvXNgraOX5WQGpePnr7unWETQ@mail.gmail.com>

2011/9/30 Dagobert Michelsen <dam at opencsw.org>:
> Hi Maciej,
>
> Am 30.09.2011 um 11:02 schrieb Maciej (Matchek) Blizi?ski:
>> 2011/9/30 Dagobert Michelsen <dam at opencsw.org>:
>>> Fine with me. Like this?
>>> ?OPENCSW_PACKAGED_ON=sparc-5.9
>>
>> Variable name suggestions:
>> - OPENCSW_OS_RELEASE
>
>> Value suggestions:
>> - SunOS5.9 (I'd prefer this one)
>
> Ok, do you also want this?
> ?OPENCSW_OS_ARCH=sparc

That will be good too.

From dam at opencsw.org  Fri Sep 30 17:43:22 2011
From: dam at opencsw.org (Dagobert Michelsen)
Date: Fri, 30 Sep 2011 17:43:22 +0200
Subject: [csw-maintainers] Fwd: proftpd build problem
References: <201109301937.27994.ai@vsu.ru>
Message-ID: <6147D366-32DB-4386-BEF5-2300864D239B@opencsw.org>

Hi Andy,

(fwd'ing to maintainers@)

Anfang der weitergeleiteten E-Mail:
> On 26 of September 2011 23:52:02 Andy Igoshin <ai at vsu.ru> wrote:
>> when i run "./configure" or "CC=cc ./configure" "ar" is found
>> in /usr/ccs/bin
>> 
>> when i run "gmake configure" "ar" is not found and "ld" is found
>> in /usr/ucb. as a result building process fails.
> 
> i confirm that the problem exists.
> 
> when i add CONFIGURE_ENV += PATH=/usr/ccs/bin:/bin
> the project is built.

Not good. Have you committed it so I can have a look? Which path in the tree?

> one more thing. does anyone maintain mysql5 now?
> 
> the directory structure of /opt/csw/mysql5/lib is changed.
> is it final change or it will be changed from time to time?

Yes, Maciej maintains it.

Maciej: I think it is final, is 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


From maciej at opencsw.org  Fri Sep 30 18:24:17 2011
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Fri, 30 Sep 2011 17:24:17 +0100
Subject: [csw-maintainers] Fwd: proftpd build problem
In-Reply-To: <6147D366-32DB-4386-BEF5-2300864D239B@opencsw.org>
References: <201109301937.27994.ai@vsu.ru>
	<6147D366-32DB-4386-BEF5-2300864D239B@opencsw.org>
Message-ID: <CALtRa-4n25-OXYtbcS-diK0+DWxFPEQeZaFGbKN1NL2ocJ5wyw@mail.gmail.com>

2011/9/30 Dagobert Michelsen <dam at opencsw.org>:
>> one more thing. does anyone maintain mysql5 now?
>>
>> the directory structure of /opt/csw/mysql5/lib is changed.
>> is it final change or it will be changed from time to time?
>
> Yes, Maciej maintains it.
>
> Maciej: I think it is final, is it?

/opt/csw/mysql5/lib is going away. Libraries will be now in
/opt/csw/lib, the same goes for include files (now in
/opt/csw/include).

I've just built a new set of packages and pushed them to unstable.
Dago, if you refresh buildfarm with these packages, Andy will have the
current CSWmysql-dev to work with.

Maciej

From dam at opencsw.org  Fri Sep 30 21:53:11 2011
From: dam at opencsw.org (Dagobert Michelsen)
Date: Fri, 30 Sep 2011 21:53:11 +0200
Subject: [csw-maintainers] Information about the OS release inside the
	package
In-Reply-To: <CALtRa-66_Mt97hg-SxyVSoyRVxvXNgraOX5WQGpePnr7unWETQ@mail.gmail.com>
References: <CALtRa-4FpUhuZ+s5uMRoE4s1sS8=0qgA6WcCO18pUSP6cHYsmg@mail.gmail.com>
	<1317322205-sup-4442@pinkfloyd.chass.utoronto.ca>
	<CALtRa-4oughPbtnmERHrbBPUi5N7XFV-tx4nHDZPu8SnTKoKqQ@mail.gmail.com>
	<FD9586A4-62F2-41A7-8EA9-14144BE6EE2A@opencsw.org>
	<CALtRa-6fcvPGO6hdqO8LUM6Ky5FWvan6YiCgpzzSj=HAhbF5LA@mail.gmail.com>
	<1B3FABAF-810B-4B7B-8557-F262D3CC55C6@opencsw.org>
	<CALtRa-66_Mt97hg-SxyVSoyRVxvXNgraOX5WQGpePnr7unWETQ@mail.gmail.com>
Message-ID: <93C6C5F4-3896-483B-B849-7629EB6A650E@opencsw.org>

Hi Maciej,

Am 30.09.2011 um 17:29 schrieb Maciej (Matchek) Blizi?ski:
> 2011/9/30 Dagobert Michelsen <dam at opencsw.org>:
>> Am 30.09.2011 um 11:02 schrieb Maciej (Matchek) Blizi?ski:
>>> 2011/9/30 Dagobert Michelsen <dam at opencsw.org>:
>>>> Fine with me. Like this?
>>>>  OPENCSW_PACKAGED_ON=sparc-5.9
>>> 
>>> Variable name suggestions:
>>> - OPENCSW_OS_RELEASE
>> 
>>> Value suggestions:
>>> - SunOS5.9 (I'd prefer this one)
>> 
>> Ok, do you also want this?
>>  OPENCSW_OS_ARCH=sparc
> 
> That will be good too.

Done in mGAR v2, checks can implemented now:
  http://sourceforge.net/apps/trac/gar/changeset/15815


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


From dam at opencsw.org  Fri Sep 30 21:56:38 2011
From: dam at opencsw.org (Dagobert Michelsen)
Date: Fri, 30 Sep 2011 21:56:38 +0200
Subject: [csw-maintainers] Fwd: proftpd build problem
In-Reply-To: <CALtRa-4n25-OXYtbcS-diK0+DWxFPEQeZaFGbKN1NL2ocJ5wyw@mail.gmail.com>
References: <201109301937.27994.ai@vsu.ru>
	<6147D366-32DB-4386-BEF5-2300864D239B@opencsw.org>
	<CALtRa-4n25-OXYtbcS-diK0+DWxFPEQeZaFGbKN1NL2ocJ5wyw@mail.gmail.com>
Message-ID: <990CF0B0-0562-41F7-AE65-2E3D68D4ED8F@opencsw.org>

Hi Maciej,

Am 30.09.2011 um 18:24 schrieb Maciej (Matchek) Blizi?ski:
> 2011/9/30 Dagobert Michelsen <dam at opencsw.org>:
>>> one more thing. does anyone maintain mysql5 now?
>>> 
>>> the directory structure of /opt/csw/mysql5/lib is changed.
>>> is it final change or it will be changed from time to time?
>> 
>> Yes, Maciej maintains it.
>> 
>> Maciej: I think it is final, is it?
> 
> /opt/csw/mysql5/lib is going away. Libraries will be now in
> /opt/csw/lib, the same goes for include files (now in
> /opt/csw/include).
> 
> I've just built a new set of packages and pushed them to unstable.
> Dago, if you refresh buildfarm with these packages, Andy will have the
> current CSWmysql-dev to work with.

Updating unstable* now.


Best regards

  -- Dago

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


From dam at opencsw.org  Fri Sep 30 22:12:47 2011
From: dam at opencsw.org (Dagobert Michelsen)
Date: Fri, 30 Sep 2011 22:12:47 +0200
Subject: [csw-maintainers] proftpd build problem
In-Reply-To: <201109301947.44113.ai@vsu.ru>
References: <201109301937.27994.ai@vsu.ru>
	<6147D366-32DB-4386-BEF5-2300864D239B@opencsw.org>
	<201109301947.44113.ai@vsu.ru>
Message-ID: <CAF4D9F0-E33A-46AA-AA01-998BD09F946D@opencsw.org>

Hi Andy,

Am 30.09.2011 um 17:47 schrieb Andy Igoshin:
> On 30 of September 2011 19:43:22 Dagobert Michelsen wrote:
>> Anfang der weitergeleiteten E-Mail:
>>> On 26 of September 2011 23:52:02 Andy Igoshin <ai at vsu.ru> wrote:
>>>> when i run "./configure" or "CC=cc ./configure" "ar" is found
>>>> in /usr/ccs/bin
>>>> 
>>>> when i run "gmake configure" "ar" is not found and "ld" is found
>>>> in /usr/ucb. as a result building process fails.
>>> 
>>> i confirm that the problem exists.
>>> 
>>> when i add CONFIGURE_ENV += PATH=/usr/ccs/bin:/bin
>>> the project is built.
>> 
>> Not good. Have you committed it so I can have a look? Which path in the
>> tree?
> 
> yes

The problem is that you are setting CONFIGURE_ENV which replaces the GAR
defaults. With the new environment sanitization only the environment
variables defined here are exported to the build, allowing tight control
of the build environment for picky systems (like nspr or samba).
In earlier times the complete exported environment leaked into the build
which was changed recently to export only the actual exported variables.
Putting your defined in EXTRA_CONFIGURE_ENV is the correct solution as
the variables are to be added to the environment. As a rule of thumb:
MYVAR replace the variable in GAR completely for maximal control,
EXTRA_MYVAR adds the value to the defaults.

I have committed my changes to proftpd here:
  http://sourceforge.net/apps/trac/gar/changeset/15816

Please review if the usage of LD_LIBRARY_PATH is still needed during
configure time.

Additionally there was until now only the possibility to use
EXTRA_CONFIGURE_EXPORTS and then set the variable or CONFIGURE_ENV_<var>
for finer control, but no EXTRA_CONFIGURE_ENV. I have added this in
  http://sourceforge.net/apps/trac/gar/changeset/15817
as a shortcut to the existing way.

Please let me know if you encounter other 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