Skip to contentSkip to conversation

poky.conf: Debian 8 is no longer supported

PATCH In review Adrian Bunk 3 participants 5 messages Dec 16, 2019 – Dec 17, 2019

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 poky.conf: Debian 8 is no longer supported

Upstream LTS EOL will be June 2020,
and Python 3.4 is now too old for bitbake.

---
 meta-poky/conf/distro/poky.conf | 1 -
 1 file changed, 1 deletion(-)
meta-poky/conf/distro/poky.conf +0 -1
index 8a0f28a863..995dd826ac 100644
@@ -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 \
Signature · 1 line
2.17.1
#1 lore raw
Quoted 14 lines · Adrian Bunk

Upstream LTS EOL will be June 2020,
and Python 3.4 is now too old for bitbake.

---
 meta-poky/conf/distro/poky.conf | 1 -
 1 file changed, 1 deletion(-)
meta- renamed from meta-poky/conf/distro/poky.conf +0 -0

poky/conf/distro/poky.conf
index 8a0f28a863..995dd826ac 100644

meta-poky/conf/distro/poky.conf SANITY_TESTED_DISTROS ?= " \ · line 64

Quoted 7 lines
meta-poky/conf/distro/poky.conf +0 -1
@@ -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...

Cheers,

Richard

#2 lore raw
Quoted 9 lines · Richard Purdie
Quoted 8 lines · Adrian Bunk

Upstream LTS EOL will be June 2020,
and Python 3.4 is now too old for bitbake.

---
 meta-poky/conf/distro/poky.conf | 1 -
 1 file changed, 1 deletion(-)
Quoted 15 lines

meta-poky/conf/distro/poky.conf SANITY_TESTED_DISTROS ?= " \ · line 64

Quoted 13 lines
meta- renamed from meta-poky/conf/distro/poky.conf +0 -0

poky/conf/distro/poky.conf
index 8a0f28a863..995dd826ac 100644

meta-poky/conf/distro/poky.conf +0 -1
@@ -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?

- armin

Quoted 14 lines

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11869): https://lists.yoctoproject.org/g/poky/message/11869
Mute This Topic: https://lists.yoctoproject.org/mt/68709532/3616698
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/poky/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#3 lore raw
Quoted 28 lines · On Mon, Dec 16, 2019 at 04:06:22PM -0800, akuster808 wrote:
Quoted 9 lines · Richard Purdie
Quoted 8 lines · Adrian Bunk

Upstream LTS EOL will be June 2020,
and Python 3.4 is now too old for bitbake.

---
 meta-poky/conf/distro/poky.conf | 1 -
 1 file changed, 1 deletion(-)
Quoted 15 lines

meta-poky/conf/distro/poky.conf SANITY_TESTED_DISTROS ?= " \ · line 64

Quoted 13 lines
meta- renamed from meta-poky/conf/distro/poky.conf +0 -0

poky/conf/distro/poky.conf
index 8a0f28a863..995dd826ac 100644

meta-poky/conf/distro/poky.conf +0 -1
@@ -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...

Quoted 2 lines

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.

Quoted 1 line

- armin

cu
Adrian

#4 lore raw
Quoted 29 lines · Adrian Bunk
Quoted 28 lines · On Mon, Dec 16, 2019 at 04:06:22PM -0800, akuster808 wrote:
Quoted 25 lines · Richard Purdie
Quoted 14 lines · Adrian Bunk

Upstream LTS EOL will be June 2020,
and Python 3.4 is now too old for bitbake.

---
 meta-poky/conf/distro/poky.conf | 1 -
 1 file changed, 1 deletion(-)
meta- renamed from meta-poky/conf/distro/poky.conf +0 -0

poky/conf/distro/poky.conf
index 8a0f28a863..995dd826ac 100644

meta-poky/conf/distro/poky.conf SANITY_TESTED_DISTROS ?= " \ · line 64

Quoted 7 lines
meta-poky/conf/distro/poky.conf +0 -1
@@ -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...

Quoted 4 lines
Quoted 2 lines

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?

It represents the list of machines we test upon, which in reality are the workers installed in the autobuilder at this point.

The autobuilder still has a debian8 worker.

Quoted 3 lines

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.

Should be straightforward to add one, nobody has pointed that out before!

Cheers,

Richard