From buildfarm at lists.opencsw.org Sat Nov 1 23:03:43 2014 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Sat, 1 Nov 2014 23:03:43 +0100 Subject: List of maintainer accounts with activity, over JSON In-Reply-To: References: Message-ID: Hi Maciej, Am 28.10.2014 um 12:10 schrieb Maciej (Matchek) Blizi?ski via buildfarm: > Hi buildfarm admins, > > Is it possible/easy to export, over http in JSON, the list of all active maintainer accounts? We could use it to cross-match the buildfarm account statuses with the CSW database, which is used by the website. This would help us maintain a consistent maintainer status. > > Something like: > > [ > { > "name": "maciej", > "type": "maintainer", > "active": true > }, > { > "name": "somebody", > "type": "maintainer", > "active": false > }, > { > "name": "somebodyelse", > "type": "upstream", > "active": true > } > ] Please try http://buildfarm.opencsw.org/cgi-bin/maintainerstatus This is pretty hacky at the moment, but it is late and I just wanted to get this done. Just let me know if this fits your needs. Best regards -- Dago From buildfarm at lists.opencsw.org Sat Nov 1 23:32:39 2014 From: buildfarm at lists.opencsw.org (Ben Walton via buildfarm) Date: Sat, 01 Nov 2014 22:32:39 +0000 Subject: List of maintainer accounts with activity, over JSON References: Message-ID: Looks pretty good to me. On Sat Nov 01 2014 at 10:03:50 PM Dagobert Michelsen wrote: > Hi Maciej, > > Am 28.10.2014 um 12:10 schrieb Maciej (Matchek) Blizi?ski via buildfarm: > > > Hi buildfarm admins, > > > > Is it possible/easy to export, over http in JSON, the list of all active > maintainer accounts? We could use it to cross-match the buildfarm account > statuses with the CSW database, which is used by the website. This would > help us maintain a consistent maintainer status. > > > > Something like: > > > > [ > > { > > "name": "maciej", > > "type": "maintainer", > > "active": true > > }, > > { > > "name": "somebody", > > "type": "maintainer", > > "active": false > > }, > > { > > "name": "somebodyelse", > > "type": "upstream", > > "active": true > > } > > ] > > Please try > http://buildfarm.opencsw.org/cgi-bin/maintainerstatus > > This is pretty hacky at the moment, but it is late and I just wanted to > get this done. > Just let me know if this fits your needs. > > > Best regards > > -- Dago > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From buildfarm at lists.opencsw.org Sun Nov 2 12:04:00 2014 From: buildfarm at lists.opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?= via buildfarm) Date: Sun, 02 Nov 2014 11:04:00 +0000 Subject: List of maintainer accounts with activity, over JSON References: Message-ID: I'm leaving for vacations very soon, I won't be able to incorporate this into the maintainer status page before I leave. I'll get back to it after the 20th. Ben Walton escreveu no dia Sat Nov 01 2014 at 22:32:53: > Looks pretty good to me. > > On Sat Nov 01 2014 at 10:03:50 PM Dagobert Michelsen > wrote: > >> Hi Maciej, >> >> Am 28.10.2014 um 12:10 schrieb Maciej (Matchek) Blizi?ski via buildfarm: >> >> > Hi buildfarm admins, >> > >> > Is it possible/easy to export, over http in JSON, the list of all >> active maintainer accounts? We could use it to cross-match the buildfarm >> account statuses with the CSW database, which is used by the website. This >> would help us maintain a consistent maintainer status. >> > >> > Something like: >> > >> > [ >> > { >> > "name": "maciej", >> > "type": "maintainer", >> > "active": true >> > }, >> > { >> > "name": "somebody", >> > "type": "maintainer", >> > "active": false >> > }, >> > { >> > "name": "somebodyelse", >> > "type": "upstream", >> > "active": true >> > } >> > ] >> >> Please try >> http://buildfarm.opencsw.org/cgi-bin/maintainerstatus >> >> This is pretty hacky at the moment, but it is late and I just wanted to >> get this done. >> Just let me know if this fits your needs. >> >> >> Best regards >> >> -- Dago >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From buildfarm at lists.opencsw.org Sun Nov 2 12:07:20 2014 From: buildfarm at lists.opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?= via buildfarm) Date: Sun, 02 Nov 2014 11:07:20 +0000 Subject: List of maintainer accounts with activity, over JSON References: Message-ID: I've noticed one detail to correct: Boolean values in JSON should be unquoted: >>> print json.dumps({'a': True}) {"a": true} Maciej (Matchek) Blizi?ski escreveu no dia Sun Nov 02 2014 at 11:03:59: > I'm leaving for vacations very soon, I won't be able to incorporate this > into the maintainer status page before I leave. I'll get back to it after > the 20th. > > Ben Walton escreveu no dia Sat Nov 01 2014 at > 22:32:53: > > Looks pretty good to me. >> >> On Sat Nov 01 2014 at 10:03:50 PM Dagobert Michelsen >> wrote: >> >>> Hi Maciej, >>> >>> Am 28.10.2014 um 12:10 schrieb Maciej (Matchek) Blizi?ski via buildfarm: >>> >>> > Hi buildfarm admins, >>> > >>> > Is it possible/easy to export, over http in JSON, the list of all >>> active maintainer accounts? We could use it to cross-match the buildfarm >>> account statuses with the CSW database, which is used by the website. This >>> would help us maintain a consistent maintainer status. >>> > >>> > Something like: >>> > >>> > [ >>> > { >>> > "name": "maciej", >>> > "type": "maintainer", >>> > "active": true >>> > }, >>> > { >>> > "name": "somebody", >>> > "type": "maintainer", >>> > "active": false >>> > }, >>> > { >>> > "name": "somebodyelse", >>> > "type": "upstream", >>> > "active": true >>> > } >>> > ] >>> >>> Please try >>> http://buildfarm.opencsw.org/cgi-bin/maintainerstatus >>> >>> This is pretty hacky at the moment, but it is late and I just wanted to >>> get this done. >>> Just let me know if this fits your needs. >>> >>> >>> Best regards >>> >>> -- Dago >>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From buildfarm at lists.opencsw.org Sun Nov 2 17:24:04 2014 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Sun, 2 Nov 2014 17:24:04 +0100 Subject: List of maintainer accounts with activity, over JSON In-Reply-To: References: Message-ID: <2048263A-8221-4884-8D80-1804979A62F5@opencsw.org> Hi Maciej, > Am 02.11.2014 um 12:07 schrieb Maciej (Matchek) Blizi?ski : > > I've noticed one detail to correct: Boolean values in JSON should be unquoted: > >>>> print json.dumps({'a': True}) > {"a": true} Ah yes, this was an artifact of the Perl JSON implementation which requires a specific singleton for booleans. Fixed now. Best regards ? Dago > > > Maciej (Matchek) Blizi?ski escreveu no dia Sun Nov 02 2014 at 11:03:59: > I'm leaving for vacations very soon, I won't be able to incorporate this into the maintainer status page before I leave. I'll get back to it after the 20th. > > Ben Walton escreveu no dia Sat Nov 01 2014 at 22:32:53: > > Looks pretty good to me. > > On Sat Nov 01 2014 at 10:03:50 PM Dagobert Michelsen wrote: > Hi Maciej, > > Am 28.10.2014 um 12:10 schrieb Maciej (Matchek) Blizi?ski via buildfarm: > >> Hi buildfarm admins, >> >> Is it possible/easy to export, over http in JSON, the list of all active maintainer accounts? We could use it to cross-match the buildfarm account statuses with the CSW database, which is used by the website. This would help us maintain a consistent maintainer status. >> >> Something like: >> >> [ >> { >> "name": "maciej", >> "type": "maintainer", >> "active": true >> }, >> { >> "name": "somebody", >> "type": "maintainer", >> "active": false >> }, >> { >> "name": "somebodyelse", >> "type": "upstream", >> "active": true >> } >> ] > > Please try > http://buildfarm.opencsw.org/cgi-bin/maintainerstatus > > This is pretty hacky at the moment, but it is late and I just wanted to get this done. > Just let me know if this fits your needs. > > > 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 buildfarm at lists.opencsw.org Sun Nov 2 17:23:43 2014 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Sun, 2 Nov 2014 17:23:43 +0100 Subject: List of maintainer accounts with activity, over JSON In-Reply-To: References: Message-ID: <4F770DAE-3073-4661-A6A4-FC6B643C7F23@opencsw.org> Hi Maciej, > Am 02.11.2014 um 12:07 schrieb Maciej (Matchek) Blizi?ski : > > I've noticed one detail to correct: Boolean values in JSON should be unquoted: > >>>> print json.dumps({'a': True}) > {"a": true} Ah yes, this was an artifact of the Perl JSON implementation which requires a specific singleton for booleans. Fixed now. Best regards ? Dago > > > Maciej (Matchek) Blizi?ski escreveu no dia Sun Nov 02 2014 at 11:03:59: > I'm leaving for vacations very soon, I won't be able to incorporate this into the maintainer status page before I leave. I'll get back to it after the 20th. > > Ben Walton escreveu no dia Sat Nov 01 2014 at 22:32:53: > > Looks pretty good to me. > > On Sat Nov 01 2014 at 10:03:50 PM Dagobert Michelsen wrote: > Hi Maciej, > > Am 28.10.2014 um 12:10 schrieb Maciej (Matchek) Blizi?ski via buildfarm: > >> Hi buildfarm admins, >> >> Is it possible/easy to export, over http in JSON, the list of all active maintainer accounts? We could use it to cross-match the buildfarm account statuses with the CSW database, which is used by the website. This would help us maintain a consistent maintainer status. >> >> Something like: >> >> [ >> { >> "name": "maciej", >> "type": "maintainer", >> "active": true >> }, >> { >> "name": "somebody", >> "type": "maintainer", >> "active": false >> }, >> { >> "name": "somebodyelse", >> "type": "upstream", >> "active": true >> } >> ] > > Please try > http://buildfarm.opencsw.org/cgi-bin/maintainerstatus > > This is pretty hacky at the moment, but it is late and I just wanted to get this done. > Just let me know if this fits your needs. > > > 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 buildfarm at lists.opencsw.org Sun Nov 2 17:24:20 2014 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Sun, 2 Nov 2014 17:24:20 +0100 Subject: List of maintainer accounts with activity, over JSON In-Reply-To: References: Message-ID: Hi Maciej, > Am 02.11.2014 um 12:07 schrieb Maciej (Matchek) Blizi?ski : > > I've noticed one detail to correct: Boolean values in JSON should be unquoted: > >>>> print json.dumps({'a': True}) > {"a": true} Ah yes, this was an artifact of the Perl JSON implementation which requires a specific singleton for booleans. Fixed now. Best regards ? Dago > > > Maciej (Matchek) Blizi?ski escreveu no dia Sun Nov 02 2014 at 11:03:59: > I'm leaving for vacations very soon, I won't be able to incorporate this into the maintainer status page before I leave. I'll get back to it after the 20th. > > Ben Walton escreveu no dia Sat Nov 01 2014 at 22:32:53: > > Looks pretty good to me. > > On Sat Nov 01 2014 at 10:03:50 PM Dagobert Michelsen wrote: > Hi Maciej, > > Am 28.10.2014 um 12:10 schrieb Maciej (Matchek) Blizi?ski via buildfarm: > >> Hi buildfarm admins, >> >> Is it possible/easy to export, over http in JSON, the list of all active maintainer accounts? We could use it to cross-match the buildfarm account statuses with the CSW database, which is used by the website. This would help us maintain a consistent maintainer status. >> >> Something like: >> >> [ >> { >> "name": "maciej", >> "type": "maintainer", >> "active": true >> }, >> { >> "name": "somebody", >> "type": "maintainer", >> "active": false >> }, >> { >> "name": "somebodyelse", >> "type": "upstream", >> "active": true >> } >> ] > > Please try > http://buildfarm.opencsw.org/cgi-bin/maintainerstatus > > This is pretty hacky at the moment, but it is late and I just wanted to get this done. > Just let me know if this fits your needs. > > > 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 buildfarm at lists.opencsw.org Tue Nov 4 21:37:49 2014 From: buildfarm at lists.opencsw.org (Peter Bonivart via buildfarm) Date: Tue, 4 Nov 2014 21:37:49 +0100 Subject: Please install CSWpm-test-most Message-ID: Thanks. From buildfarm at lists.opencsw.org Tue Nov 4 21:40:05 2014 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Tue, 4 Nov 2014 20:40:05 +0000 Subject: Please install CSWpm-test-most In-Reply-To: References: Message-ID: <906DBEC6-679D-4700-8BF0-347352F629FC@opencsw.org> Hi Peter, > Am 04.11.2014 um 20:37 schrieb Peter Bonivart via buildfarm : > > Thanks. Done. Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Tue Nov 4 22:05:06 2014 From: buildfarm at lists.opencsw.org (Peter Bonivart via buildfarm) Date: Tue, 4 Nov 2014 22:05:06 +0100 Subject: Please install pm_hash_merge_simple Message-ID: No rush. :) Thanks. From buildfarm at lists.opencsw.org Tue Nov 4 22:09:52 2014 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Tue, 4 Nov 2014 21:09:52 +0000 Subject: Please install pm_hash_merge_simple In-Reply-To: References: Message-ID: Hi Peter, > Am 04.11.2014 um 21:05 schrieb Peter Bonivart via buildfarm : > > No rush. :) Thanks. Got distracted by a movie :-) Done. Bets regards ? DAgo -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Sun Nov 9 10:39:20 2014 From: buildfarm at lists.opencsw.org (Toni Schmidbauer via buildfarm) Date: Sun, 09 Nov 2014 10:39:20 +0100 Subject: [REQUEST] ruby20 / augeas on buildfarm Message-ID: <86h9y8aehf.fsf@opencsw.org> hi, finally i think i've got a working ruby20 package. to move puppet3 to ruby20 i would like to request the installation of ruby20 on the buildfarm. it uses alternatives so installation should be possible in parallel with ruby18. furthermore i would also need the installation of an updated augeas package (1.2.0), so i can also move rubyaugeas to ruby20. the packages can be found at http://buildfarm.opencsw.org/opencsw/experimental/tosmi/ i tried to upload the packages to the unstable catalog but got the following error messages: tosmi at login [login]:~/staging/build-08.Nov.2014 > csw-upload-pkg ruby20-2.0.0p594,REV=2014.11.08-SunOS5.10-sparc-CSW.pkg.gz /opt/csw/bin/csw-upload-pkg is a wrapper, running /home/tosmi/opencsw/.buildsys/v2/bin/csw-upload-pkg ruby20-2.0.0p594,REV=2014.11.08-SunOS5.10-sparc-CSW.pkg.gz There is a problem with the presented file list. * CheckpkgTag(None, 'i386-SunOS5.10-missing', 'ruby20') building the packages with mgar on the buildfarm worked without any checkpkg errors... thanks for your help toni From buildfarm at lists.opencsw.org Sun Nov 9 12:08:55 2014 From: buildfarm at lists.opencsw.org (Peter Bonivart via buildfarm) Date: Sun, 9 Nov 2014 12:08:55 +0100 Subject: [REQUEST] ruby20 / augeas on buildfarm In-Reply-To: <86h9y8aehf.fsf@opencsw.org> References: <86h9y8aehf.fsf@opencsw.org> Message-ID: On Sun, Nov 9, 2014 at 10:39 AM, Toni Schmidbauer via buildfarm wrote: > tosmi at login [login]:~/staging/build-08.Nov.2014 > csw-upload-pkg ruby20-2.0.0p594,REV=2014.11.08-SunOS5.10-sparc-CSW.pkg.gz > /opt/csw/bin/csw-upload-pkg is a wrapper, running /home/tosmi/opencsw/.buildsys/v2/bin/csw-upload-pkg > ruby20-2.0.0p594,REV=2014.11.08-SunOS5.10-sparc-CSW.pkg.gz > There is a problem with the presented file list. > * CheckpkgTag(None, 'i386-SunOS5.10-missing', 'ruby20') Upload both architectures at once, not just Sparc as above. When they have hit the mirrors they can be installed on the build servers. From buildfarm at lists.opencsw.org Sun Nov 9 22:44:49 2014 From: buildfarm at lists.opencsw.org (Toni Schmidbauer via buildfarm) Date: Sun, 09 Nov 2014 22:44:49 +0100 Subject: [REQUEST] ruby20 / augeas on buildfarm In-Reply-To: (Peter Bonivart's message of "Sun, 9 Nov 2014 12:08:55 +0100") References: <86h9y8aehf.fsf@opencsw.org> Message-ID: <86mw8082we.fsf@opencsw.org> thanks for the hint, i've now uploaded the ruby20 and augeas packages. one more question about the augeas package: the updated package will for sure break the current ruby-augeas module. so after uploading version 1.2.0 to unstable augeas will no longer work from within puppet. but i plan to update puppet3 asap... should i send an email about this fact to the users ml? or is this ok, as it's called unstable... thanks toni From buildfarm at lists.opencsw.org Sun Nov 9 22:56:27 2014 From: buildfarm at lists.opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?= via buildfarm) Date: Sun, 09 Nov 2014 21:56:27 +0000 Subject: [REQUEST] ruby20 / augeas on buildfarm References: <86h9y8aehf.fsf@opencsw.org> <86mw8082we.fsf@opencsw.org> Message-ID: Yes, I think it's okay, if for a short time. Notifying users is a good thing, people will refrain from updating for a few days. In similar cases I used to test my intermediate builds on a private build host. I would build the ruby20 package, install it there (without releasing) and work on the dependent packages. Once I got them to build, I would repeat the process on the buildfarm. Maciej A dom, 9/11/2014, 22:44, Toni Schmidbauer via buildfarm < buildfarm at lists.opencsw.org> escreveu: > thanks for the hint, i've now uploaded the ruby20 and augeas packages. > > one more question about the augeas package: > > the updated package will for sure break the current ruby-augeas module. > so after uploading version 1.2.0 to unstable augeas will no longer work > from within puppet. but i plan to update puppet3 asap... > > should i send an email about this fact to the users ml? or is this ok, > as it's called unstable... > > thanks > toni > -------------- next part -------------- An HTML attachment was scrubbed... URL: From buildfarm at lists.opencsw.org Wed Nov 12 23:00:16 2014 From: buildfarm at lists.opencsw.org (Toni Schmidbauer via buildfarm) Date: Wed, 12 Nov 2014 23:00:16 +0100 Subject: please install libaugeas_dev, hiera and facter Message-ID: <861tp82i6n.fsf@opencsw.org> hi, i've just uploaded updated versions of augeas and facter and a new package hiera. as these packages are required to build puppet3, i would kindly ask to to install libaugeas_dev hiera facter to the buildfarm. thanks for your help toni From buildfarm at lists.opencsw.org Thu Nov 13 09:00:07 2014 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Thu, 13 Nov 2014 09:00:07 +0100 Subject: please install libaugeas_dev, hiera and facter In-Reply-To: <861tp82i6n.fsf@opencsw.org> References: <861tp82i6n.fsf@opencsw.org> Message-ID: <456EA123-1EE1-41C6-9625-1986D64A8A8F@opencsw.org> Hi Toni, > Am 12.11.2014 um 23:00 schrieb Toni Schmidbauer via buildfarm : > > hi, > > i've just uploaded updated versions of augeas and facter and a new > package hiera. as these packages are required to build puppet3, i would > kindly ask to to install > > libaugeas_dev > hiera > facter > > to the buildfarm. Done. Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Thu Nov 13 21:30:33 2014 From: buildfarm at lists.opencsw.org (Toni Schmidbauer via buildfarm) Date: Thu, 13 Nov 2014 21:30:33 +0100 Subject: [PATCH] add CSWruby20 to dependency_checks.py Message-ID: <86sihm268m.fsf@opencsw.org> hi, because we now have ruby20 in the unstable catalog i think it would make sense to add CSWruby20 to the dependency checks to avoid unnecessary checkpkg errors. i came up with the following patch, which is untested and from a guy with limited (no) knowledge about gar :-) thanks toni Index: lib/python/dependency_checks.py =================================================================== --- lib/python/dependency_checks.py (revision 24235) +++ lib/python/dependency_checks.py (working copy) @@ -40,7 +40,7 @@ # (u"CSWpython27",)), # (r"/?opt/csw/lib/python3\.3/(site-packages|lib-dynload)/.+\.py$", # (u"CSWpython33",)), - (r".*\.rb$", (u"CSWruby", u"CSWruby18", u"CSWruby191",u"CSWlibruby1-9-1-1")), + (r".*\.rb$", (u"CSWruby", u"CSWruby18", u"CSWruby191",u"CSWlibruby1-9-1-1", u"CSWruby20")), (r".*\.elc?$", (u"CSWemacs-common",)), (r"/opt/csw/apache2/", (u"CSWapache2",)), ) From buildfarm at lists.opencsw.org Fri Nov 14 09:34:19 2014 From: buildfarm at lists.opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?= via buildfarm) Date: Fri, 14 Nov 2014 08:34:19 +0000 Subject: [PATCH] add CSWruby20 to dependency_checks.py In-Reply-To: <86sihm268m.fsf@opencsw.org> References: <86sihm268m.fsf@opencsw.org> Message-ID: It makes sense. You could try thinking of a smarter regex, so that it would correctly match against Ruby versions. For example, can you match by directory name? -------------- next part -------------- An HTML attachment was scrubbed... URL: From buildfarm at lists.opencsw.org Tue Nov 25 15:02:01 2014 From: buildfarm at lists.opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?= via buildfarm) Date: Tue, 25 Nov 2014 14:02:01 +0000 Subject: Catalog auto-integration is stuck Message-ID: http://buildfarm.opencsw.org/package-promotions/promote-packages.html reads: unstable ? munich report for 2014-11-20 05:20:45.556551 +0100 CET Today is the 25th, so something got stuck. Could anybody look? This is triggered from cron on the web host. -------------- next part -------------- An HTML attachment was scrubbed... URL: From buildfarm at lists.opencsw.org Tue Nov 25 15:07:08 2014 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Tue, 25 Nov 2014 15:07:08 +0100 Subject: Catalog auto-integration is stuck In-Reply-To: References: Message-ID: <2383C2B0-5504-4035-A520-2CFC08A3EC8C@opencsw.org> Hi Maciej, > Am 25.11.2014 um 15:02 schrieb Maciej (Matchek) Blizi?ski via buildfarm : > > http://buildfarm.opencsw.org/package-promotions/promote-packages.html > > reads: > unstable ? munich report for 2014-11-20 05:20:45.556551 +0100 CET > > Today is the 25th, so something got stuck. Could anybody look? This is triggered from cron on the web host. The catalog generation log looks ok: http://buildfarm.opencsw.org/catalog-generation.log I haven?t touched /etc/opt/csw/releases/auth/web, so I am unsure if this is a real error or not. Best regards ?Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Tue Nov 25 15:20:31 2014 From: buildfarm at lists.opencsw.org (Jan Holzhueter via buildfarm) Date: Tue, 25 Nov 2014 15:20:31 +0100 Subject: Catalog auto-integration is stuck In-Reply-To: References: Message-ID: <5474902F.1030804@opencsw.org> Am 25.11.14 um 15:02 schrieb Maciej (Matchek) Blizi?ski via buildfarm: > http://buildfarm.opencsw.org/package-promotions/promote-packages.html > > reads: > unstable ? munich report for 2014-11-20 05:20:45.556551 +0100 CET > > Today is the 25th, so something got stuck. Could anybody look? This is > triggered from cron on the web host. Looks you you updated ls -alrth /home/web/bin/promote-packages -rwxr-xr-x 1 web web 395K Nov 20 18:10 /home/web/bin/promote-packages which now needs libgo.5 which is not yet installed on web. Should I install it? Greetings Jan From buildfarm at lists.opencsw.org Tue Nov 25 15:21:57 2014 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Tue, 25 Nov 2014 15:21:57 +0100 Subject: Catalog auto-integration is stuck In-Reply-To: <5474902F.1030804@opencsw.org> References: <5474902F.1030804@opencsw.org> Message-ID: <4657842C-14B5-4DC6-A7B6-15437249AADB@opencsw.org> > Am 25.11.2014 um 15:20 schrieb Jan Holzhueter via buildfarm : > > > > Am 25.11.14 um 15:02 schrieb Maciej (Matchek) Blizi?ski via buildfarm: >> http://buildfarm.opencsw.org/package-promotions/promote-packages.html >> >> reads: >> unstable ? munich report for 2014-11-20 05:20:45.556551 +0100 CET >> >> Today is the 25th, so something got stuck. Could anybody look? This is >> triggered from cron on the web host. > > Looks you you updated > ls -alrth /home/web/bin/promote-packages > -rwxr-xr-x 1 web web 395K Nov 20 18:10 > /home/web/bin/promote-packages > > which now needs libgo.5 > which is not yet installed on web. > > Should I install it? Yes please. I can?t remember updating web and I vaguely remember GO was broken in GCC 4.9.x Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Tue Nov 25 16:02:04 2014 From: buildfarm at lists.opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?= via buildfarm) Date: Tue, 25 Nov 2014 15:02:04 +0000 Subject: Catalog auto-integration is stuck References: <5474902F.1030804@opencsw.org> <4657842C-14B5-4DC6-A7B6-15437249AADB@opencsw.org> Message-ID: Right, we might need to recompile thus binary with the older gccgo compiler. Do we have it installed anywhere? A ter, 25/11/2014, 14:22, Dagobert Michelsen escreveu: > > > Am 25.11.2014 um 15:20 schrieb Jan Holzhueter via buildfarm < > buildfarm at lists.opencsw.org>: > > > > > > > > Am 25.11.14 um 15:02 schrieb Maciej (Matchek) Blizi?ski via buildfarm: > >> http://buildfarm.opencsw.org/package-promotions/promote-packages.html > >> > >> reads: > >> unstable ? munich report for 2014-11-20 05:20:45.556551 +0100 CET > >> > >> Today is the 25th, so something got stuck. Could anybody look? This is > >> triggered from cron on the web host. > > > > Looks you you updated > > ls -alrth /home/web/bin/promote-packages > > -rwxr-xr-x 1 web web 395K Nov 20 18:10 > > /home/web/bin/promote-packages > > > > which now needs libgo.5 > > which is not yet installed on web. > > > > Should I install it? > > Yes please. I can?t remember updating web and I vaguely remember GO was > broken in > GCC 4.9.x > > > Best regards > > ? Dago > > -- > "You don't become great by trying to be great, you become great by wanting > to do something, > and then doing it so hard that you become great in the process." - xkcd > #896 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From buildfarm at lists.opencsw.org Tue Nov 25 16:41:19 2014 From: buildfarm at lists.opencsw.org (Jan Holzhueter via buildfarm) Date: Tue, 25 Nov 2014 16:41:19 +0100 Subject: Catalog auto-integration is stuck In-Reply-To: References: <5474902F.1030804@opencsw.org> <4657842C-14B5-4DC6-A7B6-15437249AADB@opencsw.org> Message-ID: <5474A31F.8070505@opencsw.org> Am 25.11.14 um 16:02 schrieb Maciej (Matchek) Blizi?ski via buildfarm: > Right, we might need to recompile thus binary with the older gccgo > compiler. Do we have it installed anywhere? > I installed libgo.5 we will see if it runs tonight. otherwise yes we probably need to recompile I guess. Don't know though if we have it installed. Greetings Jan From buildfarm at lists.opencsw.org Tue Nov 25 17:02:23 2014 From: buildfarm at lists.opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?= via buildfarm) Date: Tue, 25 Nov 2014 16:02:23 +0000 Subject: Catalog auto-integration is stuck References: <5474902F.1030804@opencsw.org> <4657842C-14B5-4DC6-A7B6-15437249AADB@opencsw.org> <5474A31F.8070505@opencsw.org> Message-ID: It will likely get stuck and/or crash. I think I recompiled it on our test hosts the last time. A ter, 25/11/2014, 15:41, Jan Holzhueter escreveu: > Am 25.11.14 um 16:02 schrieb Maciej (Matchek) Blizi?ski via buildfarm: > > Right, we might need to recompile thus binary with the older gccgo > > compiler. Do we have it installed anywhere? > > > > I installed libgo.5 we will see if it runs tonight. > otherwise yes we probably need to recompile I guess. Don't know though > if we have it installed. > > Greetings > Jan > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From buildfarm at lists.opencsw.org Thu Nov 27 14:39:19 2014 From: buildfarm at lists.opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?= via buildfarm) Date: Thu, 27 Nov 2014 13:39:19 +0000 Subject: Catalog auto-integration is stuck References: <5474902F.1030804@opencsw.org> <4657842C-14B5-4DC6-A7B6-15437249AADB@opencsw.org> <5474A31F.8070505@opencsw.org> <5474AA45.8010701@opencsw.org> Message-ID: What needs to be done: - install gcc 4.8.x on a sparc box - in the gar/v2/go directory run "gmake bin/package-promotions" - copy the resulting binary to web at web:/home/web/bin Would anyone like to try it? I can do it, it's better if somebody else does it to reduce the bus factor. Maciej Jan Holzhueter escreveu no dia Tue Nov 25 2014 at 4:11:57 PM: > Am 25.11.14 um 17:02 schrieb Maciej (Matchek) Blizi?ski: > > It will likely get stuck and/or crash. I think I recompiled it on our > > test hosts the last time. > > ok die try it: > > 2014/11/25 16:08:57 src/promote-packages/promote-packages.go:1049: > Continuing to process changes for Cache-Cache > caught signal while mallocing: 11 > fatal error: caught signal while mallocing > [signal 0xb code=0x1 addr=0x10] > > runtime stack: > > :0 > > :0 > > :0 > > :0 > > :0 > > :0 > > :0 > > :0 > > :0 > > :0 > > :0 > > :0 > > :0 > main > > /home/maciej/src/opencsw/pkg/gcc4/trunk/work/solaris10- > sparc/build-isa-sparcv8plus/gcc-4.9.0/libgo/runtime/go-main.c:43 > > :0 > > goroutine 1 [select]: > main.RestRequest > src/promote-packages/promote-packages.go:375 > main.Perform.N21_main.catalogOperation > src/promote-packages/promote-packages.go:393 > main.maybeApplyChanges > src/promote-packages/promote-packages.go:1053 > main.main > src/promote-packages/promote-packages.go:1107 > > goroutine 88 [IO wait]: > > goroutine 89 [select]: > > goroutine 45 [finalizer wait]: > zsh: 24902 exit 2 /home/web/bin/promote_to_testing.sh > > > so yes it exploded. > disabled cron for now. > > Greetings > Jan > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From buildfarm at lists.opencsw.org Sat Nov 29 12:49:24 2014 From: buildfarm at lists.opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?= via buildfarm) Date: Sat, 29 Nov 2014 11:49:24 +0000 Subject: Catalog auto-integration is stuck References: <5474902F.1030804@opencsw.org> <4657842C-14B5-4DC6-A7B6-15437249AADB@opencsw.org> <5474A31F.8070505@opencsw.org> <5474AA45.8010701@opencsw.org> Message-ID: No takers - I did it myself, it should be running again. I've installed GCC 4.8.2 from allpkgs on testing10s, built a binary there and copied to web at web:bin Maciej (Matchek) Blizi?ski escreveu no dia Thu Nov 27 2014 at 13:39:18: > What needs to be done: > > - install gcc 4.8.x on a sparc box > - in the gar/v2/go directory run "gmake bin/package-promotions" > - copy the resulting binary to web at web:/home/web/bin > > Would anyone like to try it? I can do it, it's better if somebody else > does it to reduce the bus factor. > > Maciej > > Jan Holzhueter escreveu no dia Tue Nov 25 2014 at > 4:11:57 PM: > > Am 25.11.14 um 17:02 schrieb Maciej (Matchek) Blizi?ski: >> > It will likely get stuck and/or crash. I think I recompiled it on our >> > test hosts the last time. >> >> ok die try it: >> >> 2014/11/25 16:08:57 src/promote-packages/promote-packages.go:1049: >> Continuing to process changes for Cache-Cache >> caught signal while mallocing: 11 >> fatal error: caught signal while mallocing >> [signal 0xb code=0x1 addr=0x10] >> >> runtime stack: >> >> :0 >> >> :0 >> >> :0 >> >> :0 >> >> :0 >> >> :0 >> >> :0 >> >> :0 >> >> :0 >> >> :0 >> >> :0 >> >> :0 >> >> :0 >> main >> >> /home/maciej/src/opencsw/pkg/gcc4/trunk/work/solaris10-sparc >> /build-isa-sparcv8plus/gcc-4.9.0/libgo/runtime/go-main.c:43 >> >> :0 >> >> goroutine 1 [select]: >> main.RestRequest >> src/promote-packages/promote-packages.go:375 >> main.Perform.N21_main.catalogOperation >> src/promote-packages/promote-packages.go:393 >> main.maybeApplyChanges >> src/promote-packages/promote-packages.go:1053 >> main.main >> src/promote-packages/promote-packages.go:1107 >> >> goroutine 88 [IO wait]: >> >> goroutine 89 [select]: >> >> goroutine 45 [finalizer wait]: >> zsh: 24902 exit 2 /home/web/bin/promote_to_testing.sh >> >> >> so yes it exploded. >> disabled cron for now. >> >> Greetings >> Jan >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From buildfarm at lists.opencsw.org Sun Nov 30 13:40:16 2014 From: buildfarm at lists.opencsw.org (Dagobert Michelsen via buildfarm) Date: Sun, 30 Nov 2014 13:40:16 +0100 Subject: Catalog auto-integration is stuck In-Reply-To: References: <5474902F.1030804@opencsw.org> <4657842C-14B5-4DC6-A7B6-15437249AADB@opencsw.org> <5474A31F.8070505@opencsw.org> <5474AA45.8010701@opencsw.org> Message-ID: <226741D7-0D71-4307-B3BA-CC2B64AAA97D@opencsw.org> Hi Maciej, > Am 29.11.2014 um 12:49 schrieb Maciej (Matchek) Blizi?ski via buildfarm : > > No takers - I did it myself, it should be running again. I had a horrible week, sorry for not jumping in although I wanted to get more hands on the farm infra. Best regards ? Dago > I've installed GCC 4.8.2 from allpkgs on testing10s, built a binary there and copied to web at web:bin > Maciej (Matchek) Blizi?ski > escreveu no dia Thu Nov 27 2014 at 13:39:18: > What needs to be done: > > - install gcc 4.8.x on a sparc box > - in the gar/v2/go directory run "gmake bin/package-promotions" > - copy the resulting binary to web at web:/home/web/bin > > Would anyone like to try it? I can do it, it's better if somebody else does it to reduce the bus factor. > > Maciej > > Jan Holzhueter > escreveu no dia Tue Nov 25 2014 at 4:11:57 PM: > > Am 25.11.14 um 17:02 schrieb Maciej (Matchek) Blizi?ski: > > It will likely get stuck and/or crash. I think I recompiled it on our > > test hosts the last time. > > ok die try it: > > 2014/11/25 16:08:57 src/promote-packages/promote-packages.go:1049: > Continuing to process changes for Cache-Cache > caught signal while mallocing: 11 > fatal error: caught signal while mallocing > [signal 0xb code=0x1 addr=0x10] > > runtime stack: > > :0 > > :0 > > :0 > > :0 > > :0 > > :0 > > :0 > > :0 > > :0 > > :0 > > :0 > > :0 > > :0 > main > > /home/maciej/src/opencsw/pkg/gcc4/trunk/work/solaris10-sparc/build-isa-sparcv8plus/gcc-4.9.0/libgo/runtime/go-main.c:43 > > :0 > > goroutine 1 [select]: > main.RestRequest > src/promote-packages/promote-packages.go:375 > main.Perform.N21_main.catalogOperation > src/promote-packages/promote-packages.go:393 > main.maybeApplyChanges > src/promote-packages/promote-packages.go:1053 > main.main > src/promote-packages/promote-packages.go:1107 > > goroutine 88 [IO wait]: > > goroutine 89 [select]: > > goroutine 45 [finalizer wait]: > zsh: 24902 exit 2 /home/web/bin/promote_to_testing.sh > > > so yes it exploded. > disabled cron for now. > > Greetings > Jan > -- "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: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2418 bytes Desc: not available URL: From buildfarm at lists.opencsw.org Sun Nov 30 18:14:58 2014 From: buildfarm at lists.opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?= via buildfarm) Date: Sun, 30 Nov 2014 17:14:58 +0000 Subject: [CSW Notice] Catalog Signature Daemon has been reset In-Reply-To: <201411301713.sAUHDsfk026912@cswsign.bo.opencsw.org> References: <201411301713.sAUHDsfk026912@cswsign.bo.opencsw.org> Message-ID: I've re-entered the password. 2014-11-30 17:13 GMT+00:00 CSW Catalog Signing Daemon : > A human has intervened and restored the passphrase.