devel August 2025

devel@lists.apertis.org

3 participants
11 discussions

New Apertis v2024.6 stable release available
by Walter Lozano 28 Aug '25

28 Aug '25

Hello everyone, I'm glad to announce that Apertis v2024.6 stable release is now available! Apertis v2024.6 is the seventh stable release of the Apertis v2024 release flow. Apertis is committed to maintaining the v2024 release stream until December 2025. This release is based on Debian Bookworm and ships the latest LTS Linux kernel in the 6.6.x series. For more details about the Apertis release flows and support periods, see https://www.apertis.org/designs/release-flow/ You can find the full release notes at https://www.apertis.org/release/v2024.6/releasenotes/ Images are available for download at https://images.apertis.org/release/v2024/v2024.6/ Thanks to everyone who contributed! Walter -- Walter Lozano Collabora Ltd.

1 0

Apertis release candidate v2026dev3.0rc1 available for testing
by Walter Lozano 27 Aug '25

27 Aug '25

Hello everyone, I'm glad to announce that Apertis v2026dev3.0rc1 images for all the supported platforms have been published: AMD64 https://images.apertis.org/release/v2026dev3/v2026dev3.0rc1/amd64/ Arm32 public https://images.apertis.org/release/v2026dev3/v2026dev3.0rc1/armhf/ Arm64 https://images.apertis.org/release/v2026dev3/v2026dev3.0rc1/arm64/ This is the fourth development release on the Apertis v2026 release flow and it is based on Debian Trixie. This release contains Linux 6.12, updates from Trixie and bug fixes. Future releases will track newer Linux versions up to the next LTS version. The test reports are below: * https://qa.apertis.org/report/v2026dev3/20250827.0017/apt * https://qa.apertis.org/report/v2026dev3/20250827.0017/ostree * https://qa.apertis.org/report/v2026dev3/20250827.0017/lxc * https://qa.apertis.org/report/v2026dev3/20250827.0017/nfs The full release schedule is described at https://www.apertis.org/release/v2026dev3/release_schedule/ Thanks, Walter -- Walter Lozano Collabora Ltd.

1 0

Apertis release candidate v2025.2rc2 available for testing
by Walter Lozano 20 Aug '25

20 Aug '25

Hello everyone, I'm glad to announce that Apertis v2025.2rc2 images for all the supported platforms have been published: AMD64 https://images.apertis.org/release/v2025/v2025.2rc2/amd64/ Arm32 public https://images.apertis.org/release/v2025/v2025.2rc2/armhf/ Arm64 https://images.apertis.org/release/v2025/v2025.2rc2/arm64/ This is the third stable release on the Apertis v2025 release flow and it is based on Debian Bookworm. It ships latest LTS Linux 6.12 as well as updates and bugfixes from Debian Bookworm. The test reports are below: * https://qa.apertis.org/report/v2025/20250820.1346/apt * https://qa.apertis.org/report/v2025/20250820.1346/ostree * https://qa.apertis.org/report/v2025/20250820.1346/lxc * https://qa.apertis.org/report/v2025/20250820.1346/nfs The full release schedule is described at https://www.apertis.org/release/v2025/v2025.2/release_schedule/ Thanks, Walter -- Walter Lozano Collabora Ltd.

1 0

Soft code freeze/hard feature freeze for v2026dev3
by Walter Lozano 20 Aug '25

20 Aug '25

Hi all, I'm glad to announce that we have entered Soft Code Freeze / Hard Feature Freeze for v2026dev3 [1]. From this moment only bug fixes will be accepted for this release cycle. Thanks to everyone who contributed! Walter [1] https://www.apertis.org/release/v2026/v2026dev3/release_schedule/ -- Walter Lozano Collabora Ltd.

1 0

Soft feature freeze for v2026dev3
by Walter Lozano 13 Aug '25

13 Aug '25

Hi all, I'm glad to announce that we have entered Soft Feature Freeze for v2026dev3 [1]. From this moment no additional features will be accepted. Thanks to everyone who contributed! Walter [1] https://www.apertis.org/release/v2026/v2026dev3/release_schedule/ -- Walter Lozano Collabora Ltd.

1 0

Soft code freeze/hard feature freeze for v2025.2
by Walter Lozano 13 Aug '25

13 Aug '25

Hi all, I'm glad to announce that we have entered Soft Code Freeze / Hard Feature Freeze for v2025.2 [1]. From this moment only bug fixes will be accepted for this release cycle. Thanks to everyone who contributed! Walter [1] https://www.apertis.org/release/v2025/v2025.2/release_schedule/ -- Walter Lozano Collabora Ltd.

1 0

Apertis release candidate v2024.6rc1 available for testing
by Walter Lozano 13 Aug '25

13 Aug '25

