Re: arm not building for lenny-security
Hi Aurélien,
On Fri, June 3, 2011 13:19, Aurelien Jarno wrote:
> On Fri, Jun 03, 2011 at 11:54:57AM +0200, Thijs Kinkhorst wrote:
>> Hi,
>
> Hi,
>
>> For recent lenny security updates we've been consistently missing builds
>> for
>> arm. At least the following packages seem to suffer from this. Can you
>> check
>> this out please?
>
> It seems all these packages except one (see below) have been built
> successfully and the build logs have been sent correctly according to
> the exim logs. On the other hand the signing mails doesn't seem to
> arrive, so my guess is that there is a mail issue somewhere.
>
> I personally receive build logs for lenny and bpo and have no problem to
> sign the build logs. Could you please check if you have any return error
> message when signing the build logs? Some of the packages have been
> built for more than 15 days, and most MTA give up after 5 or 10 days.
We don't sign the build logs (anymore), the security suites are autosigned.
I think we need the wb-admins to check this out, then.
> Please find below the status of the builds:
>
>> bind9
>
> bind9_1:9.6.ESV.R4+dfsg-0+lenny2 built successfully on cats
>
>> apr
>
> apr_1.2.12-5+lenny3 built successfully on toffee
>
>> citadel
>
> citadel_7.37-8+lenny1 built successfully on cats
>
>> cyrus-imapd-2.2
>
> cyrus-imapd-2.2_2.2.13-14+lenny4 built successfully on cats
>
>> ejabberd
>
> ejabberd_2.0.1-6+lenny3 built successfully on cats
>
>> subversion
>
> subversion_1.5.1dfsg1-7 built successfully on toffee
>
>> oprofile
>
> doesn't appear in wanna-build, probably due to Pas given the packages is
> not shipped in lenny on arm.
>
>> fontforge
>
> fontforge_0.0.20080429-1+lenny2 fontforge_0.0.20080429-1+lenny2
>
Cheers,
Thijs
Reply to: