| Message ID | 20241014155604.569003-1-cedric.hombourger@siemens.com (mailing list archive) |
|---|---|
| State | New |
| Headers | show |
| Series | [isar-cip-core] distro: add preliminary support for the upcoming Debian 13 (trixie) | expand |
On Mon, 2024-10-14 at 17:56 +0200, cedric.hombourger@siemens.com via lists.cip-project.org wrote: > Debian will probably start freezing packages next year (first a soft freeze > then a hard freeze). It is important that the CIP community starts testing > Debian 13 to provide feedback upstream while we may still influence versions > that the distribution will select for their new major version. > > Signed-off-by: Cedric Hombourger <cedric.hombourger@siemens.com> Might be a bit to early. Expect build failures for any kind of cross builds. Package versions (at least for glibc) are currently out of sync.
On Mon, 2024-10-14 at 18:35 +0200, Florian Bezdeka wrote: > On Mon, 2024-10-14 at 17:56 +0200, cedric.hombourger@siemens.com via > lists.cip-project.org wrote: > > Debian will probably start freezing packages next year (first a > > soft freeze > > then a hard freeze). It is important that the CIP community starts > > testing > > Debian 13 to provide feedback upstream while we may still influence > > versions > > that the distribution will select for their new major version. > > > > Signed-off-by: Cedric Hombourger <cedric.hombourger@siemens.com> > > Might be a bit to early. Expect build failures for any kind of cross > builds. Package versions (at least for glibc) are currently out of > sync. Well this layer provides "sid" and isar already provides both sid and trixie. We could add a sensible snapshot date if that helps but it is definitely not too early for "platform" layers to take a look at what's coming, test it and provide feedback to the Debian community Yes surely people erring on the cutting edge side of things (trixie, sid) should be prepared to face issues If you'd like I could prepend this patch with a patch adding an "experimental" switch to Kconfig and make some of our options depend on it, thus presenting this option to people understanding risks associated with their configuration. Cedric
On 14.10.24 17:56, Cedric Hombourger wrote: > Debian will probably start freezing packages next year (first a soft freeze > then a hard freeze). It is important that the CIP community starts testing > Debian 13 to provide feedback upstream while we may still influence versions > that the distribution will select for their new major version. > > Signed-off-by: Cedric Hombourger <cedric.hombourger@siemens.com> > --- > Kconfig | 5 +++++ > conf/distro/cip-core-trixie.conf | 16 ++++++++++++++++ > kas/opt/trixie.yml | 15 +++++++++++++++ > .../secure-boot-secrets/files/trixie | 1 + > .../swupdate-certificates/files/trixie | 1 + > 5 files changed, 38 insertions(+) > create mode 100644 conf/distro/cip-core-trixie.conf > create mode 100644 kas/opt/trixie.yml > create mode 120000 recipes-devtools/secure-boot-secrets/files/trixie > create mode 120000 recipes-devtools/swupdate-certificates/files/trixie > > diff --git a/Kconfig b/Kconfig > index a70ce22..9b15c05 100644 > --- a/Kconfig > +++ b/Kconfig > @@ -136,6 +136,10 @@ config DEBIAN_BOOKWORM > bool "bookworm (12)" > depends on !ARCH_RISCV64 > > +config DEBIAN_TRIXIE > + bool "trixie (testing)" > + depends on !ARCH_RISCV64 That is obsolete once trixie is stable enough. In fact, being able to finally build RISC-V via trixie, rather than a sid snapshot, would be a good indicator that it is worth to start regular testing. > + > config DEBIAN_SID > bool "sid (unstable)" > depends on ARCH_RISCV64 > @@ -147,6 +151,7 @@ config KAS_INCLUDE_DEBIAN > default "kas/opt/buster.yml" if DEBIAN_BUSTER > default "kas/opt/bullseye.yml" if DEBIAN_BULLSEYE > default "kas/opt/bookworm.yml" if DEBIAN_BOOKWORM > + default "kas/opt/trixie.yml" if DEBIAN_TRIXIE > default "kas/opt/sid.yml" if DEBIAN_SID > > comment "Image features" > diff --git a/conf/distro/cip-core-trixie.conf b/conf/distro/cip-core-trixie.conf > new file mode 100644 > index 0000000..58999d1 > --- /dev/null > +++ b/conf/distro/cip-core-trixie.conf > @@ -0,0 +1,16 @@ > +# > +# CIP Core, generic profile > +# > +# Copyright (c) Siemens AG, 2024 > +# > +# Authors: > +# Cedric Hombourger <cedric.hombourger@siemens.com> > +# > +# SPDX-License-Identifier: MIT > +# > + > +require conf/distro/debian-trixie.conf > +require cip-core-common.inc > + > +PREFERRED_VERSION_linux-cip ?= "6.1.%" > +PREFERRED_VERSION_linux-cip-rt ?= "6.1.%" That will likely change before the release but we indeed started with an older kernel into bookworm as well. > diff --git a/kas/opt/trixie.yml b/kas/opt/trixie.yml > new file mode 100644 > index 0000000..e9a76ef > --- /dev/null > +++ b/kas/opt/trixie.yml > @@ -0,0 +1,15 @@ > +# > +# CIP Core, generic profile > +# > +# Copyright (c) Siemens AG, 2024 > +# > +# Authors: > +# Cedric Hombourger <cedric.hombourger@siemens.com> > +# > +# SPDX-License-Identifier: MIT > +# > + > +header: > + version: 14 > + > +distro: cip-core-trixie > diff --git a/recipes-devtools/secure-boot-secrets/files/trixie b/recipes-devtools/secure-boot-secrets/files/trixie > new file mode 120000 > index 0000000..91bf492 > --- /dev/null > +++ b/recipes-devtools/secure-boot-secrets/files/trixie > @@ -0,0 +1 @@ > +bullseye > \ No newline at end of file > diff --git a/recipes-devtools/swupdate-certificates/files/trixie b/recipes-devtools/swupdate-certificates/files/trixie > new file mode 120000 > index 0000000..3d633ae > --- /dev/null > +++ b/recipes-devtools/swupdate-certificates/files/trixie > @@ -0,0 +1 @@ > +../../secure-boot-secrets/files/trixie > \ No newline at end of file As Florian already mentioned, some minimal cross-compilation stability is required as we cannot wait for hours on emulated native builds. There is also [1] waiting for a fix so that our core features can be tested. And there might be more. Jan [1] https://gitlab.com/cip-project/cip-core/isar-cip-core/-/issues/114
On Tue, 2024-10-15 at 00:22 +0200, Jan Kiszka via lists.cip-project.org wrote: > On 14.10.24 17:56, Cedric Hombourger wrote: > > Debian will probably start freezing packages next year (first a soft freeze > > then a hard freeze). It is important that the CIP community starts testing > > Debian 13 to provide feedback upstream while we may still influence versions > > that the distribution will select for their new major version. > > > > Signed-off-by: Cedric Hombourger <cedric.hombourger@siemens.com> > > --- > > Kconfig | 5 +++++ > > conf/distro/cip-core-trixie.conf | 16 ++++++++++++++++ > > kas/opt/trixie.yml | 15 +++++++++++++++ > > .../secure-boot-secrets/files/trixie | 1 + > > .../swupdate-certificates/files/trixie | 1 + > > 5 files changed, 38 insertions(+) > > create mode 100644 conf/distro/cip-core-trixie.conf > > create mode 100644 kas/opt/trixie.yml > > create mode 120000 recipes-devtools/secure-boot-secrets/files/trixie > > create mode 120000 recipes-devtools/swupdate-certificates/files/trixie > > > > diff --git a/Kconfig b/Kconfig > > index a70ce22..9b15c05 100644 > > --- a/Kconfig > > +++ b/Kconfig > > @@ -136,6 +136,10 @@ config DEBIAN_BOOKWORM > > bool "bookworm (12)" > > depends on !ARCH_RISCV64 > > > > +config DEBIAN_TRIXIE > > + bool "trixie (testing)" > > + depends on !ARCH_RISCV64 > > That is obsolete once trixie is stable enough. In fact, being able to > finally build RISC-V via trixie, rather than a sid snapshot, would be a > good indicator that it is worth to start regular testing. > > > + > > config DEBIAN_SID > > bool "sid (unstable)" > > depends on ARCH_RISCV64 > > @@ -147,6 +151,7 @@ config KAS_INCLUDE_DEBIAN > > default "kas/opt/buster.yml" if DEBIAN_BUSTER > > default "kas/opt/bullseye.yml" if DEBIAN_BULLSEYE > > default "kas/opt/bookworm.yml" if DEBIAN_BOOKWORM > > + default "kas/opt/trixie.yml" if DEBIAN_TRIXIE > > default "kas/opt/sid.yml" if DEBIAN_SID > > > > comment "Image features" > > diff --git a/conf/distro/cip-core-trixie.conf b/conf/distro/cip-core-trixie.conf > > new file mode 100644 > > index 0000000..58999d1 > > --- /dev/null > > +++ b/conf/distro/cip-core-trixie.conf > > @@ -0,0 +1,16 @@ > > +# > > +# CIP Core, generic profile > > +# > > +# Copyright (c) Siemens AG, 2024 > > +# > > +# Authors: > > +# Cedric Hombourger <cedric.hombourger@siemens.com> > > +# > > +# SPDX-License-Identifier: MIT > > +# > > + > > +require conf/distro/debian-trixie.conf > > +require cip-core-common.inc > > + > > +PREFERRED_VERSION_linux-cip ?= "6.1.%" > > +PREFERRED_VERSION_linux-cip-rt ?= "6.1.%" > > That will likely change before the release but we indeed started with an > older kernel into bookworm as well. > > > diff --git a/kas/opt/trixie.yml b/kas/opt/trixie.yml > > new file mode 100644 > > index 0000000..e9a76ef > > --- /dev/null > > +++ b/kas/opt/trixie.yml > > @@ -0,0 +1,15 @@ > > +# > > +# CIP Core, generic profile > > +# > > +# Copyright (c) Siemens AG, 2024 > > +# > > +# Authors: > > +# Cedric Hombourger <cedric.hombourger@siemens.com> > > +# > > +# SPDX-License-Identifier: MIT > > +# > > + > > +header: > > + version: 14 > > + > > +distro: cip-core-trixie > > diff --git a/recipes-devtools/secure-boot-secrets/files/trixie b/recipes-devtools/secure-boot-secrets/files/trixie > > new file mode 120000 > > index 0000000..91bf492 > > --- /dev/null > > +++ b/recipes-devtools/secure-boot-secrets/files/trixie > > @@ -0,0 +1 @@ > > +bullseye > > \ No newline at end of file > > diff --git a/recipes-devtools/swupdate-certificates/files/trixie b/recipes-devtools/swupdate-certificates/files/trixie > > new file mode 120000 > > index 0000000..3d633ae > > --- /dev/null > > +++ b/recipes-devtools/swupdate-certificates/files/trixie > > @@ -0,0 +1 @@ > > +../../secure-boot-secrets/files/trixie > > \ No newline at end of file > > As Florian already mentioned, some minimal cross-compilation stability > is required as we cannot wait for hours on emulated native builds. There > is also [1] waiting for a fix so that our core features can be tested. > And there might be more. Btw: Isn't that something that should go into isar directly? Why is Trixie support isar-cip-core specific? Florian > > Jan > > [1] https://gitlab.com/cip-project/cip-core/isar-cip-core/-/issues/114 > > -- > Siemens AG, Technology > Linux Expert Center
On 15.10.24 14:27, Florian Bezdeka wrote: > On Tue, 2024-10-15 at 00:22 +0200, Jan Kiszka via lists.cip-project.org > wrote: >> On 14.10.24 17:56, Cedric Hombourger wrote: >>> Debian will probably start freezing packages next year (first a soft freeze >>> then a hard freeze). It is important that the CIP community starts testing >>> Debian 13 to provide feedback upstream while we may still influence versions >>> that the distribution will select for their new major version. >>> >>> Signed-off-by: Cedric Hombourger <cedric.hombourger@siemens.com> >>> --- >>> Kconfig | 5 +++++ >>> conf/distro/cip-core-trixie.conf | 16 ++++++++++++++++ >>> kas/opt/trixie.yml | 15 +++++++++++++++ >>> .../secure-boot-secrets/files/trixie | 1 + >>> .../swupdate-certificates/files/trixie | 1 + >>> 5 files changed, 38 insertions(+) >>> create mode 100644 conf/distro/cip-core-trixie.conf >>> create mode 100644 kas/opt/trixie.yml >>> create mode 120000 recipes-devtools/secure-boot-secrets/files/trixie >>> create mode 120000 recipes-devtools/swupdate-certificates/files/trixie >>> >>> diff --git a/Kconfig b/Kconfig >>> index a70ce22..9b15c05 100644 >>> --- a/Kconfig >>> +++ b/Kconfig >>> @@ -136,6 +136,10 @@ config DEBIAN_BOOKWORM >>> bool "bookworm (12)" >>> depends on !ARCH_RISCV64 >>> >>> +config DEBIAN_TRIXIE >>> + bool "trixie (testing)" >>> + depends on !ARCH_RISCV64 >> >> That is obsolete once trixie is stable enough. In fact, being able to >> finally build RISC-V via trixie, rather than a sid snapshot, would be a >> good indicator that it is worth to start regular testing. >> >>> + >>> config DEBIAN_SID >>> bool "sid (unstable)" >>> depends on ARCH_RISCV64 >>> @@ -147,6 +151,7 @@ config KAS_INCLUDE_DEBIAN >>> default "kas/opt/buster.yml" if DEBIAN_BUSTER >>> default "kas/opt/bullseye.yml" if DEBIAN_BULLSEYE >>> default "kas/opt/bookworm.yml" if DEBIAN_BOOKWORM >>> + default "kas/opt/trixie.yml" if DEBIAN_TRIXIE >>> default "kas/opt/sid.yml" if DEBIAN_SID >>> >>> comment "Image features" >>> diff --git a/conf/distro/cip-core-trixie.conf b/conf/distro/cip-core-trixie.conf >>> new file mode 100644 >>> index 0000000..58999d1 >>> --- /dev/null >>> +++ b/conf/distro/cip-core-trixie.conf >>> @@ -0,0 +1,16 @@ >>> +# >>> +# CIP Core, generic profile >>> +# >>> +# Copyright (c) Siemens AG, 2024 >>> +# >>> +# Authors: >>> +# Cedric Hombourger <cedric.hombourger@siemens.com> >>> +# >>> +# SPDX-License-Identifier: MIT >>> +# >>> + >>> +require conf/distro/debian-trixie.conf >>> +require cip-core-common.inc >>> + >>> +PREFERRED_VERSION_linux-cip ?= "6.1.%" >>> +PREFERRED_VERSION_linux-cip-rt ?= "6.1.%" >> >> That will likely change before the release but we indeed started with an >> older kernel into bookworm as well. >> >>> diff --git a/kas/opt/trixie.yml b/kas/opt/trixie.yml >>> new file mode 100644 >>> index 0000000..e9a76ef >>> --- /dev/null >>> +++ b/kas/opt/trixie.yml >>> @@ -0,0 +1,15 @@ >>> +# >>> +# CIP Core, generic profile >>> +# >>> +# Copyright (c) Siemens AG, 2024 >>> +# >>> +# Authors: >>> +# Cedric Hombourger <cedric.hombourger@siemens.com> >>> +# >>> +# SPDX-License-Identifier: MIT >>> +# >>> + >>> +header: >>> + version: 14 >>> + >>> +distro: cip-core-trixie >>> diff --git a/recipes-devtools/secure-boot-secrets/files/trixie b/recipes-devtools/secure-boot-secrets/files/trixie >>> new file mode 120000 >>> index 0000000..91bf492 >>> --- /dev/null >>> +++ b/recipes-devtools/secure-boot-secrets/files/trixie >>> @@ -0,0 +1 @@ >>> +bullseye >>> \ No newline at end of file >>> diff --git a/recipes-devtools/swupdate-certificates/files/trixie b/recipes-devtools/swupdate-certificates/files/trixie >>> new file mode 120000 >>> index 0000000..3d633ae >>> --- /dev/null >>> +++ b/recipes-devtools/swupdate-certificates/files/trixie >>> @@ -0,0 +1 @@ >>> +../../secure-boot-secrets/files/trixie >>> \ No newline at end of file >> >> As Florian already mentioned, some minimal cross-compilation stability >> is required as we cannot wait for hours on emulated native builds. There >> is also [1] waiting for a fix so that our core features can be tested. >> And there might be more. > > Btw: Isn't that something that should go into isar directly? Why is > Trixie support isar-cip-core specific? It seems that there is some progress in Debian now, see [1]. Jan [1] https://patchwork.isar-build.org/project/isar/patch/6c4edb8f-ff3d-400c-8b3c-08601ef428b0@siemens.com/
diff --git a/Kconfig b/Kconfig index a70ce22..9b15c05 100644 --- a/Kconfig +++ b/Kconfig @@ -136,6 +136,10 @@ config DEBIAN_BOOKWORM bool "bookworm (12)" depends on !ARCH_RISCV64 +config DEBIAN_TRIXIE + bool "trixie (testing)" + depends on !ARCH_RISCV64 + config DEBIAN_SID bool "sid (unstable)" depends on ARCH_RISCV64 @@ -147,6 +151,7 @@ config KAS_INCLUDE_DEBIAN default "kas/opt/buster.yml" if DEBIAN_BUSTER default "kas/opt/bullseye.yml" if DEBIAN_BULLSEYE default "kas/opt/bookworm.yml" if DEBIAN_BOOKWORM + default "kas/opt/trixie.yml" if DEBIAN_TRIXIE default "kas/opt/sid.yml" if DEBIAN_SID comment "Image features" diff --git a/conf/distro/cip-core-trixie.conf b/conf/distro/cip-core-trixie.conf new file mode 100644 index 0000000..58999d1 --- /dev/null +++ b/conf/distro/cip-core-trixie.conf @@ -0,0 +1,16 @@ +# +# CIP Core, generic profile +# +# Copyright (c) Siemens AG, 2024 +# +# Authors: +# Cedric Hombourger <cedric.hombourger@siemens.com> +# +# SPDX-License-Identifier: MIT +# + +require conf/distro/debian-trixie.conf +require cip-core-common.inc + +PREFERRED_VERSION_linux-cip ?= "6.1.%" +PREFERRED_VERSION_linux-cip-rt ?= "6.1.%" diff --git a/kas/opt/trixie.yml b/kas/opt/trixie.yml new file mode 100644 index 0000000..e9a76ef --- /dev/null +++ b/kas/opt/trixie.yml @@ -0,0 +1,15 @@ +# +# CIP Core, generic profile +# +# Copyright (c) Siemens AG, 2024 +# +# Authors: +# Cedric Hombourger <cedric.hombourger@siemens.com> +# +# SPDX-License-Identifier: MIT +# + +header: + version: 14 + +distro: cip-core-trixie diff --git a/recipes-devtools/secure-boot-secrets/files/trixie b/recipes-devtools/secure-boot-secrets/files/trixie new file mode 120000 index 0000000..91bf492 --- /dev/null +++ b/recipes-devtools/secure-boot-secrets/files/trixie @@ -0,0 +1 @@ +bullseye \ No newline at end of file diff --git a/recipes-devtools/swupdate-certificates/files/trixie b/recipes-devtools/swupdate-certificates/files/trixie new file mode 120000 index 0000000..3d633ae --- /dev/null +++ b/recipes-devtools/swupdate-certificates/files/trixie @@ -0,0 +1 @@ +../../secure-boot-secrets/files/trixie \ No newline at end of file
Debian will probably start freezing packages next year (first a soft freeze then a hard freeze). It is important that the CIP community starts testing Debian 13 to provide feedback upstream while we may still influence versions that the distribution will select for their new major version. Signed-off-by: Cedric Hombourger <cedric.hombourger@siemens.com> --- Kconfig | 5 +++++ conf/distro/cip-core-trixie.conf | 16 ++++++++++++++++ kas/opt/trixie.yml | 15 +++++++++++++++ .../secure-boot-secrets/files/trixie | 1 + .../swupdate-certificates/files/trixie | 1 + 5 files changed, 38 insertions(+) create mode 100644 conf/distro/cip-core-trixie.conf create mode 100644 kas/opt/trixie.yml create mode 120000 recipes-devtools/secure-boot-secrets/files/trixie create mode 120000 recipes-devtools/swupdate-certificates/files/trixie