On Mon, 2018-09-10 at 19:19 +0100, Adam D. Barratt wrote:
> On Mon, 2018-09-10 at 12:46 +0200, John Paul Adrian Glaubitz wrote:
> > On 09/10/2018 12:45 PM, Adam D. Barratt wrote:
> > > > I suggest that someone triggers binNMUs for all four packages
> > > > now
> > > > as Julien suggested.
> > >
>
On Mon, 2018-09-10 at 12:46 +0200, John Paul Adrian Glaubitz wrote:
> On 09/10/2018 12:45 PM, Adam D. Barratt wrote:
> > > I suggest that someone triggers binNMUs for all four packages now
> > > as Julien suggested.
> >
> > Do those need doing in order? (i.e. do we need to binNMU rust, and
> > the
On 09/10/2018 12:45 PM, Adam D. Barratt wrote:
>> I suggest that someone triggers binNMUs for all four packages now
>> as Julien suggested.
>
> Do those need doing in order? (i.e. do we need to binNMU rust, and then
> binNMU cargo against the rust binNMUs?)
No, the order doesn't matter. I'd sugg
On 2018-09-10 11:26, John Paul Adrian Glaubitz wrote:
On 09/10/2018 12:22 PM, Adam D. Barratt wrote:
I agree, I wanted to suggest that, too. Shall I go ahead with the
upload now?
It looks like that happened already? (Judging from
https://lists.debian.org/debian-release/2018/09/msg00112.html )
On 09/10/2018 12:22 PM, Adam D. Barratt wrote:
>> I agree, I wanted to suggest that, too. Shall I go ahead with the
>> upload now?
>
> It looks like that happened already? (Judging from
> https://lists.debian.org/debian-release/2018/09/msg00112.html )
Yes, I assumed it would land in a NEW queue
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
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 buildds.
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
>> ru
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 abel.debi
[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?
>
>
Hi!
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?
If it’s ok, I will bootstrap and upload tonight as several users have
complained that Firefox 60 ESR is n
12 matches
Mail list logo
