From: Adrian Bunk <bunk@stusta.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-architecture
<openembedded-architecture@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [Openembedded-architecture] buildtools-extended-tarball wrapping builds
Date: Mon, 9 Mar 2020 14:08:06 +0200 [thread overview]
Message-ID: <20200309120806.GB2477@localhost> (raw)
In-Reply-To: <d6099f127ccb2211996119988c9da3f95c66becb.camel@linuxfoundation.org>
On Mon, Mar 09, 2020 at 11:41:13AM +0000, Richard Purdie wrote:
> On Mon, 2020-03-09 at 12:52 +0200, Adrian Bunk wrote:
> > On Sat, Mar 07, 2020 at 04:17:28PM +0000, Richard Purdie wrote:
> > > ...
> > > This does mean we could drop gcc 4.8/4.9 support if we wanted to
> > > and
> > > rely on the tarball support for centos7/debian8.
> > > ...
> >
> > Debian 8
> > - will have LTS support ending at the end of June, and
> > - ships Python 3.4, which is no longer supported by bitbake.
> >
> > 3 months ago Yocto master stopped working on Debian 8,
> > and as expected noone complained.
>
> We still have one debian8 autobuilder worker:
>
> https://autobuilder.yoctoproject.org/typhoon/#/workers/9
>
> and with buildtools tarball it works 'fine'.
Ah right, buildtools tarball ships python3.
So yes, this invalidates my second point.
> Cheers,
>
> Richard
cu
Adrian
next prev parent reply other threads:[~2020-03-09 12:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 16:17 buildtools-extended-tarball wrapping builds Richard Purdie
2020-03-09 10:52 ` [Openembedded-architecture] " Adrian Bunk
2020-03-09 11:41 ` Richard Purdie
2020-03-09 12:08 ` Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-09 10:01 Rich Persaud
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200309120806.GB2477@localhost \
--to=bunk@stusta.de \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox