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 v2024dev1 is the second 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.1.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 v2024dev1 release are available in the following test reports:

Release flow

  • 2022 Q4: v2024dev0
  • 2023 Q1: v2024dev1
  • 2023 Q2: v2024dev2
  • 2023 Q3: v2024dev3
  • 2023 Q4: v2024pre
  • 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

Release downloads

Apertis v2024dev1.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

The Intel fixedfunction and hmi images are tested on the reference hardware (UP Squared 6000), but they can run on any UEFI-based x86-64 system. The sdk image is tested under VirtualBox.

Apertis v2024dev1 package list

The full list of packages available from the v2024dev1 APT repositories is available in tab-separated value (TSV) format for easy processing in spreadsheets:

Apertis v2024dev1 repositories

deb https://repositories.apertis.org/apertis/ v2024dev1 target development sdk

New features

Initial support for running integration tests on MRs

Following the guidelines described in the Apertis test strategy this release provides initial support for running automated tests on LAVA in the context of a MR. With this feature, packages changes can be validated by running integration tests before landing them to main branches.

It is currently recommended that only packages where potential regressions may have a high-impact on the system stability have this feature enabled, given the extra resources required to run the tests.

As before, all available integration tests are also run regularly on daily image builds.

Build and integration

Support for more fine-grained access roles in QA Report App

With the goal of providing better access control to the QA Report App, now three different roles are defined to allow performing the following actions: view results, submit manual tests results and tag images. These changes should allow teams to better split responsibilities, by only allowing the necessary access to specific users/groups.

Deprecations and ABI/API breaks


No known regressions.


No known deprecations


No known 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 apertis-base, apertis-image-builder, apertis-package-source-builder, apertis-flatdeb-builder, apertis-documentation-builder, and apertis-testcases-builder, Docker images.


Image daily builds, as well as release builds can be found at https://images.apertis.org/

Infrastructure overview

The Apertis Image Recipes provides an overview of the image building process and the involved services.

Known issues



  • Issue #7 Crash when initialising egl on ARM target
  • Issue #9 System users are shipped in /usr/etc/passwd instead of /lib/passwd
  • Issue #12 gettext-i18n: test failed
  • Issue #15 Fix the kernel command line generation in OSTRee for FIT image
  • Issue #22 debos sometimes fails to mount things
  • 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 #49 “firmware: failed to load” logs seen during boot
  • Issue #65 Terminal at xfce desktop corrupted after debos call
  • Issue #66 Some binaries in the toolchain tarball are huge
  • Issue #114 ci-package-builder tests fail due to OBS branches not being cleaned up
  • Issue #118 tiny-container-system-connectivity-profile: test failed
  • Issue #154 sdk-cross-compilation: test failed
  • Issue #206 AUM rollback tests fail on UP Squared 6000 board
  • Issue #211 AUM power cut tests fail on UP Squared 6000 board
  • Issue #217 AUM out of space tests fail on UP Squared 6000 board
  • Issue #219 Eclipse-ide-cpp can’t show preview of markdown files (.md)
  • Issue #230 WebProcess CRASHED error is seen on executing webkit related testcases
  • Issue #246 tiny-container-user-connectivity-profile: test failed
  • Issue #247 tiny-container-user-basic: test failed
  • Issue #252 tiny-container-system-basic: test failed
  • Issue #256 OBS: Backend doesn’t start immediately upon restart
  • Issue #257 sdk-performance-tools-gprof: test failed
  • Issue #260 tiny-container-user-folder-sharing: test failed
  • Issue #262 tiny-container-system-aa-enforcement: test failed
  • Issue #272 QA Report App does not handle task-per-release when using Phabricator
  • Issue #273 Debos build output hidden on GitLab job view can only be seen in the raw log file
  • Issue #281 tiny-container-user-aa-enforcement: test failed


  • Issue #23 Remote outputs and local output, buffer size combined in Maynard/GTK
  • Issue #38 LAVA/Phab bridge timeouts
  • Issue #40 evolution-sync-bluetooth test not available in v2022 and v2023dev1 testcase page
  • Issue #45 Manual testcase results should not have any hyperlink in the LavaPhabridge report page
  • Issue #93 “Error: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs” logs seen during bluez-phone test