From bwalton at opencsw.org  Sun Feb  3 12:48:07 2013
From: bwalton at opencsw.org (Ben Walton)
Date: Sun, 3 Feb 2013 11:48:07 +0000
Subject: [csw-maintainers] new packages mailing list
Message-ID: <CAP30j15geGqj_Msn_9qT+6GMSASC6LRf5cVU368-s1EkOE+VTA@mail.gmail.com>

Hi All,

I'm doing a bit of cleanup on the ruby code I use for atom feeds, etc
and noticed that I'd written but never activated a script to take an
atom feed and produce a weekly mail digest.  Is there interest in this
function still?  If so, which list should the mail be sent to?  I'll
send a single message per catalog with the weekly changes.

Thanks
-Ben

From bwalton at opencsw.org  Sun Feb  3 14:12:43 2013
From: bwalton at opencsw.org (Ben Walton)
Date: Sun, 3 Feb 2013 13:12:43 +0000
Subject: [csw-maintainers] maintainer field empty for etty6
In-Reply-To: <CAP30j16BOJo+6QDZLr_6hXJOQrHnypFarzbxBSK2peiu-p5=Cg@mail.gmail.com>
References: <3d1e23d4f7eb56522c210b1897bd5d7e@opencsw.org>
	<CALtRa-6EWchKfn1eNWZMxSLxA5Wq4xZirbznV+420CLnESARgg@mail.gmail.com>
	<98A3C8B5-55A3-41D8-87AF-6C423D65B8DF@opencsw.org>
	<CAP30j15S41DxZGyxNq+KObg4BMwPU1baBPrN7Ye7stFp_WbmSw@mail.gmail.com>
	<CALtRa-5tV_TDwL7TtW5qkjKia-mzN2R3pA-OAtyG++BdGS6ooA@mail.gmail.com>
	<CAP30j14Pt1jaqvb=HAj5BgWft_F2FAuZVzi9AdpDDCzuVVCJdA@mail.gmail.com>
	<CALtRa-5CaON9MJn+abwycPyZpjaOQX8t6e5msUCR8h8y8LMZUg@mail.gmail.com>
	<CAP30j16BOJo+6QDZLr_6hXJOQrHnypFarzbxBSK2peiu-p5=Cg@mail.gmail.com>
Message-ID: <CAP30j14b1G9zwj_+yS+gcn0HZD1JmSnmrhRkJjqiXbm4A1+mGA@mail.gmail.com>

I've increased the timeout and things are now updating properly again.
 The original problem was actually different though.  There are
several packages from 2008, jetty6 among them, that have "Unnamed
Maintainer" <trygvel at opencsw.org> as part of the data for them.  This
was pulled from the pkgdb and is accurate as far as the automated
systems are concerned...the package files themselves embed this
incorrect data.

I'll fix the DB by hand for these few instances and that should be
sticky until either a) a full re-import of all data from the build
farm or b) someone updates the packages in question.  The first is
unlikely and the second would see things corrected properly anyway.

Thanks
-Ben

On Sat, Jan 26, 2013 at 12:00 PM, Ben Walton <bwalton at opencsw.org> wrote:
> Likely.  The ruby http library is (uncharacteristically) painful, but
> I should be able to adjust that setting.
>
> Thanks
> -Ben
>
> On Fri, Jan 25, 2013 at 8:20 PM, Maciej (Matchek) Blizi?ski
> <maciej at opencsw.org> wrote:
>> No dia 25/01/2013 20:36, "Ben Walton" <bwalton at opencsw.org> escreveu:
>>
>>
>>>
>>> It's causing timeouts in (at least) some calls to it.
>>
>> Can the http client be a bit more patient?
>>
>>
>> _______________________________________________
>> 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 Feb  3 17:38:38 2013
From: pfelecan at opencsw.org (Peter FELECAN)
Date: Sun, 03 Feb 2013 17:38:38 +0100
Subject: [csw-maintainers] new packages mailing list
In-Reply-To: <CAP30j15geGqj_Msn_9qT+6GMSASC6LRf5cVU368-s1EkOE+VTA@mail.gmail.com>
	(Ben Walton's message of "Sun, 3 Feb 2013 11:48:07 +0000")
References: <CAP30j15geGqj_Msn_9qT+6GMSASC6LRf5cVU368-s1EkOE+VTA@mail.gmail.com>
Message-ID: <x6a9rll5dd.fsf@opencsw.org>

Ben Walton <bwalton at opencsw.org> writes:

> I'm doing a bit of cleanup on the ruby code I use for atom feeds, etc
> and noticed that I'd written but never activated a script to take an
> atom feed and produce a weekly mail digest.  Is there interest in this
> function still?  If so, which list should the mail be sent to?  I'll
> send a single message per catalog with the weekly changes.

users?
-- 
Peter

From dam at opencsw.org  Sun Feb  3 17:40:03 2013
From: dam at opencsw.org (Dagobert Michelsen)
Date: Sun, 3 Feb 2013 17:40:03 +0100
Subject: [csw-maintainers] Problems with login.opencsw.org
Message-ID: <A8F7FD5E-879D-4D8B-9EF8-9CA88FC41D99@opencsw.org>

Hi folks,

there is a problem with login.opencsw.org at the moment. Jan is looking at it
and it will hopefully be back online soon.


Best regards

 -- Dago

From jh at opencsw.org  Sun Feb  3 18:00:19 2013
From: jh at opencsw.org (Jan Holzhueter)
Date: Sun, 03 Feb 2013 18:00:19 +0100
Subject: [csw-maintainers] Problems with login.opencsw.org
In-Reply-To: <A8F7FD5E-879D-4D8B-9EF8-9CA88FC41D99@opencsw.org>
References: <A8F7FD5E-879D-4D8B-9EF8-9CA88FC41D99@opencsw.org>
Message-ID: <510E97A3.4030408@opencsw.org>

Hi hope it's back :)

Greetings
Jan



Am 03.02.13 17:40, schrieb Dagobert Michelsen:
> Hi folks,
> 
> there is a problem with login.opencsw.org at the moment. Jan is looking at it
> and it will hopefully be back online soon.
> 
> 
> Best regards
> 
>  -- Dago
> _______________________________________________
> 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  Sun Feb  3 23:15:43 2013
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sun, 3 Feb 2013 22:15:43 +0000
Subject: [csw-maintainers] new packages mailing list
In-Reply-To: <x6a9rll5dd.fsf@opencsw.org>
References: <CAP30j15geGqj_Msn_9qT+6GMSASC6LRf5cVU368-s1EkOE+VTA@mail.gmail.com>
	<x6a9rll5dd.fsf@opencsw.org>
Message-ID: <CALtRa-48nFoS0GPAmQQXKX2kg=QvP2kd=967fSOKa0knjAEBQg@mail.gmail.com>

No dia 03/02/2013 17:39, "Peter FELECAN" <pfelecan at opencsw.org> escreveu:
>
> Ben Walton <bwalton at opencsw.org> writes:
>
> > I'm doing a bit of cleanup on the ruby code I use for atom feeds, etc
> > and noticed that I'd written but never activated a script to take an
> > atom feed and produce a weekly mail digest.  Is there interest in this
> > function still?  If so, which list should the mail be sent to?  I'll
> > send a single message per catalog with the weekly changes.
>
> users?

We used to have a dedicated mailing list for that, didn't we?

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

From dam at opencsw.org  Mon Feb  4 10:02:20 2013
From: dam at opencsw.org (Dagobert Michelsen)
Date: Mon, 4 Feb 2013 10:02:20 +0100
Subject: [csw-maintainers] Downtime for buildfarm this evening
Message-ID: <A2ACA150-1992-4D63-9C62-1593818D2F74@opencsw.org>

Hi folks,

as you may have noticed the buildfarm had some problems yesterday and we suspect
a missing patch which I would like to install this evening. The buildfarm will
not be available during this time.

Yann, while I am at it: I also got an IDR for the hanging ldd -r which I also would like
to install.


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 Feb  4 14:22:53 2013
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Mon, 4 Feb 2013 13:22:53 +0000
Subject: [csw-maintainers] Proposal: switch off autostarting of services
In-Reply-To: <CAP30j17FbS8mE=_HtAeBkVDa6=64v0VYQyf0j6-vB-A5JAx5uQ@mail.gmail.com>
References: <7a97dd2f5e692a537557871493fc735d@opencsw.org>
	<CAF2fwsccz6tAm8o5Qes4JOqW2UNygEGQHzA03AGnf7+E2V--Eg@mail.gmail.com>
	<CALtRa-7e0QODR+evKk3uP2jTJ1vsGMTzCzoq+Toxw9ttO+eqDg@mail.gmail.com>
	<CAF2fwsd4Ma_MbseH4o7-A_=OzMWUe7aPGuDRp1SUXNJ26SJg0Q@mail.gmail.com>
	<CALtRa-4FCmjwqU1CGbAYkfS6K1cPGVKk5-7u4-JMd6NaUwDSbw@mail.gmail.com>
	<CAP30j17FbS8mE=_HtAeBkVDa6=64v0VYQyf0j6-vB-A5JAx5uQ@mail.gmail.com>
Message-ID: <CALtRa-4D4ko9cMJ-kcn2sj+1frOr682W+NfE_+toDp4rb6J-pw@mail.gmail.com>

Let's pick this topic up again. We are in agreement to switch off
autostarting. Would anyone like to volunteer and make the change?

From jh at opencsw.org  Mon Feb  4 14:37:31 2013
From: jh at opencsw.org (Jan Holzhueter)
Date: Mon, 04 Feb 2013 14:37:31 +0100
Subject: [csw-maintainers] Downtime for buildfarm this evening
In-Reply-To: <A2ACA150-1992-4D63-9C62-1593818D2F74@opencsw.org>
References: <A2ACA150-1992-4D63-9C62-1593818D2F74@opencsw.org>
Message-ID: <510FB99B.7020705@opencsw.org>

Do to problems still happing on the farm I will reboot now.
Sorry for that.



Am 04.02.13 10:02, schrieb Dagobert Michelsen:
> Hi folks,
> 
> as you may have noticed the buildfarm had some problems yesterday and we suspect
> a missing patch which I would like to install this evening. The buildfarm will
> not be available during this time.
> 
> Yann, while I am at it: I also got an IDR for the hanging ldd -r which I also would like
> to install.
> 
> 
> Best regards
> 
>   -- Dago
> 


From dam at opencsw.org  Mon Feb  4 23:18:05 2013
From: dam at opencsw.org (Dagobert Michelsen)
Date: Mon, 4 Feb 2013 23:18:05 +0100
Subject: [csw-maintainers] Buildfarm still down
Message-ID: <96783266-1035-4FC6-B9C1-F5FC237BA6E1@opencsw.org>

Fellow maintainers,

the update of the buildfarm server was harder than expected and the patches are applied right now.
I will leave the patches running overnight and hopefully the machine will be available tomorrow
again.


Sorry for the inconvenience

  -- 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  Mon Feb  4 23:19:43 2013
From: dam at opencsw.org (Dagobert Michelsen)
Date: Mon, 4 Feb 2013 23:19:43 +0100
Subject: [csw-maintainers] [buildfarm-announce] The OpenCSW buildfarm is
	being patched
Message-ID: <BF0643D9-EE7B-4817-AA7E-42FE4EDCAEF5@opencsw.org>

Fellow OpenCSW buildfarm users,

the update of the buildfarm server was harder than expected and the patches
are still applying right now. I will leave the patches running overnight
and hopefully the machine will be available tomorrow again.


Sorry for the inconvenience

  -- 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

_______________________________________________
buildfarm-announce mailing list
buildfarm-announce at opencsw.org
https://lists.opencsw.org/mailman/listinfo/buildfarm-announce

From dam at opencsw.org  Tue Feb  5 14:11:13 2013
From: dam at opencsw.org (Dagobert Michelsen)
Date: Tue, 5 Feb 2013 14:11:13 +0100
Subject: [csw-maintainers] Buildfarm available again
Message-ID: <0E76B199-0C0A-4F04-A250-A646952027C7@opencsw.org>

Hi folks,

the buildfarm-update is finished. Please let me know if you encounter anything suspicious


Sorry for the inconvenience

  -- 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  Thu Feb  7 11:19:01 2013
From: dam at opencsw.org (Dagobert Michelsen)
Date: Thu, 7 Feb 2013 11:19:01 +0100
Subject: [csw-maintainers] Problem with Solaris 11 catalog
Message-ID: <A77684A5-C74E-44B1-9FB7-AE1820308D74@opencsw.org>

Hi folks,

I just wanted to install guile_dev which is in the Solaris 11 catalog, but the package
file is not there:

> => Fetching new catalog and descriptions (http://buildfarm.opencsw.org/opencsw-official/unstable/sparc/5.11) if available ...
> ==> 3599 packages loaded from /var/opt/csw/pkgutil/catalog.buildfarm.opencsw.org_opencsw-official_unstable_sparc_5.11
> Solving needed dependencies ...
> Solving dependency order ...
> 14 CURRENT packages:
>         CSWcas-texinfo-1.42,REV=2010.11.26
>         CSWcommon-1.5,REV=2010.12.11
>         CSWggettext-data-0.18.1.1,p,REV=2011.03.15
>         CSWiconv-1.14,REV=2011.08.08
>         CSWlibcharset1-1.14,REV=2011.08.07
>         CSWlibffi4-4.7.2,REV=2013.01.19
>         CSWlibgcc-s1-4.7.2,REV=2013.01.19
>         CSWlibgmp10-5.0.4,REV=2012.03.18
>         CSWlibiconv2-1.14,REV=2011.08.07
>         CSWlibintl8-0.18.1.1,p,REV=2011.03.15
>         CSWlibltdl7-2.4.2,REV=2012.04.26
>         CSWlibncurses5-5.9,REV=2011.11.21
>         CSWlibreadline6-6.2,REV=2011.07.02
>         CSWterminfo-5.9,REV=2011.11.21
> Install 6 NEW packages:
>         CSWguile-2.0.7,REV=2013.02.06 (opencsw-official/unstable)
>         CSWguile-dev-2.0.7,REV=2013.02.06 (opencsw-official/unstable)
>         CSWlibgc1-7.1,REV=2012.01.15 (opencsw-official/unstable)
>         CSWlibguile2-0-22-2.0.7,REV=2013.02.06 (opencsw-official/unstable)
>         CSWlibguilereadline-v18-18-2.0.7,REV=2013.02.06 (opencsw-official/unstable)
>         CSWlibunistring0-0.9.3,REV=2012.01.15 (opencsw-official/unstable)
> Total size: 5.5 MB
> => Fetching CSWlibunistring0-0.9.3,REV=2012.01.15 (1/6) ...
> => Fetching CSWlibgc1-7.1,REV=2012.01.15 (2/6) ...
> => Fetching CSWlibguile2-0-22-2.0.7,REV=2013.02.06 (3/6) ...
> --2013-02-07 11:14:19--  http://buildfarm.opencsw.org/opencsw-official/unstable/sparc/5.11/libguile2_0_22-2.0.7,REV=2013.02.06-SunOS5.10-sparc-CSW.pkg.gz
> Resolving proxy (proxy)... 192.168.1.6
> Connecting to proxy (proxy)|192.168.1.6|:3128... connected.
> Proxy request sent, awaiting response... 404 Not Found
> 2013-02-07 11:14:19 ERROR 404: Not Found.
> 


Maybe someone has an idea why this happened?


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 jh at opencsw.org  Thu Feb  7 12:47:25 2013
From: jh at opencsw.org (Jan Holzhueter)
Date: Thu, 07 Feb 2013 12:47:25 +0100
Subject: [csw-maintainers] Buildfarm just crashed
In-Reply-To: <0E76B199-0C0A-4F04-A250-A646952027C7@opencsw.org>
References: <0E76B199-0C0A-4F04-A250-A646952027C7@opencsw.org>
Message-ID: <5113944D.5020403@opencsw.org>

Hi,
it just crashed. No clue why yet but working on getting it back.

Greetings
Jan



Am 05.02.13 14:11, schrieb Dagobert Michelsen:
> Hi folks,
> 
> the buildfarm-update is finished. Please let me know if you encounter anything suspicious
> 
> 
> Sorry for the inconvenience
> 
>   -- Dago
> 


From jh at opencsw.org  Thu Feb  7 15:36:33 2013
From: jh at opencsw.org (Jan Holzhueter)
Date: Thu, 07 Feb 2013 15:36:33 +0100
Subject: [csw-maintainers] Buildfarm just crashed
In-Reply-To: <5113944D.5020403@opencsw.org>
References: <0E76B199-0C0A-4F04-A250-A646952027C7@opencsw.org>
	<5113944D.5020403@opencsw.org>
Message-ID: <5113BBF1.7020701@opencsw.org>

Hi,
ok we are back up. I hope for longer time :)

Greetings
Jan



Am 07.02.13 12:47, schrieb Jan Holzhueter:
> Hi,
> it just crashed. No clue why yet but working on getting it back.
> 
> Greetings
> Jan
> 
> 
> 
> Am 05.02.13 14:11, schrieb Dagobert Michelsen:
>> Hi folks,
>>
>> the buildfarm-update is finished. Please let me know if you encounter anything suspicious
>>
>>
>> Sorry for the inconvenience
>>
>>   -- Dago
>>
> 
> _______________________________________________
> 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  Fri Feb  8 11:09:39 2013
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Fri, 8 Feb 2013 10:09:39 +0000
Subject: [csw-maintainers] Problem with Solaris 11 catalog
In-Reply-To: <A77684A5-C74E-44B1-9FB7-AE1820308D74@opencsw.org>
References: <A77684A5-C74E-44B1-9FB7-AE1820308D74@opencsw.org>
Message-ID: <CALtRa-4T+RyHguNH0prfZ9VYSo0KGn-X+AC3_=_57Jawtz+qZw@mail.gmail.com>

2013/2/7 Dagobert Michelsen <dam at opencsw.org>
>
> > --2013-02-07 11:14:19--  http://buildfarm.opencsw.org/opencsw-official/unstable/sparc/5.11/libguile2_0_22-2.0.7,REV=2013.02.06-SunOS5.10-sparc-CSW.pkg.gz
> > Resolving proxy (proxy)... 192.168.1.6
> > Connecting to proxy (proxy)|192.168.1.6|:3128... connected.
> > Proxy request sent, awaiting response... 404 Not Found
> > 2013-02-07 11:14:19 ERROR 404: Not Found.
> >
>
> Maybe someone has an idea why this happened?

I briefly looked at it, and initially thought that it could be a race
condition between uploading a package and generating the catalog. But
it looks like it's not that, because the race condition problem goes
away upon next catalog generation. First thing to check: is the
catalog generation currently succeeding or failing at some point?

Maciej

From dam at opencsw.org  Fri Feb  8 13:28:38 2013
From: dam at opencsw.org (Dagobert Michelsen)
Date: Fri, 8 Feb 2013 13:28:38 +0100
Subject: [csw-maintainers] Problem with Solaris 11 catalog
In-Reply-To: <CALtRa-4T+RyHguNH0prfZ9VYSo0KGn-X+AC3_=_57Jawtz+qZw@mail.gmail.com>
References: <A77684A5-C74E-44B1-9FB7-AE1820308D74@opencsw.org>
	<CALtRa-4T+RyHguNH0prfZ9VYSo0KGn-X+AC3_=_57Jawtz+qZw@mail.gmail.com>
Message-ID: <D3080E2E-E3E3-40F1-949A-9B20774F76B6@opencsw.org>

Hi Maciej,

Am 08.02.2013 um 11:09 schrieb Maciej (Matchek) Blizi?ski <maciej at opencsw.org>:
> 2013/2/7 Dagobert Michelsen <dam at opencsw.org>
>> 
>>> --2013-02-07 11:14:19--  http://buildfarm.opencsw.org/opencsw-official/unstable/sparc/5.11/libguile2_0_22-2.0.7,REV=2013.02.06-SunOS5.10-sparc-CSW.pkg.gz
>>> Resolving proxy (proxy)... 192.168.1.6
>>> Connecting to proxy (proxy)|192.168.1.6|:3128... connected.
>>> Proxy request sent, awaiting response... 404 Not Found
>>> 2013-02-07 11:14:19 ERROR 404: Not Found.
>>> 
>> 
>> Maybe someone has an idea why this happened?
> 
> I briefly looked at it, and initially thought that it could be a race
> condition between uploading a package and generating the catalog. But
> it looks like it's not that, because the race condition problem goes
> away upon next catalog generation. First thing to check: is the
> catalog generation currently succeeding or failing at some point?

Indeed, there was a stale lock probable left after the buildfarm going down.
I made the locking more robust and cleanup stale locks:
  http://opencsw.svn.sourceforge.net/viewvc/opencsw/buildfarm/bin/opencsw-future-update?r1=649&r2=648&pathrev=649


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 jh at opencsw.org  Sat Feb  9 10:09:38 2013
From: jh at opencsw.org (Jan Holzhueter)
Date: Sat, 09 Feb 2013 10:09:38 +0100
Subject: [csw-maintainers] Buildfarm exploded again.
Message-ID: <51161252.5050603@opencsw.org>

Hi,
the buildfarm died again.
Sorry for that.
I hope we can fix it soon.

Greetings
Jan


From dam at opencsw.org  Sat Feb  9 10:17:55 2013
From: dam at opencsw.org (Dagobert Michelsen)
Date: Sat, 9 Feb 2013 10:17:55 +0100
Subject: [csw-maintainers] Buildfarm crashed again
Message-ID: <545485AC-69CB-45B0-921B-54316C67E9BD@opencsw.org>

Hi folks,

the buildfarm crashed again. I am looking into it and I can also tell
you that I am pretty unhappy with the present situation given that
one of disks from the mirrored main pool died and the server crashed
while sending over the data.


Best regards

  -- Dago

From dam at opencsw.org  Sat Feb  9 10:31:01 2013
From: dam at opencsw.org (Dagobert Michelsen)
Date: Sat, 9 Feb 2013 10:31:01 +0100
Subject: [csw-maintainers] Buildfarm crashed again
In-Reply-To: <545485AC-69CB-45B0-921B-54316C67E9BD@opencsw.org>
References: <545485AC-69CB-45B0-921B-54316C67E9BD@opencsw.org>
Message-ID: <D375AECB-6AD9-456E-914E-415BC85DF15C@opencsw.org>

Hi folks,

Am 09.02.2013 um 10:17 schrieb Dagobert Michelsen:
> the buildfarm crashed again. I am looking into it and I can also tell
> you that I am pretty unhappy with the present situation given that
> one of disks from the mirrored main pool died and the server crashed
> while sending over the data.

The farm is running again, I got a crashdump this time indicating an ZFS issue.
@Ben, Maciej: Would you be so kind starting the signing again?


Best regards

  -- Dago

From opk at opencsw.org  Tue Feb 12 11:36:34 2013
From: opk at opencsw.org (Oliver Kiddle)
Date: Tue, 12 Feb 2013 11:36:34 +0100
Subject: [csw-maintainers] working on guile
In-Reply-To: <9b9e0e385db249df40c6e0b7d114456c@opencsw.org>
References: <9b9e0e385db249df40c6e0b7d114456c@opencsw.org>
Message-ID: <30408.1360665394@thecus.kiddle.eu>

On 9 Jan, pfelecan wrote:
> I started an upgrade work on guile 
> http://www.opencsw.org/packages/CSWguile/ on a specific branch: 2.0.7
> 
> The results are quite promising.
> 
> If there are people who worked on it I welcome their suggestions, 
> hints, comments, &c

I don't know if this is too late for you but I tried building 2.0.6 a little
while back and needed a couple of tweaks. The patch below is one of them. I
also needed an extra cc option. I may not remember correctly but it was perhaps
-features=extensions.

Oliver

diff -ur guile-2.0.6-attempt/libguile/gc.h guile-2.0.6/libguile/gc.h
--- guile-2.0.6-attempt/libguile/gc.h   Fri Nov  2 14:04:38 2012
+++ guile-2.0.6/libguile/gc.h   Mon Jul  2 11:28:13 2012
@@ -240,10 +240,6 @@
   return cell;
 }
 
