From dam at opencsw.org Sat Sep 4 21:22:21 2010 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 4 Sep 2010 21:22:21 +0200 Subject: [buildfarm-announce] Hardware maintenance tomorrow Message-ID: Fellow buildfarm users, tomorrow will be a downtime of the buildfarm for hardware maintenance. It will start in roughly 12 hours (about 10 AM MET) and hopefully last a few hours. Sorry for the inconvenience -- Dago PS: If you want to know what is going on please read on! Two weeks ago I had a hang of the external storage array (16 x 120 GB SATA-to-FC) when I tried to replace a failed disk. After powercycling the array and changing the disk I kept getting parity errors from ZFS from the array without bad blocks from a disk, which is a bad sign, typically a memory problem on the array controller. Tomorrow the array will be replaced by 4 x 1 TB 2,5" SATA internal disks. From dam at opencsw.org Sun Sep 5 15:40:20 2010 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 5 Sep 2010 15:40:20 +0200 Subject: [buildfarm-announce] Buildfarm is available again Message-ID: Hi, the buildfarm is available again. The resilvering will take another day, so please take that into consideration if you measure disk performance. Please let me know if you encounter anything strange. Sorry for the inconvenience -- Dago From dam at opencsw.org Fri Sep 10 15:51:51 2010 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 10 Sep 2010 15:51:51 +0200 Subject: [buildfarm-announce] Again downtime of OpenCSW buildfarm on monday Message-ID: <03F6BCBF-4613-4D00-A6BF-71F42CBDC234@opencsw.org> Fellow buildfarm users, I am very unhappy to be forced to announce another downtime of the buildfarm on the evening of monday, 13th (3 days from now). The homedirectories on the new local disks is too slow due to the I/O of specific buildjobs, so we will try some hopefully faster configuration and update to Solaris 10u9 during this opportunity. Sorry for the inconvenience -- Dago From dam at opencsw.org Mon Sep 13 22:43:59 2010 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 13 Sep 2010 22:43:59 +0200 Subject: [buildfarm-announce] Buildfarm update almost finished Message-ID: <26AE7C9B-AD96-4E8C-B450-882A3F58E3AA@opencsw.org> Hi, the buildfarm update is mostly done. There are still some patches being applied for Solaris 9 which may take some more hours and will require a reboot of the zones tomorrow. I'll keep you informed. Best regards -- Dago From dam at opencsw.org Tue Sep 14 09:51:31 2010 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 14 Sep 2010 09:51:31 +0200 Subject: [buildfarm-announce] Buildfarm update finally finished Message-ID: Fellow buildfarm users, the update is now finally done and the farm should be fully usable again. Please let me know if you encounter anything suspicious. Sorry for the inconvenience -- Dago From dam at opencsw.org Sat Sep 18 07:46:22 2010 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 18 Sep 2010 07:46:22 +0200 Subject: [buildfarm-announce] Fwd: [csw-buildfarm] Latest libffi/libffidevel on build servers References: <1284766806-sup-3533@pinkfloyd.chass.utoronto.ca> Message-ID: <5DFBCD19-C953-4DB1-8B44-F2AA6803F12D@opencsw.org> Hi Jens, Anfang der weitergeleiteten E-Mail: >> I'm trying to build the latest version of Ruby (1.9.2 p0) and am >> running into a compiler issue related to libffi headers. The fix >> appears to be in libffi 3.0.9 (which is in svn), but the build >> servers still have 3.0.8. Would it be possible to update the build >> servers to the latest libffi/libffidevel (3.0.9)? > > The policy is that the buildfarm (current* boxen) only get packages > available from the current catalog. There are testing* boxen that we > can use to put things from experimental into play when required. > > When you say that 3.0.9 is in svn, do that mean there is an updated > GAR recipe for it? If so, the best approach is to ping the > maintainer[1] > for an update and if there's no active maintainer, take it over! :) > > HTH. > -Ben > > [1] In this case, Mike Watters is on 'sabbatical' so you'd be best to > roll the updated package yourself. As Roger already built libffi 3.0.9 and put it into testing I suggest you respin the package, we install it on a testing-machine and you release it after verification. Then it gets installed on the current* machines and you can proceed. Best regards -- Dago