[maemo-developers] Problem with the Diablo autobuilder

[From: Niels Breet]

Hi,

Sorry for the delay. The queue-manager for diablo extras-devel didn't run
because there was a residual PID file.

The incoming queue has now been processed and everything should be back to
normal.

--
Niels Breet
maemo.org webmaster

On Sun, May 3, 2009 18:52, Faheem Pervez wrote:
> Hi,
>
>
> The autobuilder doesn't seem to be moving packages to extras-devel. I
> uploaded python-vte to the diablo autobuilder and it still has not shown
> up yet. I checked with some other packages, by other people, osm2go and
> dialcentral and they haven't been uploaded to extras-devel - despite it
> having been many hours since they had been uploaded.
>
> Please don't tell me to reupload as I do not have the original source
> packages available to me and the autobuilder, being the clever thing it
> is, deletes the source packages it has while it's "moving" them to
> extras-devel.
>
> I realise my tone isn't a nice one and the annoyance isn't directed at
> you, or the maemo.org team responisble for the autobuilder, but rather at
> the autobuilder for chewing my packages.
>
> Best Regards,
> Faheem
>
>
> On Thu, Apr 30, 2009 at 10:05 AM, Jeremiah Foster <
> jeremiah at jeremiahfoster.com> wrote:
>
>>
>> On Apr 30, 2009, at 8:57, Cornelius Hald wrote:
>>
>>
>>> Hi,
>>>
>>>
>>> it looks like there is something wrong with the Diablo autobuilder. I
>>>  was submitting conboy 0.3.2 two times already and it doesn't show up
>>>  in extras-devel. For Chinook and Fremantle it worked fine.
>>>
>>> The mails I received are attached.
>>>
>>>
>>> It would be nice if someone please could check.
>>>
>>
>> As far as the autobuilder is concerned, the indexing tool that updates
>> the list of Packages stopped running yesterday. I am trying to fix that
>> now so that new packages start appearing in diablo.
>>
>> Jeremiah