Apertis is a Debian derivative distribution geared towards the creation of product-specific images for ARM (both the 32bit ARMv7 and 64-bit ARMv8 versions using the hardfloat ABI) and Intel x86-64 (64-bit) systems.
Apertis v2024dev0 is first development release of the Apertis v2024 stable release flow that will lead to the LTS Apertis v2024.0 release in March 2024.
This Apertis release is built on top of Debian Bullseye with several customizations. It currently ships with the Linux kernel 6.0.x series. Later releases in the v2024 channel will be tracking newer kernel versions up to the next LTS, as well as Debian Bookworm.
Test results for the v2024dev0 release are available in the following test reports:
- 2022 Q4: v2024dev0
- 2023 Q1: v2024dev1
- 2023 Q2: v2024dev2
- 2023 Q3: v2024dev3
- 2023 Q4: v2024dev0
- 2024 Q1: v2024.0
- 2024 Q2: v2024.1
- 2024 Q3: v2024.2
- 2024 Q4: v2024.3
- 2025 Q1: v2024.4
- 2025 Q2: v2024.5
- 2025 Q3: v2024.6
- 2025 Q4: v2024.7
|Apertis v2024dev0.0 images|
|Intel 64-bit||fixedfunction||hmi||base SDK||SDK|
|ARM 32-bit (U-Boot)||fixedfunction||hmi|
|ARM 64-bit (U-Boot)||fixedfunction|
|ARM 64-bit (Raspberry Pi)||fixedfunction||hmi|
Apertis v2024dev0 package list
The full list of packages available from the v2024dev0 APT repositories is available in tab-separated value (TSV) format for easy processing in spreadsheets:
Apertis v2024dev0 repositories
deb https://repositories.apertis.org/apertis/ v2024dev0 target development sdk
No new features since this is a preview release.
Build and integration
Improved QA Report App configuration management and deployment
A set of changes were introduced to make configuring the QA Report App more straightforward and consistent, also including an improved validation of configuration settings. These improvements align with the use of ansible and kubernetes as a way to manage deployments and orchestration, improving automation and reducing manual work. These changes will also benefit downstream distributions, which will find it easier to deploy new instances.
QA Report App and OIDC authentication mechanism
As a way to provide more flexibility around authentication mechanisms, the QA Report App now uses OpenID Connect as the authentication mechanism, replacing the previous GitLab OAuth mechanism.
Although the Apertis deployment still uses GitLab as the OIDC provider, this change will allow deployments to use any OIDC provider that best fit their needs.
Relatedly, the QA Report App now also provides the support to always require login, allowing deployments to control whether login is required to access the reports.
Improved QA Report App support for weekly images
Weekly Apertis images are tested with both automated and manual test cases, as part of the QA process. The results from these tests are submitted to the QA Report App, and now can be easily seen in the main page which provides a separate section for each type of image: releases, weeklies and dailies.
Deprecations and ABI/API breaks
No known regressions.
No known deprecations
No know breaks
Apertis Docker images
The Apertis Docker images provide a unified and easily reproducible build environment for developers and services.
As of today, this includes the
Image daily builds, as well as release builds can be found at https://images.apertis.org/
The Apertis Image Recipes provides an overview of the image building process and the involved services.
- Issue #122 aum-offline-upgrade: test failed
- Issue #126 aum-offline-upgrade-signed: test failed
- Issue #127 aum-api: test failed
- Issue #128 aum-ota-api: test failed
- Issue #134 aum-ota-signed: test failed
- Issue #146 aum-ota-out-of-space: test failed
- Issue #167 aum-ota-auto: test failed
- Issue #169 aum-out-of-space: test failed
- Issue #190 aum-power-cut: test failed
- Issue #203 aum-ota-rollback-blacklist: test failed
- Issue #204 aum-rollback-blacklist: test failed
- Issue #213 dbus-installed-tests: test failed
- Issue #215 Follow up FS corruption issue - part 2
- Issue #223 Launching an Application on agl-compositor takes more time
- Issue #224 SD card timeout issues in RPi4
- Issue #230 WebProcess CRASHED error is seen on executing webkit related testcases
- Issue #7 Crash when initialising egl on ARM target
- Issue #8 arm-linux-gnueabihf-pkg-config does not work with sysroots installed by
- Issue #12 gettext-i18n: test failed
- Issue #15 Fix the kernel command line generation in OSTRee for FIT image
- Issue #17 SabreLite failing to boot due to failing “to start udev Coldplug all Devices”
- Issue #22 debos sometimes fails to mount things
- Issue #26 newport: test failed
- Issue #32 Gitlab pipeline OBS job reported “success” but OBS build was “unresolvable”
- Issue #36 dashboard: gnome-settings-daemon-data incorrectly flagged as missing the git repository
- Issue #38 LAVA/Phab bridge timeouts
- Issue #39 grilo: test failed
- Issue #45 Manual testcase results should not have any hyperlink in the LavaPhabridge report page
- Issue #47 Failed to start Access poi…server : logs seen in v2023 amd64/armhf boot logs
- Issue #62 apparmor-ofono: test failed
- Issue #118 tiny-container-system-connectivity-profile: test failed
- Issue #119 tiny-container-user-connectivity-profile: test failed
- Issue #193 flatpak-run-demo-cli-app: test failed
- Issue #210 tiny-container-system-folder-sharing: test failed
- Issue #23 Remote outputs and local output, buffer size combined in Maynard/GTK