From: "Adrian Bunk" <bunk@stusta.de>
To: akuster808 <akuster808@gmail.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
poky@yoctoproject.org
Subject: Re: [poky] [meta-poky][PATCH] poky.conf: Debian 8 is no longer supported
Date: Tue, 17 Dec 2019 05:27:56 +0200 [thread overview]
Message-ID: <20191217032756.GA32000@localhost> (raw)
In-Reply-To: <0f4abf32-abc4-8413-3e6b-600f3cf7c1f4@gmail.com>
On Mon, Dec 16, 2019 at 04:06:22PM -0800, akuster808 wrote:
>
>
> On 12/16/19 3:55 PM, Richard Purdie wrote:
> > On Mon, 2019-12-16 at 06:06 +0200, Adrian Bunk wrote:
> >> Upstream LTS EOL will be June 2020,
> >> and Python 3.4 is now too old for bitbake.
> >>
> >> Signed-off-by: Adrian Bunk <bunk@stusta.de>
> >> ---
> >> meta-poky/conf/distro/poky.conf | 1 -
> >> 1 file changed, 1 deletion(-)
> >>
> >> diff --git a/meta-poky/conf/distro/poky.conf b/meta-
> >> poky/conf/distro/poky.conf
> >> index 8a0f28a863..995dd826ac 100644
> >> --- a/meta-poky/conf/distro/poky.conf
> >> +++ b/meta-poky/conf/distro/poky.conf
> >> @@ -59,7 +59,6 @@ SANITY_TESTED_DISTROS ?= " \
> >> fedora-29 \n \
> >> fedora-30 \n \
> >> centos-7 \n \
> >> - debian-8 \n \
> >> debian-9 \n \
> >> debian-10 \n \
> >> opensuseleap-15.1 \n \
> > We still have such a worker in the autobuilder right now as it can work
> > using our buildtools tarball...
>
> Is there a recommend process we should consult when adding or
> subtracting host support for the project?
And what does "SANITY_TESTED_DISTROS" actually mean?
If this might require the buildtools tarball, the next issue is that
there is not yet an aarch64 buildtools tarball available in stable
series supporting aarch64 hosts.
> - armin
cu
Adrian
next prev parent reply other threads:[~2019-12-17 3:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 4:06 [meta-poky][PATCH] poky.conf: Debian 8 is no longer supported Adrian Bunk
2019-12-16 23:55 ` [poky] " Richard Purdie
2019-12-17 0:06 ` Armpit
2019-12-17 3:27 ` Adrian Bunk [this message]
2019-12-17 9:44 ` Richard Purdie
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=20191217032756.GA32000@localhost \
--to=bunk@stusta.de \
--cc=akuster808@gmail.com \
--cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.