On 2018-09-10 08:46, John Paul Adrian Glaubitz wrote:
On 09/10/2018 09:41 AM, Julien Cristau wrote:
Before giving back firefox-esr on those archs if we go with
Adrian's packages, I'd at least want to binNMU rustc/cargo
so we're using binaries built on buildds (and so we know
they're buildable
On 09/10/2018 09:41 AM, Julien Cristau wrote:
> My own armhf builds, both native and cross, died either with rustc or
> gcc errors, IIRC (it looked pretty flaky in general).
That's odd because I did not see that issue in the past, both on abel
and on the buildds when 1.24 was built on the
On 09/08/2018 04:07 PM, Adam D. Barratt wrote:
> [CC += jcristau and team@security]
>
> On Sat, 2018-09-08 at 13:17 +0200, John Paul Adrian Glaubitz wrote:
>> Can I get permission to bootstrap and upload to stretch or spu for
>> armhf and armel or is there anything that speaks against having
>>
On Sun, Sep 09, 2018 at 11:01:18PM +0200, John Paul Adrian Glaubitz wrote:
> On 9/8/18 4:07 PM, Adam D. Barratt wrote:
> > Please co-ordinate with Julien, who handled the bootstrapping so far in
> > combination with Moritz.
> >
> > (I'm also not sure whether the security chroots still have pu
> >
On 9/8/18 4:07 PM, Adam D. Barratt wrote:
> Please co-ordinate with Julien, who handled the bootstrapping so far in
> combination with Moritz.
>
> (I'm also not sure whether the security chroots still have pu
> available, as it was added as a special case to get firefox built.)
Built on
[CC += jcristau and team@security]
On Sat, 2018-09-08 at 13:17 +0200, John Paul Adrian Glaubitz wrote:
> Can I get permission to bootstrap and upload to stretch or spu for
> armhf and armel or is there anything that speaks against having
> rustc/firefox-esr in stretch for these architectures?
>
6 matches
Mail list logo