launchpad-dev team mailing list archive

[Benji York <benji.york@xxxxxxxxxxxxx>]

On Thu, Dec 8, 2011 at 10:25 AM, Gary Poster <gary.poster@xxxxxxxxxxxxx> wrote:
>
> On Dec 8, 2011, at 10:18 AM, Francis J. Lacoste wrote:
>
>> On 11-12-08 08:09 AM, Gary Poster wrote:
>>>
>>> On Dec 7, 2011, at 6:46 PM, William Grant wrote:
>>>
>>>> On 08/12/11 03:50, Colin Watson wrote:
>>>>> On Wed, Dec 07, 2011 at 04:40:43PM +0000, Julian Edwards wrote:
>>>>>> On Tuesday 06 December 2011 22:00:39 Colin Watson wrote:
>>>>>>> Could a Launchpad developer review this lot and copy into the Launchpad
>>>>>>> PPA?  germinate 2.0 is in precise (or will be once the librarian is
>>>>>>> fixed), so no change is needed for that suite.
>>>>>>
>>>>>> All copied.
>>>>>
>>>>> Thanks.
>>>>>
>>>>>> The ec2 and buildbot images will need updating as well if you are
>>>>>> using the new package in tests?
>>>>>
>>>>> Yes.  Can somebody take care of that, as I can't?  (Maybe it's easier to
>>>>> merge
>>>>> https://code.launchpad.net/~cjwatson/meta-lp-deps/python-germinate/+merge/84763
>>>>> before doing that; not sure.)
>>>>
>>>> Actually, poolie changed ec2 to autoupgrade recently.
>>>
>>> Wasn't that undone because it led ec2 to bless code that failed on buildbot?
>>>
>>
>> It wasn't. I suggested we undo it, but Robert and Martin said that this
>> only change the place where it's possible to make a mistake.
>>
>> If the same mistake happens again though, I'll personally disable it :-)
>
> My understanding is that it is happening now, in reverse.  Benji (and
> Francesco?) both report a buildd error in ec2 and locally on trunk
> after they update the package.  This is not failing on buildbot,
> presumably because the package is not updated there yet.  Benji, could
> you confirm or deny?

Correct.  Buildbot isn't exhibiting the symptom, but both EC2 and my (up
to date) dev VM generate errors for devel: http://paste.ubuntu.com/763881/

-- 
Benji York