2010/1/1 Ed Bartosh <bart...@gmail.com>:
> 2010/1/1 Jeff Moe <m...@blagblagblag.org>:
>> On Friday 01 January 2010 11:12:47 Ed Bartosh wrote:
>>> 2010/1/1 Jeremiah Foster <jerem...@jeremiahfoster.com>:
>>> > On Jan 1, 2010, at 15:00, Ed Bartosh wrote:
>>> >> 2010/1/1 Andrew Flegg <and...@bleb.org>:
>>> >>> Hi,
>>> >>>
>>> >>> Attempting to upload a new version of vim to the Fremantle
>>> >>> auto-builder, I get the following failure:
>>> >>>
>>> >>>
>>> >>> https://garage.maemo.org/builder/fremantle/vim_7.2-0maemo6/armel.root.l
>>> >>>og.FAILED.txt
>>> >>
>>> >> Should be fixed now:
>>> >> https://garage.maemo.org/builder/fremantle/vim_7.2-0maemo6/ Thanks for
>>> >> pointing out to this.
>>> >>
>>> >> Somebody's changed sbdmock configuration on the build host. I don't
>>> >> know why, because it was working just fine before.
>>> >>
>>> >> This reminds me aphorisms like 'Too many cooks spoil the broth' or
>>> >> 'Many commanders sink the ship". I like better Russian one 'Seven
>>> >> babysitters have a child without eye'. Autobuilder reminds me that
>>> >> child sometimes.
>>> >
>>> > Funny, I was thinking the exact opposite. If more people had access, then
>>> > more than one person could fix it.
>>>
>>> I doubt that. What I can see is that more people can break it.
>>> If you need a proof - give everyone root access to that box :)
>>
>> Starting with me.  :)
>>
>> Though I must say things seem down an awfully lot and we just sit around
>> waiting for someone to fix it. How does Fedora do it? I imagine they have a
>> number of people with access.
>>
> OK, let's look at this particular case. Autobuilder was broken for
> about 15 hours. There were about 40 packages uploaded and failed
> during that time. Before that change builder was working fine.
>
Sorry, I was wrong. It was down for about 24 hours and there were
about 50 failed package builds.

-- 
BR,
Ed
_______________________________________________
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Reply via email to