-SCM_API void scm_remember_upto_here_1 (SCM obj);
-SCM_API void scm_remember_upto_here_2 (SCM obj1, SCM obj2);
-SCM_API void scm_remember_upto_here (SCM obj1, ...);
-
 SCM_INLINE_IMPLEMENTATION SCM
 scm_double_cell (scm_t_bits car, scm_t_bits cbr,
                 scm_t_bits ccr, scm_t_bits cdr)
@@ -319,6 +315,10 @@
 
 #endif /* SCM_CAN_INLINE || defined SCM_INLINE_C_IMPLEMENTING_INLINES */
 
+SCM_API void scm_remember_upto_here_1 (SCM obj);
+SCM_API void scm_remember_upto_here_2 (SCM obj1, SCM obj2);
+SCM_API void scm_remember_upto_here (SCM obj1, ...);
+
 /* In GCC we can force a reference to an SCM by making it an input to an
    empty asm.  This avoids the code size and slowdown of an actual function
    call.  Unfortunately there doesn't seem to be any way to do the varargs

From pfelecan at opencsw.org  Tue Feb 12 14:24:13 2013
From: pfelecan at opencsw.org (pfelecan)
Date: Tue, 12 Feb 2013 14:24:13 +0100
Subject: [csw-maintainers] mgar merge: pcopy doesn't preserve files epoch;
	it should...
Message-ID: <11d50187be59fb87e3cbfd4eea47bcaa@opencsw.org>

When using guile in autotools, the detection of its version fails
because the logic of the test is based on filtering the output of
guile-config and when the supplied Scheme scripts are newer than the
pre-compiled ones we get a warning on the same file handle, e.g.:

;;; note: source file /opt/csw/share/guile/2.0/ice-9/eval.scm
;;;       newer than compiled 
/opt/csw/lib/guile/2.0/ccache/ice-9/eval.go
guile-config - Guile version 2.0.7

Thus, the test fails. I agree that the logic of the test is flaky
but this is not the point.

Looking up the incriminated files epoch I can see:

cd ~/opencsw/guile/trunk/work/solaris10-sparc

gls -l --time-style=+%s
pkgroot/opt/csw/share/guile/2.0/ice-9/eval.scm \
   
work/solaris10-sparc/pkgroot/opt/csw/lib/guile/2.0/ccache/ice-9/eval.go
-rw-r--r-- 1 pfelecan csw 13506 1360592755 
pkgroot/opt/csw/lib/guile/2.0/ccache/ice-9/eval.go
-rw-r--r-- 1 pfelecan csw 20920 1360592757 
pkgroot/opt/csw/share/guile/2.0/ice-9/eval.scm

and

gls -l --time-style=+%s 
install-isa-sparcv8plus/opt/csw/share/guile/2.0/ice-9/eval.scm 
work/solaris10-sparc/install-isa-sparcv8plus/opt/csw/lib/guile/2.0/ccache/ice-9/eval.go
-rw-r--r-- 1 pfelecan csw 13506 1360592531 
install-isa-sparcv8plus/opt/csw/lib/guile/2.0/ccache/ice-9/eval.go
-rw-r--r-- 1 pfelecan csw 20920 1360592494 
install-isa-sparcv8plus/opt/csw/share/guile/2.0/ice-9/eval.scm

This means that the epoch is changed when merging; i.e. when pcopy
transfers the files from the installation directory to the packaging
directory.

In my opinion, this is sub-optimal. Can we replace the pcopy with
the good old GNU tar, which have all the required features to
obtain the same effect or modify the copy routine (now provided by
File::Copy module) to preserve all the inode's attributes?

I understand that I can supply a kludgy post-install script which
either compiles the Scheme scripts or recursively touch the
pre-compiled files on the target system to avoid the unwanted
behavior of guile-config. However, this is not what I want /
is required.


From dam at opencsw.org  Tue Feb 12 14:57:13 2013
From: dam at opencsw.org (Dagobert Michelsen)
Date: Tue, 12 Feb 2013 14:57:13 +0100
Subject: [csw-maintainers] mgar merge: pcopy doesn't preserve files
	epoch; it should...
In-Reply-To: <11d50187be59fb87e3cbfd4eea47bcaa@opencsw.org>
References: <11d50187be59fb87e3cbfd4eea47bcaa@opencsw.org>
Message-ID: <14324416-90CD-456F-BEEC-2DB33C133274@opencsw.org>

Hi Peter,

Am 12.02.2013 um 14:24 schrieb pfelecan <pfelecan at opencsw.org>:
> Looking up the incriminated files epoch I can see:
> 
> cd ~/opencsw/guile/trunk/work/solaris10-sparc
> 
> gls -l --time-style=+%s
> pkgroot/opt/csw/share/guile/2.0/ice-9/eval.scm \
>  work/solaris10-sparc/pkgroot/opt/csw/lib/guile/2.0/ccache/ice-9/eval.go
> -rw-r--r-- 1 pfelecan csw 13506 1360592755 pkgroot/opt/csw/lib/guile/2.0/ccache/ice-9/eval.go
> -rw-r--r-- 1 pfelecan csw 20920 1360592757 pkgroot/opt/csw/share/guile/2.0/ice-9/eval.scm
> 
> and
> 
> gls -l --time-style=+%s install-isa-sparcv8plus/opt/csw/share/guile/2.0/ice-9/eval.scm work/solaris10-sparc/install-isa-sparcv8plus/opt/csw/lib/guile/2.0/ccache/ice-9/eval.go
> -rw-r--r-- 1 pfelecan csw 13506 1360592531 install-isa-sparcv8plus/opt/csw/lib/guile/2.0/ccache/ice-9/eval.go
> -rw-r--r-- 1 pfelecan csw 20920 1360592494 install-isa-sparcv8plus/opt/csw/share/guile/2.0/ice-9/eval.scm
> 
> This means that the epoch is changed when merging; i.e. when pcopy
> transfers the files from the installation directory to the packaging
> directory.
> 
> In my opinion, this is sub-optimal. Can we replace the pcopy with
> the good old GNU tar, which have all the required features to
> obtain the same effect or modify the copy routine (now provided by
> File::Copy module) to preserve all the inode's attributes?

Unfortunately not as pcopy does relocation on the fly much like pax,
but that has ugly bugs under certain conditions so I decided to rewrite it.

> I understand that I can supply a kludgy post-install script which
> either compiles the Scheme scripts or recursively touch the
> pre-compiled files on the target system to avoid the unwanted
> behavior of guile-config. However, this is not what I want /
> is required.


This is definitely not good. I changed pcopy to keep the mtime and atime:
  http://sourceforge.net/apps/trac/gar/changeset/20300


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 pfelecan at opencsw.org  Tue Feb 12 19:02:35 2013
From: pfelecan at opencsw.org (Peter FELECAN)
Date: Tue, 12 Feb 2013 19:02:35 +0100
Subject: [csw-maintainers] mgar merge: pcopy doesn't preserve files
	epoch; it should...
In-Reply-To: <14324416-90CD-456F-BEEC-2DB33C133274@opencsw.org> (Dagobert
	Michelsen's message of "Tue, 12 Feb 2013 14:57:13 +0100")
References: <11d50187be59fb87e3cbfd4eea47bcaa@opencsw.org>
	<14324416-90CD-456F-BEEC-2DB33C133274@opencsw.org>
Message-ID: <x6y5eth0lg.fsf@opencsw.org>

Dagobert Michelsen <dam at opencsw.org> writes:

> This is definitely not good. I changed pcopy to keep the mtime and atime:
>   http://sourceforge.net/apps/trac/gar/changeset/20300

You correction solves the issue. Thank you.
-- 
Peter

From maciej at opencsw.org  Wed Feb 13 14:06:29 2013
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Wed, 13 Feb 2013 13:06:29 +0000
Subject: [csw-maintainers] http://www.opencsw.org/community/questions/
In-Reply-To: <C10CE01A-E9EC-4D20-8EE0-860F60E96D90@opencsw.org>
References: <510D3150.3090500@apt-get.be>
	<CALtRa-5AC+hGQbj+Vbi2MF146t0FD688RHqqMQJO-gpmR4bV9Q@mail.gmail.com>
	<CALtRa-6XgVqbi+mL9xCSDap8a_SuYX7kX__qqBC2EO+LkiKKuA@mail.gmail.com>
	<C10CE01A-E9EC-4D20-8EE0-860F60E96D90@opencsw.org>
Message-ID: <CALtRa-5jeiy4ROt34U5scBjZv+LwhFXZs2jL5akCggoZNe0ksg@mail.gmail.com>

Dear maintainers,

Our OSQA-powered site, http://www.opencsw.org/community/ is getting spammed
and is not getting any user input. OSQA itself doesn't have good facilities
for fighting spam. For example, to get rid of harmful links from spam
profiles, we need to run SQL queries by hand (thanks go to Dago for doing
it recently).

2013/2/2 Dagobert Michelsen <dam at opencsw.org>

> We have spam from time to time and I usually just delete it. It may
> probably
> be best to just enable moderation on new accounts if possible.
>

People / users are not registering there and not asking questions via OSQA.
We have roughly these choices:

1. Close /community/ and copy existing content into a static page (on
wordpress) or wiki, or some other place (the manual?). Create a HTTP
redirect from /community/.*
2. Try harder: Upgrade OSQA to the newest version (trunk from upstream svn)
and start promoting the site so maybe people will start registering.
3. (credit goes to Trygve) Use the "opencsw" tag in serverfault.com. Try to
create a link to a form with the tag prefilled. Then subscribe to
unanswered questions with the tag. An example:
http://serverfault.com/unanswered/tagged/solaris - also via RSS:
http://serverfault.com/feeds/tag/solaris

Thoughts?

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

From maciej at opencsw.org  Wed Feb 13 17:27:31 2013
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Wed, 13 Feb 2013 16:27:31 +0000
Subject: [csw-maintainers] mgar on login - disable?
Message-ID: <CALtRa-6gMVSEGUvrAP9SC-mFurmKwcPBcfPNSvKn+VMnN1OXEg@mail.gmail.com>

Do we ever want or need to run mgar on login? If we don't, maybe we should
make mgar refuse to run on login, because it's tripping new people up.

For example: http://pastie.org/6153160

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

From pfelecan at opencsw.org  Wed Feb 13 19:03:16 2013
From: pfelecan at opencsw.org (Peter FELECAN)
Date: Wed, 13 Feb 2013 19:03:16 +0100
Subject: [csw-maintainers] mgar on login - disable?
In-Reply-To: <CALtRa-6gMVSEGUvrAP9SC-mFurmKwcPBcfPNSvKn+VMnN1OXEg@mail.gmail.com>
	("Maciej (Matchek) =?utf-8?Q?Blizi=C5=84ski=22's?= message of "Wed,
	13 Feb 2013 16:27:31 +0000")
References: <CALtRa-6gMVSEGUvrAP9SC-mFurmKwcPBcfPNSvKn+VMnN1OXEg@mail.gmail.com>
Message-ID: <x6ip5wgkgr.fsf@opencsw.org>

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

> Do we ever want or need to run mgar on login? If we don't, maybe we should
> make mgar refuse to run on login, because it's tripping new people up.

refuse++
-- 
Peter

From dam at opencsw.org  Wed Feb 13 19:23:46 2013
From: dam at opencsw.org (Dagobert Michelsen)
Date: Wed, 13 Feb 2013 19:23:46 +0100
Subject: [csw-maintainers] mgar on login - disable?
In-Reply-To: <CALtRa-6gMVSEGUvrAP9SC-mFurmKwcPBcfPNSvKn+VMnN1OXEg@mail.gmail.com>
References: <CALtRa-6gMVSEGUvrAP9SC-mFurmKwcPBcfPNSvKn+VMnN1OXEg@mail.gmail.com>
Message-ID: <E7952140-6820-4D41-9078-1C2B5C22F7D8@opencsw.org>

Hi Maciej,

Am 13.02.2013 um 17:27 schrieb Maciej (Matchek) Blizi?ski <maciej at opencsw.org>:
> Do we ever want or need to run mgar on login? If we don't, maybe we should make mgar refuse to run on login, because it's tripping new people up.
> 
> For example: http://pastie.org/6153160

This is because it uses /usr/bin/env python pulling in /usr/bin/python before /opt/csw/bin/python in
addition to not checking the presence of mako.

> dam at login [login]:/home/dam > PATH=/opt/csw/bin:$PATH mgar newpkg test2
> Creating package skeleton for test2 X.Y.
> A         test2
> A         test2/trunk
> A         test2/trunk/files
> A         test2/branches
> A         test2/tags
> A         test2/Makefile
> A         test2/trunk/Makefile
> A         test2/trunk/checksums
> Eigenschaft ?svn:keywords? f?r ?test2/trunk/Makefile? gesetzt
> Eigenschaft ?svn:ignore? f?r ?test2/trunk? gesetzt
> 
> Created successfully at /home/dam/mgar/pkg/test2/trunk
> 
> dam at login [login]:/home/dam > 

I again suggest prefering /opt/csw/bin/python.


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 Feb 13 20:01:42 2013
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Wed, 13 Feb 2013 19:01:42 +0000
Subject: [csw-maintainers] mgar on login - disable?
In-Reply-To: <E7952140-6820-4D41-9078-1C2B5C22F7D8@opencsw.org>
References: <CALtRa-6gMVSEGUvrAP9SC-mFurmKwcPBcfPNSvKn+VMnN1OXEg@mail.gmail.com>
	<E7952140-6820-4D41-9078-1C2B5C22F7D8@opencsw.org>
Message-ID: <CALtRa-5FiqWgaOwNdBSbzRXTM7jag6cneCL4cPookp3ceMAVwg@mail.gmail.com>

2013/2/13 Dagobert Michelsen <dam at opencsw.org>

> I again suggest prefering /opt/csw/bin/python.


We can do both things. If you run mgar newpkg and it succeeds, you'll think
that other commands will too. If mgar refuses to run right at the start,
you'll ssh to a build machine and work there.

The only thing that you maybe could do from login is 'mgar platforms' and
'mgar replatforms'.

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

From claudio at opencsw.org  Wed Feb 13 20:08:19 2013
From: claudio at opencsw.org (Claudio)
Date: Wed, 13 Feb 2013 20:08:19 +0100
Subject: [csw-maintainers] mgar on login - disable?
In-Reply-To: <CALtRa-5FiqWgaOwNdBSbzRXTM7jag6cneCL4cPookp3ceMAVwg@mail.gmail.com>
References: <CALtRa-6gMVSEGUvrAP9SC-mFurmKwcPBcfPNSvKn+VMnN1OXEg@mail.gmail.com>
	<E7952140-6820-4D41-9078-1C2B5C22F7D8@opencsw.org>
	<CALtRa-5FiqWgaOwNdBSbzRXTM7jag6cneCL4cPookp3ceMAVwg@mail.gmail.com>
Message-ID: <CAJ2-jQ=R5_q8HQzQ9TYL_2OwCWyr5kVdOHp8xuCrgAEPBKJO5g@mail.gmail.com>

On Wed, Feb 13, 2013 at 8:01 PM, Maciej (Matchek) Blizi?ski <
maciej at opencsw.org> wrote:

>
> The only thing that you maybe could do from login is 'mgar platforms' and
> 'mgar replatforms'.
>
>
Wouldn't this be confusing?

C.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20130213/7a42d696/attachment.html>

From maciej at opencsw.org  Wed Feb 13 21:54:48 2013
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Wed, 13 Feb 2013 20:54:48 +0000
Subject: [csw-maintainers] mgar on login - disable?
In-Reply-To: <CAJ2-jQ=R5_q8HQzQ9TYL_2OwCWyr5kVdOHp8xuCrgAEPBKJO5g@mail.gmail.com>
References: <CALtRa-6gMVSEGUvrAP9SC-mFurmKwcPBcfPNSvKn+VMnN1OXEg@mail.gmail.com>
	<E7952140-6820-4D41-9078-1C2B5C22F7D8@opencsw.org>
	<CALtRa-5FiqWgaOwNdBSbzRXTM7jag6cneCL4cPookp3ceMAVwg@mail.gmail.com>
	<CAJ2-jQ=R5_q8HQzQ9TYL_2OwCWyr5kVdOHp8xuCrgAEPBKJO5g@mail.gmail.com>
Message-ID: <CALtRa-5Aq=ME34KZOEnE4T5YEZJdDATeQ09S9TJ_FVejfWqyjw@mail.gmail.com>

2013/2/13 Claudio <claudio at opencsw.org>:
> On Wed, Feb 13, 2013 at 8:01 PM, Maciej (Matchek) Blizi?ski
> <maciej at opencsw.org> wrote:
>>
>>
>> The only thing that you maybe could do from login is 'mgar platforms' and
>> 'mgar replatforms'.
>
> Wouldn't this be confusing?

It could be, but not if you know the buildfarm well. I think there's
no harm in disabling it on login altogether. Maybe simply
uninstalling?

From dam at opencsw.org  Wed Feb 13 22:25:23 2013
From: dam at opencsw.org (Dagobert Michelsen)
Date: Wed, 13 Feb 2013 22:25:23 +0100
Subject: [csw-maintainers] http://www.opencsw.org/community/questions/
In-Reply-To: <CALtRa-5jeiy4ROt34U5scBjZv+LwhFXZs2jL5akCggoZNe0ksg@mail.gmail.com>
References: <510D3150.3090500@apt-get.be>
	<CALtRa-5AC+hGQbj+Vbi2MF146t0FD688RHqqMQJO-gpmR4bV9Q@mail.gmail.com>
	<CALtRa-6XgVqbi+mL9xCSDap8a_SuYX7kX__qqBC2EO+LkiKKuA@mail.gmail.com>
	<C10CE01A-E9EC-4D20-8EE0-860F60E96D90@opencsw.org>
	<CALtRa-5jeiy4ROt34U5scBjZv+LwhFXZs2jL5akCggoZNe0ksg@mail.gmail.com>
Message-ID: <D413E32F-6C22-4BB3-B87E-10C7CABFCF1E@opencsw.org>

Hi Maciej,

Am 13.02.2013 um 14:06 schrieb Maciej (Matchek) Blizi?ski <maciej at opencsw.org>:
> Our OSQA-powered site, http://www.opencsw.org/community/ is getting spammed and is not getting any user input. OSQA itself doesn't have good facilities for fighting spam. For example, to get rid of harmful links from spam profiles, we need to run SQL queries by hand (thanks go to Dago for doing it recently).
> 
> 2013/2/2 Dagobert Michelsen <dam at opencsw.org>
> We have spam from time to time and I usually just delete it. It may probably
> be best to just enable moderation on new accounts if possible.
>  
> People / users are not registering there and not asking questions via OSQA. We have roughly these choices:
> 
> 1. Close /community/ and copy existing content into a static page (on wordpress) or wiki, or some other place (the manual?). Create a HTTP redirect from /community/.*
> 2. Try harder: Upgrade OSQA to the newest version (trunk from upstream svn) and start promoting the site so maybe people will start registering.
> 3. (credit goes to Trygve) Use the "opencsw" tag in serverfault.com. Try to create a link to a form with the tag prefilled. Then subscribe to unanswered questions with the tag. An example: http://serverfault.com/unanswered/tagged/solaris - also via RSS: http://serverfault.com/feeds/tag/solaris

4. Ban yahoo and hotmail users as they match 100% of the spam producers.


Best regards

  -- Dago

> 
> Thoughts?
> 
> Maciej
> _______________________________________________
> maintainers mailing list
> maintainers at lists.opencsw.org
> https://lists.opencsw.org/mailman/listinfo/maintainers
> .:: This mailing list's archive is public. ::.

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

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

From maciej at opencsw.org  Wed Feb 13 22:31:33 2013
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Wed, 13 Feb 2013 21:31:33 +0000
Subject: [csw-maintainers] Promoting dublin to stable
Message-ID: <CALtRa-4HSiX+rC+1YKcCWhfWPWzFZ9L6FSySTKbFUWu0sD4FwQ@mail.gmail.com>

I hope that there aren't many users left who are using the legacy release
from 2008. Unfortunately, I don't have any data - maybe there are, maybe
there aren't. I don't think we have a way to know, so we need to
arbitrarily set a date when we'll make 'dublin' the stable release and
'kiel' the testing release. Any suggestions or ideas? How much more time do
we need to give people to notice? I was thinking about for example the
beginning of May.

Thoughts?

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

From dam at opencsw.org  Wed Feb 13 22:46:35 2013
From: dam at opencsw.org (Dagobert Michelsen)
Date: Wed, 13 Feb 2013 22:46:35 +0100
Subject: [csw-maintainers] Promoting dublin to stable
In-Reply-To: <CALtRa-4HSiX+rC+1YKcCWhfWPWzFZ9L6FSySTKbFUWu0sD4FwQ@mail.gmail.com>
References: <CALtRa-4HSiX+rC+1YKcCWhfWPWzFZ9L6FSySTKbFUWu0sD4FwQ@mail.gmail.com>
Message-ID: <D064E302-5806-464B-884A-8F1A6C0F83C0@opencsw.org>

Hi Maciej,

Am 13.02.2013 um 22:31 schrieb Maciej (Matchek) Blizi?ski <maciej at opencsw.org>:
> I hope that there aren't many users left who are using the legacy release from 2008. Unfortunately, I don't have any data - maybe there are, maybe there aren't. I don't think we have a way to know, so we need to arbitrarily set a date when we'll make 'dublin' the stable release and 'kiel' the testing release. Any suggestions or ideas? How much more time do we need to give people to notice? I was thinking about for example the beginning of May.

I suggest announcing it on all channels and then change a few days later.


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  Wed Feb 13 22:48:27 2013
From: dam at opencsw.org (Dagobert Michelsen)
Date: Wed, 13 Feb 2013 22:48:27 +0100
Subject: [csw-maintainers] mgar on login - disable?
In-Reply-To: <CALtRa-5Aq=ME34KZOEnE4T5YEZJdDATeQ09S9TJ_FVejfWqyjw@mail.gmail.com>
References: <CALtRa-6gMVSEGUvrAP9SC-mFurmKwcPBcfPNSvKn+VMnN1OXEg@mail.gmail.com>
	<E7952140-6820-4D41-9078-1C2B5C22F7D8@opencsw.org>
	<CALtRa-5FiqWgaOwNdBSbzRXTM7jag6cneCL4cPookp3ceMAVwg@mail.gmail.com>
	<CAJ2-jQ=R5_q8HQzQ9TYL_2OwCWyr5kVdOHp8xuCrgAEPBKJO5g@mail.gmail.com>
	<CALtRa-5Aq=ME34KZOEnE4T5YEZJdDATeQ09S9TJ_FVejfWqyjw@mail.gmail.com>
Message-ID: <B531CA29-60F7-4606-9B21-27E7E2999D71@opencsw.org>

Hi,

Am 13.02.2013 um 21:54 schrieb Maciej (Matchek) Blizi?ski <maciej at opencsw.org>:
> 2013/2/13 Claudio <claudio at opencsw.org>:
>> On Wed, Feb 13, 2013 at 8:01 PM, Maciej (Matchek) Blizi?ski
>> <maciej at opencsw.org> wrote:
>>> The only thing that you maybe could do from login is 'mgar platforms' and
>>> 'mgar replatforms'.
>> 
>> Wouldn't this be confusing?
> 
> It could be, but not if you know the buildfarm well. I think there's
> no harm in disabling it on login altogether. Maybe simply
> uninstalling?

Package deleted.


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 pfelecan at opencsw.org  Thu Feb 14 10:02:00 2013
From: pfelecan at opencsw.org (pfelecan)
Date: Thu, 14 Feb 2013 10:02:00 +0100
Subject: [csw-maintainers] mgar: platforms-repackage output
Message-ID: <ff2266632bd219499202191bcdeca1ab@opencsw.org>

When I "platforms-repackage", the output is misleading, only the names 
of the packages generated for one architecture and "all" are printed 
out:

$ mgar platforms-remerge platforms-repackage
[...]
   CSWautogen           
/home/pfelecan/staging/build-14.Feb.2013/autogen-5.17.1,REV=2013.02.14-SunOS5.10-i386-CSW.pkg.gz
   CSWautogen-dev       
/home/pfelecan/staging/build-14.Feb.2013/autogen_dev-5.17.1,REV=2013.02.14-SunOS5.10-all-CSW.pkg.gz
   CSWautogen-doc       
/home/pfelecan/staging/build-14.Feb.2013/autogen_doc-5.17.1,REV=2013.02.14-SunOS5.10-all-CSW.pkg.gz
   CSWautogendoc        
/home/pfelecan/staging/build-14.Feb.2013/autogen_doc_stub-5.17.1,REV=2013.02.14-SunOS5.10-all-CSW.pkg.gz
   CSWautogenrt         
/home/pfelecan/staging/build-14.Feb.2013/autogenrt_stub-5.17.1,REV=2013.02.14-SunOS5.10-all-CSW.pkg.gz
   CSWlibopts25         
/home/pfelecan/staging/build-14.Feb.2013/libopts25-5.17.1,REV=2013.02.14-SunOS5.10-i386-CSW.pkg.gz

but in the stagging directory we have:

autogen-5.17.1,REV=2013.02.14-SunOS5.10-i386-CSW.pkg.gz
autogen-5.17.1,REV=2013.02.14-SunOS5.10-sparc-CSW.pkg.gz
autogen_dev-5.17.1,REV=2013.02.14-SunOS5.10-all-CSW.pkg.gz
autogen_doc-5.17.1,REV=2013.02.14-SunOS5.10-all-CSW.pkg.gz
autogen_doc_stub-5.17.1,REV=2013.02.14-SunOS5.10-all-CSW.pkg.gz
autogenrt_stub-5.17.1,REV=2013.02.14-SunOS5.10-all-CSW.pkg.gz
libopts25-5.17.1,REV=2013.02.14-SunOS5.10-i386-CSW.pkg.gz
libopts25-5.17.1,REV=2013.02.14-SunOS5.10-sparc-CSW.pkg.gz

all this is done from unstable10s


From pfelecan at opencsw.org  Thu Feb 14 10:43:37 2013
From: pfelecan at opencsw.org (pfelecan)
Date: Thu, 14 Feb 2013 10:43:37 +0100
Subject: [csw-maintainers] checkpkg signals a misterious dependency for
	TeXLive and it's right
Message-ID: <fb79243fbd8ae8bf0095ab4289845972@opencsw.org>

TeXLive has many packages. One of them is
texlive_latex_extra_binaries, which contains architecturally
dependent files and some symbolic links toward them; the
texlive_common is a package containing only architecturally
neutral files and is the result of the "reminder" files, i.e.,
everything not in specific packages is in it...

However, I get:

RUNTIME_DEP_PKGS_CSWtexlive-common += CSWtexlive-latex-extra-binaries
If any of the reported errors were false positives, you can override 
them
pasting the lines below to the GAR recipe.
CHECKPKG_OVERRIDES_CSWtexlive-common += 
missing-dependency|CSWtexlive-latex-extra-binaries

Dependency issues of CSWtexlive-common:
CSWtexlive-latex-extra-binaries is needed by CSWtexlive-common, 
because:
- symlink contains a CSWtexlive-common (u'/opt/csw/bin/bg5+latex') 
which
needs the target file: '/opt/csw/bin/gbklatex'.
- symlink contains a CSWtexlive-common (u'/opt/csw/bin/bg5+pdflatex')
which needs the target file: '/opt/csw/bin/gbkpdflatex'.
RUNTIME_DEP_PKGS_CSWtexlive-common += CSWtexlive-latex-extra-binaries

But the incriminated files are all part of the
texlive_latex_extra_binaries:

PKGFILES_CSWtexlive-latex-extra-binaries		+=	/opt/csw/bin/bg5+latex
PKGFILES_CSWtexlive-latex-extra-binaries		+=	/opt/csw/bin/bg5+pdflatex
PKGFILES_CSWtexlive-latex-extra-binaries		+=	/opt/csw/bin/gbklatex
PKGFILES_CSWtexlive-latex-extra-binaries		+=	/opt/csw/bin/gbkpdflatex

Effectively, we have in the texlive_comon prototype:

s none /opt/csw/bin/bg5+latex=gbklatex
s none /opt/csw/bin/bg5+pdflatex=gbkpdflatex

and in the texlive_latex_extra_binaries the symbolic links are missing.

 From whichever point I look at the recipe,
http://gar.svn.sourceforge.net/viewvc/gar/csw/mgar/pkg/texlive/trunk/Makefile,
this stays a mystery for me. The only cue is that checkpkg is right and 
mgar wrong...

I gratefully thank in advance those who help solving this puzzle.


From dam at opencsw.org  Thu Feb 14 11:02:49 2013
From: dam at opencsw.org (Dagobert Michelsen)
Date: Thu, 14 Feb 2013 11:02:49 +0100
Subject: [csw-maintainers] checkpkg signals a misterious dependency for
	TeXLive and it's right
In-Reply-To: <fb79243fbd8ae8bf0095ab4289845972@opencsw.org>
References: <fb79243fbd8ae8bf0095ab4289845972@opencsw.org>
Message-ID: <A1BDA6BE-3199-4394-B7D3-BA1DFEC09F8B@opencsw.org>

Hi Peter,

Am 14.02.2013 um 10:43 schrieb pfelecan <pfelecan at opencsw.org>:

> TeXLive has many packages. One of them is
> texlive_latex_extra_binaries, which contains architecturally
> dependent files and some symbolic links toward them; the
> texlive_common is a package containing only architecturally
> neutral files and is the result of the "reminder" files, i.e.,
> everything not in specific packages is in it...
> 
> However, I get:
> 
> RUNTIME_DEP_PKGS_CSWtexlive-common += CSWtexlive-latex-extra-binaries
> If any of the reported errors were false positives, you can override them
> pasting the lines below to the GAR recipe.
> CHECKPKG_OVERRIDES_CSWtexlive-common += missing-dependency|CSWtexlive-latex-extra-binaries
> 
> Dependency issues of CSWtexlive-common:
> CSWtexlive-latex-extra-binaries is needed by CSWtexlive-common, because:
> - symlink contains a CSWtexlive-common (u'/opt/csw/bin/bg5+latex') which
> needs the target file: '/opt/csw/bin/gbklatex'.
> - symlink contains a CSWtexlive-common (u'/opt/csw/bin/bg5+pdflatex')
> which needs the target file: '/opt/csw/bin/gbkpdflatex'.
> RUNTIME_DEP_PKGS_CSWtexlive-common += CSWtexlive-latex-extra-binaries
> 
> But the incriminated files are all part of the
> texlive_latex_extra_binaries:
> 
> PKGFILES_CSWtexlive-latex-extra-binaries        +=    /opt/csw/bin/bg5+latex
> PKGFILES_CSWtexlive-latex-extra-binaries        +=    /opt/csw/bin/bg5+pdflatex
> PKGFILES_CSWtexlive-latex-extra-binaries        +=    /opt/csw/bin/gbklatex
> PKGFILES_CSWtexlive-latex-extra-binaries        +=    /opt/csw/bin/gbkpdflatex
> 
> Effectively, we have in the texlive_comon prototype:
> 
> s none /opt/csw/bin/bg5+latex=gbklatex
> s none /opt/csw/bin/bg5+pdflatex=gbkpdflatex
> 
> and in the texlive_latex_extra_binaries the symbolic links are missing.
> 
> From whichever point I look at the recipe,
> http://gar.svn.sourceforge.net/viewvc/gar/csw/mgar/pkg/texlive/trunk/Makefile,
> this stays a mystery for me. The only cue is that checkpkg is right and mgar wrong...

The arguments of PKGFILES are regexes, try \+ instead of +.

Best regards

  -- Dago

From dam at opencsw.org  Fri Feb 15 15:43:41 2013
From: dam at opencsw.org (Dagobert Michelsen)
Date: Fri, 15 Feb 2013 15:43:41 +0100
Subject: [csw-maintainers] mgar: platforms-repackage output
In-Reply-To: <ff2266632bd219499202191bcdeca1ab@opencsw.org>
References: <ff2266632bd219499202191bcdeca1ab@opencsw.org>
Message-ID: <1667E6A3-04C9-4231-A44B-8F5CAA422E8E@opencsw.org>

Hi Peter,

Am 14.02.2013 um 10:02 schrieb pfelecan <pfelecan at opencsw.org>:
> When I "platforms-repackage", the output is misleading, only the names of the packages generated for one architecture and "all" are printed out:
> 
> $ mgar platforms-remerge platforms-repackage
> [...]
>  CSWautogen           /home/pfelecan/staging/build-14.Feb.2013/autogen-5.17.1,REV=2013.02.14-SunOS5.10-i386-CSW.pkg.gz
>  CSWautogen-dev       /home/pfelecan/staging/build-14.Feb.2013/autogen_dev-5.17.1,REV=2013.02.14-SunOS5.10-all-CSW.pkg.gz
>  CSWautogen-doc       /home/pfelecan/staging/build-14.Feb.2013/autogen_doc-5.17.1,REV=2013.02.14-SunOS5.10-all-CSW.pkg.gz
>  CSWautogendoc        /home/pfelecan/staging/build-14.Feb.2013/autogen_doc_stub-5.17.1,REV=2013.02.14-SunOS5.10-all-CSW.pkg.gz
>  CSWautogenrt         /home/pfelecan/staging/build-14.Feb.2013/autogenrt_stub-5.17.1,REV=2013.02.14-SunOS5.10-all-CSW.pkg.gz
>  CSWlibopts25         /home/pfelecan/staging/build-14.Feb.2013/libopts25-5.17.1,REV=2013.02.14-SunOS5.10-i386-CSW.pkg.gz
> 
> but in the stagging directory we have:
> 
> autogen-5.17.1,REV=2013.02.14-SunOS5.10-i386-CSW.pkg.gz
> autogen-5.17.1,REV=2013.02.14-SunOS5.10-sparc-CSW.pkg.gz
> autogen_dev-5.17.1,REV=2013.02.14-SunOS5.10-all-CSW.pkg.gz
> autogen_doc-5.17.1,REV=2013.02.14-SunOS5.10-all-CSW.pkg.gz
> autogen_doc_stub-5.17.1,REV=2013.02.14-SunOS5.10-all-CSW.pkg.gz
> autogenrt_stub-5.17.1,REV=2013.02.14-SunOS5.10-all-CSW.pkg.gz
> libopts25-5.17.1,REV=2013.02.14-SunOS5.10-i386-CSW.pkg.gz
> libopts25-5.17.1,REV=2013.02.14-SunOS5.10-sparc-CSW.pkg.gz
> 
> all this is done from unstable10s


Right. This is because the generated files are printed after each platform, so the other
packages are printed after sparc and before i386. But you are right, it would be better
to collect the output until the end.

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 pfelecan at opencsw.org  Fri Feb 15 19:38:40 2013
From: pfelecan at opencsw.org (Peter FELECAN)
Date: Fri, 15 Feb 2013 19:38:40 +0100
Subject: [csw-maintainers] Promoting dublin to stable
In-Reply-To: <CALtRa-4HSiX+rC+1YKcCWhfWPWzFZ9L6FSySTKbFUWu0sD4FwQ@mail.gmail.com>
	("Maciej (Matchek) =?utf-8?Q?Blizi=C5=84ski=22's?= message of "Wed,
	13 Feb 2013 21:31:33 +0000")
References: <CALtRa-4HSiX+rC+1YKcCWhfWPWzFZ9L6FSySTKbFUWu0sD4FwQ@mail.gmail.com>
Message-ID: <x6621th173.fsf@opencsw.org>

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

> I hope that there aren't many users left who are using the legacy release
> from 2008. Unfortunately, I don't have any data - maybe there are, maybe
> there aren't. I don't think we have a way to know, so we need to
> arbitrarily set a date when we'll make 'dublin' the stable release and
> 'kiel' the testing release. Any suggestions or ideas? How much more time do
> we need to give people to notice? I was thinking about for example the
> beginning of May.

No need to wait till May. Lets do it now.
-- 
Peter

From pfelecan at opencsw.org  Fri Feb 15 19:39:39 2013
From: pfelecan at opencsw.org (Peter FELECAN)
Date: Fri, 15 Feb 2013 19:39:39 +0100
Subject: [csw-maintainers] checkpkg signals a misterious dependency for
	TeXLive and it's right
In-Reply-To: <A1BDA6BE-3199-4394-B7D3-BA1DFEC09F8B@opencsw.org> (Dagobert
	Michelsen's message of "Thu, 14 Feb 2013 11:02:49 +0100")
References: <fb79243fbd8ae8bf0095ab4289845972@opencsw.org>
	<A1BDA6BE-3199-4394-B7D3-BA1DFEC09F8B@opencsw.org>
Message-ID: <x61uchh15g.fsf@opencsw.org>

Dagobert Michelsen <dam at opencsw.org> writes:

> The arguments of PKGFILES are regexes, try \+ instead of +.

Thank you. This got me nearer to releasing TeXLive...
-- 
Peter

From bwalton at opencsw.org  Fri Feb 15 21:45:55 2013
From: bwalton at opencsw.org (Ben Walton)
Date: Fri, 15 Feb 2013 20:45:55 +0000
Subject: [csw-maintainers] Promoting dublin to stable
In-Reply-To: <x6621th173.fsf@opencsw.org>
References: <CALtRa-4HSiX+rC+1YKcCWhfWPWzFZ9L6FSySTKbFUWu0sD4FwQ@mail.gmail.com>
	<x6621th173.fsf@opencsw.org>
Message-ID: <CAP30j17t-kSwPhvY1Nc6t3QNc6R_soSiwdLyUiQQiuDHLzyoZA@mail.gmail.com>

Agreed.  For anyone still using stable, the difference between now and
May is meaningless. :)

Thanks
-Ben

On Fri, Feb 15, 2013 at 6:38 PM, Peter FELECAN <pfelecan at opencsw.org> wrote:
> "Maciej (Matchek) Blizi?ski" <maciej at opencsw.org> writes:
>
>> I hope that there aren't many users left who are using the legacy release
>> from 2008. Unfortunately, I don't have any data - maybe there are, maybe
>> there aren't. I don't think we have a way to know, so we need to
>> arbitrarily set a date when we'll make 'dublin' the stable release and
>> 'kiel' the testing release. Any suggestions or ideas? How much more time do
>> we need to give people to notice? I was thinking about for example the
>> beginning of May.
>
> No need to wait till May. Lets do it now.
> --
> Peter
> _______________________________________________
> 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 Feb 16 13:24:16 2013
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Sat, 16 Feb 2013 12:24:16 +0000
Subject: [csw-maintainers] Promoting dublin to stable
In-Reply-To: <CAP30j17t-kSwPhvY1Nc6t3QNc6R_soSiwdLyUiQQiuDHLzyoZA@mail.gmail.com>
References: <CALtRa-4HSiX+rC+1YKcCWhfWPWzFZ9L6FSySTKbFUWu0sD4FwQ@mail.gmail.com>
	<x6621th173.fsf@opencsw.org>
	<CAP30j17t-kSwPhvY1Nc6t3QNc6R_soSiwdLyUiQQiuDHLzyoZA@mail.gmail.com>
Message-ID: <CALtRa-65YwrK_nmBBbX+mnsZ2bhbvHJuTWgoDD+E1yqK46UVrg@mail.gmail.com>

2013/2/15 Ben Walton <bwalton at opencsw.org>
>
> Agreed.  For anyone still using stable, the difference between now and
> May is meaningless. :)

Cool. Three voices of support so far. Any objections to mark dublin as
stable in the coming days?

We could call it releasing the dublin catalog. I think it's a word
that will catch on. I will write two announcement messages: the one
we'll publish one week in advance, and the one we'll publish when it's
done.

Maciej

From pfelecan at opencsw.org  Tue Feb 19 13:46:47 2013
From: pfelecan at opencsw.org (pfelecan)
Date: Tue, 19 Feb 2013 13:46:47 +0100
Subject: [csw-maintainers] cannot upload update of class action script
	texhash package
Message-ID: <1b05bdccbafda9ecde9884bc84f4045e@opencsw.org>

I bit flabbergasted:

Having modified my class action script, I package-it following the 
instructions in the README file:

on unstable10s:

mgar package-CSWcas-texhash

the log file is in ~/logs/cas_texhash

On login, I try to upload it:


csw-upload-pkg staging/build-19.Feb.2013/*

and I got:

Processing 1 file(s). Please wait.
WARNING:root:http://buildfarm.opencsw.org/pkgdb/rest/srv4/a439d983f79d027331a940859c4aca76/ 
-- HTTP Error 404: Not Found
WARNING:root:staging/build-19.Feb.2013/cas_texhash-1.49,REV=2013.02.19-SunOS5.10-all-CSW.pkg.gz 
(a439d983f79d027331a940859c4aca76) is not known to the database.
INFO:root:Juicing the svr4 package stream files...
Traceback (most recent call last):                                      
       |
   File "/opt/csw/bin/pkgdb", line 698, in <module>
     main()
   File "/opt/csw/bin/pkgdb", line 444, in main
     force_unpack=options.force_unpack)
   File "/opt/csw/lib/python/csw/package_stats.py", line 506, in 
CollectStatsFromFiles
     stats.CollectStats(force=force_unpack)
   File "/opt/csw/lib/python/csw/package_stats.py", line 175, in 
CollectStats
     return self._CollectStats(register_files=register_files)
   File "/opt/csw/lib/python/csw/package_stats.py", line 187, in 
_CollectStats
     dir_pkg = self.GetInspectivePkg()
   File "/opt/csw/lib/python/csw/package_stats.py", line 120, in 
GetInspectivePkg
     self.dir_format_pkg = self.srv4_pkg.GetInspectivePkg()
   File "/opt/csw/lib/python/csw/inspective_package.py", line 761, in 
GetInspectivePkg
     return self.GetDirFormatPkg()
   File "/opt/csw/lib/python/csw/package.py", line 176, in 
GetDirFormatPkg
     self.TransformToDir()
   File "/opt/csw/lib/python/csw/package.py", line 167, in 
TransformToDir
     unused_retcode = self.ShellCommand(args, quiet=(not self.debug))
   File "/opt/csw/lib/python/csw/shell.py", line 18, in ShellCommand
     stderr=subprocess.PIPE)
   File "/opt/csw/lib/python/subprocess.py", line 623, in __init__
     errread, errwrite)
   File "/opt/csw/lib/python/subprocess.py", line 1141, in 
_execute_child
     raise child_exception
OSError: [Errno 2] No such file or directory
Traceback (most recent call last):
   File "/opt/csw/bin/csw-upload-pkg", line 516, in <module>
     uploader.Upload()
   File "/opt/csw/bin/csw-upload-pkg", line 150, in Upload
     self._ImportMetadata(filename)
   File "/opt/csw/bin/csw-upload-pkg", line 134, in _ImportMetadata
     raise OSError("An error occurred when running %s." % args)
OSError: An error occurred when running ['/opt/csw/bin/pkgdb', 
'importpkg', 
'staging/build-19.Feb.2013/cas_texhash-1.49,REV=2013.02.19-SunOS5.10-all-CSW.pkg.gz'].


Is there someone understanding what happened?

TIA


From maciej at opencsw.org  Tue Feb 19 14:23:47 2013
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Tue, 19 Feb 2013 13:23:47 +0000
Subject: [csw-maintainers] cannot upload update of class action script
 texhash package
In-Reply-To: <1b05bdccbafda9ecde9884bc84f4045e@opencsw.org>
References: <1b05bdccbafda9ecde9884bc84f4045e@opencsw.org>
Message-ID: <CALtRa-7E-kLNg0=uh=g+Ffy7jLHm6_AAwCmdkA3Q75TvfzfT6A@mail.gmail.com>

2013/2/19 pfelecan <pfelecan at opencsw.org>:
> Is there someone understanding what happened?

>From reading "/opt/csw/lib/python/csw/package.py", line 167, looks
like custom-pkgtrans from gar/v2/bin cannot be found.

Could you try running in debug mode? I think that it will say what
exactly was not found ("No such file or directory").

By the way - we seem to have problems with the /opt/csw/bin
installation of our tools a lot. It's obviously poorly tested in this
location. Myself, I'm almost always testing my local changes, so I
obviously can't run from /opt/csw/bin, and this causes me to miss
issues with the /opt/csw/bin installation. Any ideas how to improve
this process?

Maciej

From pfelecan at opencsw.org  Tue Feb 19 14:48:45 2013
From: pfelecan at opencsw.org (pfelecan)
Date: Tue, 19 Feb 2013 14:48:45 +0100
Subject: [csw-maintainers] cannot upload update of class action script
	texhash package
In-Reply-To: <1b05bdccbafda9ecde9884bc84f4045e@opencsw.org>
References: <1b05bdccbafda9ecde9884bc84f4045e@opencsw.org>
Message-ID: <47d5b88682bfc1d91de53c2573aacb24@opencsw.org>

Here is the debug output --- BTW, when running csw-upload-pkg, the 
debug option is not mentionned in the usage...

pfelecan at login [login]:~ > csw-upload-pkg --debug 
staging/build-19.Feb.2013/* 2>&1 | tee ~/logs/csw-upload-pkg
DEBUG:root:args: 
['staging/build-19.Feb.2013/cas_texhash-1.49,REV=2013.02.19-SunOS5.10-all-CSW.pkg.gz']
DEBUG:root:_GetFileMd5sum(staging/build-19.Feb.2013/cas_texhash-1.49,REV=2013.02.19-SunOS5.10-all-CSW.pkg.gz): 
Reading the file
DEBUG:root:GetPkgByMd5(): GET 
http://buildfarm.opencsw.org/pkgdb/rest/srv4/a439d983f79d027331a940859c4aca76/
WARNING:root:http://buildfarm.opencsw.org/pkgdb/rest/srv4/a439d983f79d027331a940859c4aca76/ 
-- HTTP Error 404: Not Found
WARNING:root:staging/build-19.Feb.2013/cas_texhash-1.49,REV=2013.02.19-SunOS5.10-all-CSW.pkg.gz 
(a439d983f79d027331a940859c4aca76) is not known to the database.
DEBUG:root:Debugging on
DEBUG:root:db_name: checkpkg, db_user: pkg_maintainer
DEBUG:root:auto_manage_option = no
DEBUG:root:auto_manage: False
DEBUG:root:Database schema version: 9, application expects: 9
DEBUG:root:GetDatabaseMtime() --> 1
DEBUG:root:args: 
['staging/build-19.Feb.2013/cas_texhash-1.49,REV=2013.02.19-SunOS5.10-all-CSW.pkg.gz']
DEBUG:root:_GetFileMd5sum(staging/build-19.Feb.2013/cas_texhash-1.49,REV=2013.02.19-SunOS5.10-all-CSW.pkg.gz): 
Reading the file
DEBUG:root:GetPkgByMd5(): GET 
http://buildfarm.opencsw.org/pkgdb/rest/srv4/a439d983f79d027331a940859c4aca76/
WARNING:root:http://buildfarm.opencsw.org/pkgdb/rest/srv4/a439d983f79d027331a940859c4aca76/ 
-- HTTP Error 404: Not Found
WARNING:root:staging/build-19.Feb.2013/cas_texhash-1.49,REV=2013.02.19-SunOS5.10-all-CSW.pkg.gz 
(a439d983f79d027331a940859c4aca76) is not known to the database.
DEBUG:root:Debugging on
DEBUG:root:db_name: checkpkg, db_user: pkg_maintainer
DEBUG:root:auto_manage_option = no
DEBUG:root:auto_manage: False
DEBUG:root:Database schema version: 9, application expects: 9
DEBUG:root:GetDatabaseMtime() --> 1
DEBUG:root:IsDatabaseUpToDate: f_mtime time.struct_time(tm_year=2013, 
tm_mon=2, tm_mday=13, tm_hour=21, tm_min=49, tm_sec=2, tm_wday=2, 
tm_yday=44, tm_isdst=0), d_time: time.struct_time(tm_year=1970, 
tm_mon=1, tm_mday=1, tm_hour=0, tm_min=0, tm_sec=1, tm_wday=3, 
tm_yday=1, tm_isdst=0)
DEBUG:root:IsDatabaseUpToDate: good_version=True, fresh=False
DEBUG:root:Processing: 
['staging/build-19.Feb.2013/cas_texhash-1.49,REV=2013.02.19-SunOS5.10-all-CSW.pkg.gz'], 
please be patient
DEBUG:root:CswSrv4File('staging/build-19.Feb.2013/cas_texhash-1.49,REV=2013.02.19-SunOS5.10-all-CSW.pkg.gz', 
debug=True)
INFO:root:Juicing the svr4 package stream files...
   0% |                                                                  
      |
^MDEBUG:root:GetMd5sum() reading file 
'staging/build-19.Feb.2013/cas_texhash-1.49,REV=2013.02.19-SunOS5.10-all-CSW.pkg.gz'
DEBUG:root:GetDbObject(): <PackageStats 
srv4_pkg=CswSrv4File('staging/build-19.Feb.2013/cas_texhash-1.49,REV=2013.02.19-SunOS5.10-all-CSW.pkg.gz') 
md5sum=a439d983f79d027331a940859c4aca76> md5sum: 
a439d983f79d027331a940859c4aca76
DEBUG:root:GetDbObject(): a439d983f79d027331a940859c4aca76 not found
DEBUG:root:Could not get db object for a439d983f79d027331a940859c4aca76
DEBUG:root:Calling: ['gunzip', '-f', 
'/tmp/pkg_7bnjlH/cas_texhash-1.49,REV=2013.02.19-SunOS5.10-all-CSW.pkg.gz']
DEBUG:root:GetPkgname(): 'CSWcas-texhash'
DEBUG:root:transforming: 
['/opt/csw/lib/python/csw/../../bin/custom-pkgtrans', 
'/tmp/pkg_7bnjlH/cas_texhash-1.49,REV=2013.02.19-SunOS5.10-all-CSW.pkg', 
'/tmp/pkg_7bnjlH', 'CSWcas-texhash']
DEBUG:root:Calling: 
['/opt/csw/lib/python/csw/../../bin/custom-pkgtrans', 
'/tmp/pkg_7bnjlH/cas_texhash-1.49,REV=2013.02.19-SunOS5.10-all-CSW.pkg', 
'/tmp/pkg_7bnjlH', 'CSWcas-texhash']
Traceback (most recent call last):
   File "/opt/csw/bin/pkgdb", line 698, in <module>
     main()
   File "/opt/csw/bin/pkgdb", line 444, in main
     force_unpack=options.force_unpack)
   File "/opt/csw/lib/python/csw/package_stats.py", line 506, in 
CollectStatsFromFiles
     stats.CollectStats(force=force_unpack)
   File "/opt/csw/lib/python/csw/package_stats.py", line 175, in 
CollectStats
     return self._CollectStats(register_files=register_files)
   File "/opt/csw/lib/python/csw/package_stats.py", line 187, in 
_CollectStats
     dir_pkg = self.GetInspectivePkg()
   File "/opt/csw/lib/python/csw/package_stats.py", line 120, in 
GetInspectivePkg
     self.dir_format_pkg = self.srv4_pkg.GetInspectivePkg()
   File "/opt/csw/lib/python/csw/inspective_package.py", line 761, in 
GetInspectivePkg
     return self.GetDirFormatPkg()
   File "/opt/csw/lib/python/csw/package.py", line 176, in 
GetDirFormatPkg
     self.TransformToDir()
   File "/opt/csw/lib/python/csw/package.py", line 167, in 
TransformToDir
     unused_retcode = self.ShellCommand(args, quiet=(not self.debug))
   File "/opt/csw/lib/python/csw/shell.py", line 22, in ShellCommand
     retcode = subprocess.call(args)
   File "/opt/csw/lib/python/subprocess.py", line 470, in call
     return Popen(*popenargs, **kwargs).wait()
   File "/opt/csw/lib/python/subprocess.py", line 623, in __init__
     errread, errwrite)
   File "/opt/csw/lib/python/subprocess.py", line 1141, in 
_execute_child
     raise child_exception
OSError: [Errno 2] No such file or directory
DEBUG:root:Removing '/tmp/pkg_7bnjlH'
Processing 1 file(s). Please wait.
Traceback (most recent call last):
   File "/opt/csw/bin/csw-upload-pkg", line 516, in <module>
     uploader.Upload()
   File "/opt/csw/bin/csw-upload-pkg", line 150, in Upload
     self._ImportMetadata(filename)
   File "/opt/csw/bin/csw-upload-pkg", line 134, in _ImportMetadata
     raise OSError("An error occurred when running %s." % args)
OSError: An error occurred when running ['/opt/csw/bin/pkgdb', 
'importpkg', '--debug', 
'staging/build-19.Feb.2013/cas_texhash-1.49,REV=2013.02.19-SunOS5.10-all-CSW.pkg.gz'].


From maciej at opencsw.org  Tue Feb 19 15:19:10 2013
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Tue, 19 Feb 2013 14:19:10 +0000
Subject: [csw-maintainers] cannot upload update of class action script
 texhash package
In-Reply-To: <47d5b88682bfc1d91de53c2573aacb24@opencsw.org>
References: <1b05bdccbafda9ecde9884bc84f4045e@opencsw.org>
	<47d5b88682bfc1d91de53c2573aacb24@opencsw.org>
Message-ID: <CALtRa-4Q7T11AApF1gEXhhOzUkqS5wT2NWr+Rsf2m1e_eM9v5g@mail.gmail.com>

2013/2/19 pfelecan <pfelecan at opencsw.org>:
> Here is the debug output --- BTW, when running csw-upload-pkg, the debug
> option is not mentionned in the usage...

Is it not? I'm getting:

maciej at login [login]:~ > csw-upload-pkg --help | grep debug
  -d, --debug

Where did you expect to see it?

> pfelecan at login [login]:~ > csw-upload-pkg --debug
> staging/build-19.Feb.2013/* 2>&1 | tee ~/logs/csw-upload-pkg
(...)
> DEBUG:root:Calling: ['/opt/csw/lib/python/csw/../../bin/custom-pkgtrans',

Here we are. It expects it to be in /opt/csw/lib/bin/custom-pkgtrans,
and it's not there.

But hang on... the pkgtrans step is never done on login, it should
not, it cannot be done on login because we're now running ldd as part
of package indexing. Did you disable checkpkg during the package
build stage? Or did you not do build it on the buildfarm? Or did you
run GAR in such a way that it didn't call checkpkg?

Maciej

From dam at opencsw.org  Tue Feb 19 15:22:01 2013
From: dam at opencsw.org (Dagobert Michelsen)
Date: Tue, 19 Feb 2013 15:22:01 +0100
Subject: [csw-maintainers] cannot upload update of class action script
	texhash package
In-Reply-To: <CALtRa-4Q7T11AApF1gEXhhOzUkqS5wT2NWr+Rsf2m1e_eM9v5g@mail.gmail.com>
References: <1b05bdccbafda9ecde9884bc84f4045e@opencsw.org>
	<47d5b88682bfc1d91de53c2573aacb24@opencsw.org>
	<CALtRa-4Q7T11AApF1gEXhhOzUkqS5wT2NWr+Rsf2m1e_eM9v5g@mail.gmail.com>
Message-ID: <AFB0B6D7-8425-4530-8B79-2FE5B7FA47D8@opencsw.org>

Hi Maciej,

Am 19.02.2013 um 15:19 schrieb Maciej (Matchek) Blizi?ski <maciej at opencsw.org>:
> 2013/2/19 pfelecan <pfelecan at opencsw.org>:
>> Here is the debug output --- BTW, when running csw-upload-pkg, the debug
>> option is not mentionned in the usage...
> 
> Is it not? I'm getting:
> 
> maciej at login [login]:~ > csw-upload-pkg --help | grep debug
>  -d, --debug
> 
> Where did you expect to see it?
> 
>> pfelecan at login [login]:~ > csw-upload-pkg --debug
>> staging/build-19.Feb.2013/* 2>&1 | tee ~/logs/csw-upload-pkg
> (...)
>> DEBUG:root:Calling: ['/opt/csw/lib/python/csw/../../bin/custom-pkgtrans',
> 
> Here we are. It expects it to be in /opt/csw/lib/bin/custom-pkgtrans,
> and it's not there.
> 
> But hang on... the pkgtrans step is never done on login, it should
> not, it cannot be done on login because we're now running ldd as part
> of package indexing. Did you disable checkpkg during the package
> build stage? Or did you not do build it on the buildfarm? Or did you
> run GAR in such a way that it didn't call checkpkg?


As Peter used
  mgar package-<pkgname>
to rebuild just a single package I am afraid it does not call checkpkg. Most certainly
it will also not work to call it individually due to the package interdependencies.
Thoughts?

@Peter: You could try to checkpkg it manually, but I doubt it would work.


Best regards

  -- Dago

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


From maciej at opencsw.org  Tue Feb 19 15:52:30 2013
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Tue, 19 Feb 2013 14:52:30 +0000
Subject: [csw-maintainers] cannot upload update of class action script
 texhash package
In-Reply-To: <AFB0B6D7-8425-4530-8B79-2FE5B7FA47D8@opencsw.org>
References: <1b05bdccbafda9ecde9884bc84f4045e@opencsw.org>
	<47d5b88682bfc1d91de53c2573aacb24@opencsw.org>
	<CALtRa-4Q7T11AApF1gEXhhOzUkqS5wT2NWr+Rsf2m1e_eM9v5g@mail.gmail.com>
	<AFB0B6D7-8425-4530-8B79-2FE5B7FA47D8@opencsw.org>
Message-ID: <CALtRa-6tg5OnjKaB6ASk1YaanEL2_=B0ZjLD4M=1atrA-UTZSA@mail.gmail.com>

2013/2/19 Dagobert Michelsen <dam at opencsw.org>:
> As Peter used
>   mgar package-<pkgname>
> to rebuild just a single package I am afraid it does not call checkpkg. Most certainly
> it will also not work to call it individually due to the package interdependencies.

If this package can be uploaded on its own, it should also pass checks
on its own. Calling checkpkg individually won't work in the general
case, but if a maintainer builds only one package... maybe at least
display a copy-pastable command to run checkpkg easily?

> @Peter: You could try to checkpkg it manually, but I doubt it would work.

I think it could work.

From pfelecan at opencsw.org  Tue Feb 19 16:51:18 2013
From: pfelecan at opencsw.org (pfelecan)
Date: Tue, 19 Feb 2013 16:51:18 +0100
Subject: [csw-maintainers] cannot upload update of class action script
	texhash package
In-Reply-To: <1b05bdccbafda9ecde9884bc84f4045e@opencsw.org>
References: <1b05bdccbafda9ecde9884bc84f4045e@opencsw.org>
Message-ID: <6d4dd1d5f4b478fd2beea73044c5a2cc@opencsw.org>

Well, running checkpkg doesn't grok:

~/opencsw/.buildsys/v2/bin/checkpkg --os-releases=SunOS5.10,SunOS5.11 
--architecture=all 
~/staging/build-19.Feb.2013/cas_texhash-1.49\,REV\=2013.02.19-SunOS5.10-all-CSW.pkg.gz
Traceback (most recent call last):
   File "/home/pfelecan/opencsw/.buildsys/v2/bin/checkpkg", line 197, in 
<module>
     main()
   File "/home/pfelecan/opencsw/.buildsys/v2/bin/checkpkg", line 106, in 
main
     raise UsageError(" ".join(err_msg_list))
__main__.UsageError: Valid --architecture values are: ['sparc', 
'i386'], you passed: 'all'

Yes, showing how to use checkpkg in this case is not a luxury...


From pfelecan at opencsw.org  Tue Feb 19 19:18:56 2013
From: pfelecan at opencsw.org (Peter FELECAN)
Date: Tue, 19 Feb 2013 19:18:56 +0100
Subject: [csw-maintainers] cannot upload update of class action script
	texhash package
In-Reply-To: <CALtRa-4Q7T11AApF1gEXhhOzUkqS5wT2NWr+Rsf2m1e_eM9v5g@mail.gmail.com>
	("Maciej (Matchek) =?utf-8?Q?Blizi=C5=84ski=22's?= message of "Tue,
	19 Feb 2013 14:19:10 +0000")
References: <1b05bdccbafda9ecde9884bc84f4045e@opencsw.org>
	<47d5b88682bfc1d91de53c2573aacb24@opencsw.org>
	<CALtRa-4Q7T11AApF1gEXhhOzUkqS5wT2NWr+Rsf2m1e_eM9v5g@mail.gmail.com>
Message-ID: <x6liak5fqn.fsf@opencsw.org>

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

> 2013/2/19 pfelecan <pfelecan at opencsw.org>:
>> Here is the debug output --- BTW, when running csw-upload-pkg, the debug
>> option is not mentionned in the usage...
>
> Is it not? I'm getting:
>
> maciej at login [login]:~ > csw-upload-pkg --help | grep debug
>   -d, --debug
>
> Where did you expect to see it?

In my wonderful world, when I'm miss-using an utility, it shows its
usage, i.e., same thing as --help with the additional and specific
message about what's wrong with my incantation.
-- 
Peter

From pfelecan at opencsw.org  Tue Feb 19 19:19:56 2013
From: pfelecan at opencsw.org (Peter FELECAN)
Date: Tue, 19 Feb 2013 19:19:56 +0100
Subject: [csw-maintainers] cannot upload update of class action script
	texhash package
In-Reply-To: <CALtRa-6tg5OnjKaB6ASk1YaanEL2_=B0ZjLD4M=1atrA-UTZSA@mail.gmail.com>
	("Maciej (Matchek) =?utf-8?Q?Blizi=C5=84ski=22's?= message of "Tue,
	19 Feb 2013 14:52:30 +0000")
References: <1b05bdccbafda9ecde9884bc84f4045e@opencsw.org>
	<47d5b88682bfc1d91de53c2573aacb24@opencsw.org>
	<CALtRa-4Q7T11AApF1gEXhhOzUkqS5wT2NWr+Rsf2m1e_eM9v5g@mail.gmail.com>
	<AFB0B6D7-8425-4530-8B79-2FE5B7FA47D8@opencsw.org>
	<CALtRa-6tg5OnjKaB6ASk1YaanEL2_=B0ZjLD4M=1atrA-UTZSA@mail.gmail.com>
Message-ID: <x6hal85foz.fsf@opencsw.org>

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

> 2013/2/19 Dagobert Michelsen <dam at opencsw.org>:
>> As Peter used
>>   mgar package-<pkgname>
>> to rebuild just a single package I am afraid it does not call checkpkg. Most certainly
>> it will also not work to call it individually due to the package interdependencies.
>
> If this package can be uploaded on its own, it should also pass checks
> on its own. Calling checkpkg individually won't work in the general
> case, but if a maintainer builds only one package... maybe at least
> display a copy-pastable command to run checkpkg easily?

Oh yes, please!

>> @Peter: You could try to checkpkg it manually, but I doubt it would work.
>
> I think it could work.

It didn't, see my next message.
-- 
Peter

From maciej at opencsw.org  Tue Feb 19 21:13:48 2013
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Tue, 19 Feb 2013 20:13:48 +0000
Subject: [csw-maintainers] cannot upload update of class action script
 texhash package
In-Reply-To: <6d4dd1d5f4b478fd2beea73044c5a2cc@opencsw.org>
References: <1b05bdccbafda9ecde9884bc84f4045e@opencsw.org>
	<6d4dd1d5f4b478fd2beea73044c5a2cc@opencsw.org>
Message-ID: <CALtRa-4zPfyDiET6qCqssxBM-wn+G85vLbZUCThgBRMJYH5rWQ@mail.gmail.com>

2013/2/19 pfelecan <pfelecan at opencsw.org>:
> Well, running checkpkg doesn't grok:
>
> ~/opencsw/.buildsys/v2/bin/checkpkg --os-releases=SunOS5.10,SunOS5.11
> --architecture=all
> ~/staging/build-19.Feb.2013/cas_texhash-1.49\,REV\=2013.02.19-SunOS5.10-all-CSW.pkg.gz
>
> Traceback (most recent call last):
>   File "/home/pfelecan/opencsw/.buildsys/v2/bin/checkpkg", line 197, in
> <module>
>     main()
>   File "/home/pfelecan/opencsw/.buildsys/v2/bin/checkpkg", line 106, in main
>     raise UsageError(" ".join(err_msg_list))
> __main__.UsageError: Valid --architecture values are: ['sparc', 'i386'], you
> passed: 'all'
>
> Yes, showing how to use checkpkg in this case is not a luxury...

Not sure what you mean with the luxury. It does tell you how to use
it, doesn't it? It does tell you what the valid values are. So... you
see it, and it's not a luxury? I'm not getting it. Anyway...

The --architecture flag is not about your package. It's about the
catalog you want to check your package against. We do not have an
'all' catalog. When you have an 'all' package, you want to either
check it against the sparc, or against the intel catalog. If the
quoted above message from checkpkg wasn't clear, what would a clear
message look like?

Maciej

From pfelecan at opencsw.org  Wed Feb 20 10:13:09 2013
From: pfelecan at opencsw.org (pfelecan)
Date: Wed, 20 Feb 2013 10:13:09 +0100
Subject: [csw-maintainers] cannot upload update of class action script
	texhash package
In-Reply-To: <6d4dd1d5f4b478fd2beea73044c5a2cc@opencsw.org>
References: <1b05bdccbafda9ecde9884bc84f4045e@opencsw.org>
	<6d4dd1d5f4b478fd2beea73044c5a2cc@opencsw.org>
Message-ID: <47d3838bf71b2f6eb5318769096f041e@opencsw.org>

The following incantation worked:

~/opencsw/.buildsys/v2/bin/checkpkg --catalog-release=unstable 
--os-releases=SunOS5.10,SunOS5.11 --architecture=sparc 
~/staging/build-19.Feb.2013/cas_texhash-1.49\,REV\=2013.02.19-SunOS5.10-all-CSW.pkg.gz

Thanking everybody who tried to help.




From pfelecan at opencsw.org  Wed Feb 20 19:10:36 2013
From: pfelecan at opencsw.org (Peter FELECAN)
Date: Wed, 20 Feb 2013 19:10:36 +0100
Subject: [csw-maintainers] cannot upload update of class action script
	texhash package
In-Reply-To: <CALtRa-4zPfyDiET6qCqssxBM-wn+G85vLbZUCThgBRMJYH5rWQ@mail.gmail.com>
	("Maciej (Matchek) =?utf-8?Q?Blizi=C5=84ski=22's?= message of "Tue,
	19 Feb 2013 20:13:48 +0000")
References: <1b05bdccbafda9ecde9884bc84f4045e@opencsw.org>
	<6d4dd1d5f4b478fd2beea73044c5a2cc@opencsw.org>
	<CALtRa-4zPfyDiET6qCqssxBM-wn+G85vLbZUCThgBRMJYH5rWQ@mail.gmail.com>
Message-ID: <x638wq6elf.fsf@opencsw.org>

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

> 2013/2/19 pfelecan <pfelecan at opencsw.org>:
>> Well, running checkpkg doesn't grok:
>>
>> ~/opencsw/.buildsys/v2/bin/checkpkg --os-releases=SunOS5.10,SunOS5.11
>> --architecture=all
>> ~/staging/build-19.Feb.2013/cas_texhash-1.49\,REV\=2013.02.19-SunOS5.10-all-CSW.pkg.gz
>>
>> Traceback (most recent call last):
>>   File "/home/pfelecan/opencsw/.buildsys/v2/bin/checkpkg", line 197, in
>> <module>
>>     main()
>>   File "/home/pfelecan/opencsw/.buildsys/v2/bin/checkpkg", line 106, in main
>>     raise UsageError(" ".join(err_msg_list))
>> __main__.UsageError: Valid --architecture values are: ['sparc', 'i386'], you
>> passed: 'all'
>>
>> Yes, showing how to use checkpkg in this case is not a luxury...
>
> Not sure what you mean with the luxury. It does tell you how to use
> it, doesn't it? It does tell you what the valid values are. So... you
> see it, and it's not a luxury? I'm not getting it. Anyway...

Yes and no... It tells to use an architecture, BTW using Python
convention and not BNF as is expected from a syntax scheme, but it
doesn't tell that's about catalogs and not the nature of the package;
IMHO, the argument should be --catalog-architecture.

Finally, when I'm writing "luxury" I think to what was suggested by Dag,
i.e. when using only the "packaging" target on a system which has
checkpkg activated showing what should be the checkpkg stanza; and this
is not a luxury but a necessity as we have seen.

> The --architecture flag is not about your package. It's about the
> catalog you want to check your package against. We do not have an
> 'all' catalog. When you have an 'all' package, you want to either
> check it against the sparc, or against the intel catalog. If the
> quoted above message from checkpkg wasn't clear, what would a clear
> message look like?

When I understand the implicit it becomes clear as it must be and I
thank you.
-- 
Peter

From maciej at opencsw.org  Thu Feb 21 10:24:09 2013
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Thu, 21 Feb 2013 09:24:09 +0000
Subject: [csw-maintainers] cannot upload update of class action script
 texhash package
In-Reply-To: <x638wq6elf.fsf@opencsw.org>
References: <1b05bdccbafda9ecde9884bc84f4045e@opencsw.org>
	<6d4dd1d5f4b478fd2beea73044c5a2cc@opencsw.org>
	<CALtRa-4zPfyDiET6qCqssxBM-wn+G85vLbZUCThgBRMJYH5rWQ@mail.gmail.com>
	<x638wq6elf.fsf@opencsw.org>
Message-ID: <CALtRa-6NZi2MTJiZu5KuVQwDYJNTnAsYoOsEed=iD9UY33QmOg@mail.gmail.com>

2013/2/20 Peter FELECAN <pfelecan at opencsw.org>:
> "Maciej (Matchek) Blizi?ski" <maciej at opencsw.org> writes:
>>
>> Not sure what you mean with the luxury. It does tell you how to use
>> it, doesn't it? It does tell you what the valid values are. So... you
>> see it, and it's not a luxury? I'm not getting it. Anyway...
>
> Yes and no... It tells to use an architecture, BTW using Python
> convention and not BNF as is expected from a syntax scheme, but it
> doesn't tell that's about catalogs and not the nature of the package;
> IMHO, the argument should be --catalog-architecture.

Sure, done: http://sourceforge.net/apps/trac/gar/changeset/20325

> Finally, when I'm writing "luxury" I think to what was suggested by Dag,
> i.e. when using only the "packaging" target on a system which has
> checkpkg activated showing what should be the checkpkg stanza; and this
> is not a luxury but a necessity as we have seen.

Some GAR code refactoring will be required around line 1015 of
gar.pkg.mk, so that you can either run or display the checkpkg
command, and you still keep all how-to-run-checkpkg information in one place.

Dago, is it doable?

Maciej

From dam at opencsw.org  Thu Feb 21 10:56:16 2013
From: dam at opencsw.org (Dagobert Michelsen)
Date: Thu, 21 Feb 2013 10:56:16 +0100
Subject: [csw-maintainers] cannot upload update of class action script
	texhash package
In-Reply-To: <CALtRa-6NZi2MTJiZu5KuVQwDYJNTnAsYoOsEed=iD9UY33QmOg@mail.gmail.com>
References: <1b05bdccbafda9ecde9884bc84f4045e@opencsw.org>
	<6d4dd1d5f4b478fd2beea73044c5a2cc@opencsw.org>
	<CALtRa-4zPfyDiET6qCqssxBM-wn+G85vLbZUCThgBRMJYH5rWQ@mail.gmail.com>
	<x638wq6elf.fsf@opencsw.org>
	<CALtRa-6NZi2MTJiZu5KuVQwDYJNTnAsYoOsEed=iD9UY33QmOg@mail.gmail.com>
Message-ID: <0D6867CF-47F7-4C68-A795-17F80DBB8917@opencsw.org>

Hi,

Am 21.02.2013 um 10:24 schrieb Maciej (Matchek) Blizi?ski <maciej at opencsw.org>:
>> Finally, when I'm writing "luxury" I think to what was suggested by Dag,
>> i.e. when using only the "packaging" target on a system which has
>> checkpkg activated showing what should be the checkpkg stanza; and this
>> is not a luxury but a necessity as we have seen.
> 
> Some GAR code refactoring will be required around line 1015 of
> gar.pkg.mk, so that you can either run or display the checkpkg
> command, and you still keep all how-to-run-checkpkg information in one place.
> 
> Dago, is it doable?

The question is what the workflow would be and what should be done. A good thing would IMHO be

- mgar package
- (Edit some stuff)
- mgar repackage-CSWjustone

After the individual repackage all packages would be checked together. Checking just one
package would IMHO be too dangerous. Additionally, I would remove the target
  package-CSWfoo
as it indicates it could be explicitly called. Building just one package without the others
first is also a usecase I would like to avoid.

Peter, would this be acceptable?


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 pfelecan at opencsw.org  Fri Feb 22 19:35:13 2013
From: pfelecan at opencsw.org (Peter FELECAN)
Date: Fri, 22 Feb 2013 19:35:13 +0100
Subject: [csw-maintainers] cannot upload update of class action script
	texhash package
In-Reply-To: <0D6867CF-47F7-4C68-A795-17F80DBB8917@opencsw.org> (Dagobert
	Michelsen's message of "Thu, 21 Feb 2013 10:56:16 +0100")
References: <1b05bdccbafda9ecde9884bc84f4045e@opencsw.org>
	<6d4dd1d5f4b478fd2beea73044c5a2cc@opencsw.org>
	<CALtRa-4zPfyDiET6qCqssxBM-wn+G85vLbZUCThgBRMJYH5rWQ@mail.gmail.com>
	<x638wq6elf.fsf@opencsw.org>
	<CALtRa-6NZi2MTJiZu5KuVQwDYJNTnAsYoOsEed=iD9UY33QmOg@mail.gmail.com>
	<0D6867CF-47F7-4C68-A795-17F80DBB8917@opencsw.org>
Message-ID: <x6hal442ou.fsf@opencsw.org>

Dagobert Michelsen <dam at opencsw.org> writes:

> Hi,
>
> Am 21.02.2013 um 10:24 schrieb Maciej (Matchek) Blizi?ski <maciej at opencsw.org>:
>>> Finally, when I'm writing "luxury" I think to what was suggested by Dag,
>>> i.e. when using only the "packaging" target on a system which has
>>> checkpkg activated showing what should be the checkpkg stanza; and this
>>> is not a luxury but a necessity as we have seen.
>> 
>> Some GAR code refactoring will be required around line 1015 of
>> gar.pkg.mk, so that you can either run or display the checkpkg
>> command, and you still keep all how-to-run-checkpkg information in one place.
>> 
>> Dago, is it doable?
>
> The question is what the workflow would be and what should be done. A good thing would IMHO be
>
> - mgar package
> - (Edit some stuff)
> - mgar repackage-CSWjustone
>
> After the individual repackage all packages would be checked together. Checking just one
> package would IMHO be too dangerous. Additionally, I would remove the target
>   package-CSWfoo
> as it indicates it could be explicitly called. Building just one package without the others
> first is also a usecase I would like to avoid.
>
> Peter, would this be acceptable?

In principle yes. However, for cas-* packages the work-flow is:

- package one cas
- upload the resulting cas which is usually architecture neutral
-- 
Peter

From jh at opencsw.org  Mon Feb 25 13:17:04 2013
From: jh at opencsw.org (Jan Holzhueter)
Date: Mon, 25 Feb 2013 13:17:04 +0100
Subject: [csw-maintainers] [csw-pkgrequests] New package request :
 MPlayer and Mencoder and a new version of ffmpeg
In-Reply-To: <201302242328.r1ONSGVB014958@www.opencsw.org>
References: <201302242328.r1ONSGVB014958@www.opencsw.org>
Message-ID: <512B5640.1070105@opencsw.org>

Hi,

I just updated ffmpeg to the lastest version 1.1.3. (Should hit the
mirrors soon)
regarding mplay and memcoder this will probably not happen as this is a
mess to build the last time I tried it. Feel free to join and try to
build it though :)

Greetings
Jan



Am 25.02.13 00:28, schrieb pkgrequests at lists.opencsw.org:
> Dear maintainers,
> 
> A new package request has been received from Mike Young (mailto:TheLaptop at comcast.net). MPlayer and Mencoder and a new version of ffmpeg is requested to be added to our catalog.
> 
> Here is the attached message : 
> 
> 
> _______________________________________________
> pkgrequests mailing list
> pkgrequests at lists.opencsw.org
> https://lists.opencsw.org/mailman/listinfo/pkgrequests
> 


From pfelecan at opencsw.org  Tue Feb 26 13:19:36 2013
From: pfelecan at opencsw.org (pfelecan)
Date: Tue, 26 Feb 2013 13:19:36 +0100
Subject: [csw-maintainers] surprising set of packages when build spans 2 days
Message-ID: <0245410b7b06e1e33a9f4bc5a45e829a@opencsw.org>

I started a build on February 25th which ended on 26th:

    nohup mgar spotless platforms < /dev/null > ~/logs/texlive 2>&1 &

The resulting packages are in ~/staging/build-25.Feb.2013

Here are the first lines of the content as shown by
    ls -1 ~/staging/build-25.Feb.2013

    libkpathsea6-20120701,REV=2013.02.25-SunOS5.10-sparc-CSW.pkg.gz
    libkpathsea6-20120701,REV=2013.02.26-SunOS5.10-i386-CSW.pkg.gz
    libptexenc1-20120701,REV=2013.02.25-SunOS5.10-sparc-CSW.pkg.gz
    libptexenc1-20120701,REV=2013.02.26-SunOS5.10-i386-CSW.pkg.gz
    pdfjam_stub-20120701,REV=2013.02.25-SunOS5.10-all-CSW.pkg.gz
    pdfjam_stub-20120701,REV=2013.02.26-SunOS5.10-all-CSW.pkg.gz
    tetex_stub-20120701,REV=2013.02.25-SunOS5.10-all-CSW.pkg.gz
    tetex_stub-20120701,REV=2013.02.26-SunOS5.10-all-CSW.pkg.gz
    
tex_pdftricks_old_stub-20120701,REV=2013.02.25-SunOS5.10-all-CSW.pkg.gz
    
tex_pdftricks_old_stub-20120701,REV=2013.02.26-SunOS5.10-all-CSW.pkg.gz
    tex_pdftricks_stub-20120701,REV=2013.02.25-SunOS5.10-all-CSW.pkg.gz
    tex_pdftricks_stub-20120701,REV=2013.02.26-SunOS5.10-all-CSW.pkg.gz
    texlive-20120701,REV=2013.02.25-SunOS5.10-all-CSW.pkg.gz
    texlive-20120701,REV=2013.02.26-SunOS5.10-all-CSW.pkg.gz
    texlive_base-20120701,REV=2013.02.25-SunOS5.10-all-CSW.pkg.gz
    texlive_base-20120701,REV=2013.02.26-SunOS5.10-all-CSW.pkg.gz
    
texlive_bibtex_extra-20120701,REV=2013.02.25-SunOS5.10-all-CSW.pkg.gz
    
texlive_bibtex_extra-20120701,REV=2013.02.26-SunOS5.10-all-CSW.pkg.gz
    texlive_binaries-20120701,REV=2013.02.25-SunOS5.10-sparc-CSW.pkg.gz
    texlive_binaries-20120701,REV=2013.02.26-SunOS5.10-i386-CSW.pkg.gz
    texlive_common-20120701,REV=2013.02.25-SunOS5.10-all-CSW.pkg.gz
    texlive_common-20120701,REV=2013.02.26-SunOS5.10-all-CSW.pkg.gz

The sparc specific packages were generated before midnight, the
i386 ones after midnight.

As we can see, all the architecture neutral packages, infix "all",
are duplicated. This is not only a waste of space but also of
time: it means that for each platform they are generated
even though once is enough.

Can this be optimized by generating only once the "all" packages
when using the "platforms" target?

I don't know which is the effect of this on the packages upload
but I'll test it very soon.


From dam at opencsw.org  Tue Feb 26 16:26:49 2013
From: dam at opencsw.org (Dagobert Michelsen)
Date: Tue, 26 Feb 2013 16:26:49 +0100
Subject: [csw-maintainers] surprising set of packages when build spans 2
	days
In-Reply-To: <0245410b7b06e1e33a9f4bc5a45e829a@opencsw.org>
References: <0245410b7b06e1e33a9f4bc5a45e829a@opencsw.org>
Message-ID: <04AEBEEC-D8F7-48A8-9697-980506DA8560@opencsw.org>

Hi Peter,

Am 26.02.2013 um 13:19 schrieb pfelecan <pfelecan at opencsw.org>:
> As we can see, all the architecture neutral packages, infix "all",
> are duplicated. This is not only a waste of space but also of
> time: it means that for each platform they are generated
> even though once is enough.

This is only true if you build both architectures at the same time.
Ideally they should be the same between sparc and i386, so if you
build both sparc and i386 on the same day, yes, it gets rewritten.
It could be excluded from all but the first requested arch, but
up to now it was not an issue.

> Can this be optimized by generating only once the "all" packages
> when using the "platforms" target?
> 
> I don't know which is the effect of this on the packages upload
> but I'll test it very soon.


You will get collisions, so just throw away the packages from one arch
with archall.


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 pfelecan at opencsw.org  Tue Feb 26 19:27:47 2013
From: pfelecan at opencsw.org (Peter FELECAN)
Date: Tue, 26 Feb 2013 19:27:47 +0100
Subject: [csw-maintainers] surprising set of packages when build spans 2
	days
In-Reply-To: <04AEBEEC-D8F7-48A8-9697-980506DA8560@opencsw.org> (Dagobert
	Michelsen's message of "Tue, 26 Feb 2013 16:26:49 +0100")
References: <0245410b7b06e1e33a9f4bc5a45e829a@opencsw.org>
	<04AEBEEC-D8F7-48A8-9697-980506DA8560@opencsw.org>
Message-ID: <x6fw0j0w2k.fsf@opencsw.org>

Dagobert Michelsen <dam at opencsw.org> writes:

> Am 26.02.2013 um 13:19 schrieb pfelecan <pfelecan at opencsw.org>:
>> As we can see, all the architecture neutral packages, infix "all",
>> are duplicated. This is not only a waste of space but also of
>> time: it means that for each platform they are generated
>> even though once is enough.
>
> This is only true if you build both architectures at the same time.

Yes: "platforms" target which is the most frequent use case, isn't it?

> Ideally they should be the same between sparc and i386, so if you
> build both sparc and i386 on the same day, yes, it gets rewritten.

>From the outside they are not the same...

> It could be excluded from all but the first requested arch, but
> up to now it was not an issue.

This is quite simple to test: start before midnight and instrument a
recipe such as to wait until after midnight at the end of the packaging.

>> Can this be optimized by generating only once the "all" packages
>> when using the "platforms" target?
>> 
>> I don't know which is the effect of this on the packages upload
>> but I'll test it very soon.
>
> You will get collisions, so just throw away the packages from one arch
> with archall.

Thanks. I'll remove one set of architecture neutral packages.

-- 
Peter

From dam at opencsw.org  Tue Feb  5 14:13:07 2013
From: dam at opencsw.org (Dagobert Michelsen)
Date: Tue, 05 Feb 2013 13:13:07 -0000
Subject: [csw-maintainers] [buildfarm-announce] The OpenCSW buildfarm is
	available again
Message-ID: <3EBA972D-1E43-43EA-A47F-4D7BCD4E9699@opencsw.org>

Dear buildfarm users,

the OpenCSW buildfarm is available again. Please let me know if you encounter anything
suspicious.


Sorry for the inconvenience

  -- 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

_______________________________________________
buildfarm-announce mailing list
buildfarm-announce at opencsw.org
https://lists.opencsw.org/mailman/listinfo/buildfarm-announce