Hello everyone, I'm glad to announce that Apertis v2024.6rc1 images for all the supported platforms have been published: AMD64 https://images.apertis.org/release/v2024/v2024.6rc1/amd64/ Arm32 https://images.apertis.org/release/v2024/v2024.6rc1/armhf/ Arm64 https://images.apertis.org/release/v2024/v2024.6rc1/arm64/ Compared to v2024.5 this release contains security updates from Debian Bookworm and the latest LTS Linux kernel on the 6.6.x series. The test reports are below: * https://qa.apertis.org/report/v2024/20250813.0216/apt * https://qa.apertis.org/report/v2024/20250813.0216/ostree * https://qa.apertis.org/report/v2024/20250813.0216/lxc * https://qa.apertis.org/report/v2024/20250813.0216/nfs The full release schedule is described at https://www.apertis.org/release/v2024/v2024.6/release_schedule/ Thanks, Walter -- Walter Lozano Collabora Ltd.

1 0

Re: Idea: Using ESSTRA for -dbgsym packages
by Dylan Aïssi 08 Aug '25

08 Aug '25

Hi Niels, On 8/7/25 19:18, Niels Thykier wrote: > Hi, > > I noticed that apertis modified the `debhelper` source package for this. > This is of course a valid solution, I wanted to highlight that there > should be less need for that with DH_EXTRA_ADDONS environment variable. > > The ENV variable was developed for this purpose where people want to > prototype something new or when do custom builds. Obviously, migrating > to it now would only make sense if it would simplify matters when > maintaining the addon. > > Best regards, > Niels > Thanks! I will take a look at DH_EXTRA_ADDONS, I guess it could simplify our work when will we have to rebase Apertis on a newer Debian release. Best regards, Dylan

1 0

Fwd: Idea: Using ESSTRA for -dbgsym packages
by Dylan Aïssi 08 Aug '25

08 Aug '25

FYI -------- Forwarded Message -------- Subject: Re: Idea: Using ESSTRA for -dbgsym packages Date: Thu, 7 Aug 2025 18:36:36 +0200 From: Dylan Aïssi <daissi(a)debian.org> To: Hideki Yamane <henrich(a)iijmio-mail.jp>, Takuya.Namae(a)sony.com CC: debian-devel(a)lists.debian.org, devel(a)lists.apertis.org Hello Hideki and Takuya, Le dim. 13 juil. 2025 à 21:14, Hideki Yamane <henrich(a)iijmio-mail.jp> a écrit : > > You can find more detailed information in our presentation slides for > the upcoming DebConf25: > https://salsa.debian.org/henrich/debconf25/-/blob/main/20250718_DebConf25_E… Thanks, that was a very interesting talk! > This leads me to a proposal I'm excited about: enabling ESSTRA for Debian's > -dbgsym packages. > https://docs.google.com/presentation/d/10BWJXGchob4UsKMrSUJl1AMzrkyBQ-gJ6Db… That's exactly what we do in Apertis [0], instead of modifying binaries, we extract the name of the used source files from the DWARF debugging information using dwarf2sources [1] via a debhelper addon [2]. Thus, this approach is compatible with all compilers which generate DWARF information, including LLVM, Go and Rust. For each source file used, a license is associated with it through the use of a consolidated debian/copyright file (based on the result of scan-copyright [3]). Additionally, our approach handles non-binary files, like scripts, configuration and documentation which are part of the binary packages. I'm in the process of upstreaming our tools into Debian, we still have to remove Apertis specific parts, hoping that this may be useful to you. I think we are still quite a long way from being able to enable this feature by default in Debian, but that's something I would really like and which I work on. For now, our approach fix some issues you mentioned in your talk. For instance, we don't modify the binaries (and therefore to increase their size, which is a concern for embedded use cases like where Apertis is used) instead we use already available data from DWARF info. This is a more generic method which is already compatible with Rust and Go binaries since it does not involve a plugin for GCC. And finally, it relies on Debian standard workflows (debhelper and debian/copyright), thus we don't have to modify each debian/rules. I invite you to try it once I have uploaded it into Debian. It would be great if you had the opportunity to compare the two approaches and give us some numbers for comparison. What do you think? Best regards, Dylan [0] https://www.apertis.org/ [1] https://tracker.debian.org/pkg/dwarf2sources [2] https://gitlab.apertis.org/pkg/debhelper/-/blob/apertis/v2026dev3/dh_setup_… [3] https://gitlab.apertis.org/pkg/apertis-dev-tools/-/blob/apertis/v2026dev3/t…

1 0

Soft code freeze/hard feature freeze for v2024.6
by Dylan Aïssi 06 Aug '25

06 Aug '25

Hi all, I'm glad to announce that we have entered Soft Code Freeze / Hard Feature Freeze for v2024.6 [1]. From this moment only bug fixes will be accepted for this release cycle. Thanks to everyone who contributed! Dylan [1] https://www.apertis.org/release/v2024/v2024.6/release_schedule/ -- Dylan Aïssi Collabora Ltd.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

devel August 2025