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 v2026dev2 is the third development release of the Apertis v2026 stable release flow that will lead to the Apertis v2026.0 release in March 2026.

This Apertis release is the first based on Debian Trixie and on top of it provides several customizations. It ships the latest Linux kernel in 6.12.x series but later releases in the v2026 channel will be tracking newer kernel versions up to the next LTS.

Test results for the v2026dev2 release are available in the following test reports:

Since this release is the first development release after the rebase on top of Debian Trixie no manual testing has been performed.

Release flow

  • 2024 Q4: v2026dev0
  • 2025 Q1: v2026dev1
  • 2025 Q2: 2026dev2
  • 2025 Q3: v2026dev3
  • 2025 Q4: v2026pre
  • 2026 Q1: v2026.0
  • 2026 Q2: v2026.1
  • 2026 Q3: v2026.2
  • 2026 Q4: v2026.3
  • 2027 Q1: v2026.4
  • 2027 Q2: v2026.5
  • 2027 Q3: v2026.6
  • 2027 Q4: v2026.7

Release downloads

Apertis v2026dev2.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 v2026dev2 package list

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

Apertis v2026dev2 repositories

deb https://repositories.apertis.org/apertis/ v2026dev2 target development sdk non-free

New features

New versions of core packages

As part of the rebase on top of Debian Bookworm all the packages have been updated. As a summary this is a list of the packages available:

Build and integration

Delta review and cleaning

As part of the rebase, all the packages were upgraded to the version available in Debian Trixie. During this process, the Apertis specific changes, known as delta, were reviewed and cleaned, improving the codebase.

Germinate improvements

A rebase a very demanding task, which requires a careful planning and tracking. To support these activities, the Apertis team have improved the germinate repo with additional tooling to make this process friendlier.

Deprecations and ABI/API breaks

Regressions

No known regressions.

Deprecations

No known deprecations

Breaks

No known breaks

Infrastructure

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.

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

High

  • Issue #615 aum-offline-upgrade-branch: test failed
  • Issue #636 WiFi connection does not bring up after reboot
  • Issue #695 aum-rollback-bootcount: error message displayed during the test
  • Issue #731 Investigate license issue with golang-github-juju-ratelimit and golang-github-juju-ansiterm
  • Issue #752 Unable to test audio policies in armhf
  • Issue #790 scan-copyrights provides different results on different runs
  • Issue #796 dh_setup_copyright does not perform well on big packages
  • Issue #801 initramfs-tools is not able to include all the needed modules
  • Issue #802 Image pipeline detects GPL-3 code
  • Issue #805 aum-ota-api: test failed
  • Issue #806 publishing issue due to sync2aptly miscalculates which version is newer
  • Issue #810 aum-api: test failed
  • Issue #811 aum-ota-rollback-blacklist: test failed
  • Issue #812 aum-ota-out-of-space: test failed
  • Issue #813 Investigate license issue for rust-ansi-colours
  • Issue #822 Image for ls1028ardb cannot be built
  • Issue #824 apparmor: test failed
  • Issue #825 apparmor-dbus: test failed
  • Issue #827 aum-offline-upgrade: test failed
  • Issue #828 aum-offline-upgrade-signed: test failed
  • Issue #829 aum-ota-auto: test failed
  • Issue #830 aum-ota-signed: test failed
  • Issue #831 aum-out-of-space: test failed
  • Issue #832 aum-power-cut: test failed
  • Issue #833 aum-rollback-blacklist: test failed
  • Issue #834 aum-rollback-blacklist: test failed
  • Issue #835 sanity-check: test failed

Normal

  • Issue #7 Crash when initialising egl on ARM target
  • Issue #9 System users are shipped in /usr/etc/passwd instead of /lib/passwd
  • Issue #32 Gitlab pipeline OBS job reported “success” but OBS build was “unresolvable”
  • Issue #49 “firmware: failed to load” logs seen during boot
  • Issue #66 Some binaries in the toolchain tarball are huge
  • Issue #256 OBS: Backend doesn’t start immediately upon restart
  • Issue #273 Debos build output hidden on GitLab job view can only be seen in the raw log file
  • Issue #331 Frequent 504 Errors repeatedly causing pipelines to be marked as failed
  • Issue #339 Up Squared 6000 board fails to boot randomly in LAVA
  • Issue #377 import-debian-package issues during package import
  • Issue #396 Pipeline to build package fails during build-source for texlive-extra
  • Issue #413 obs-runner: Disabled architectures on a OBS package get re-enabled when CI creates a branch
  • Issue #459 tiny-container-system-device-sharing: test failed
  • Issue #462 agl-compositor mute functionality not working
  • Issue #486 “webkit2gtk-ac-3d-rendering” fails in “ARMHF”.
  • Issue #490 gpgv (sequioa) crashes when added debian archives
  • Issue #528 OBS runner creates conflicts in the origin repo, then waits forever for them
  • Issue #537 Update some apertis gitlab-ci pipeline to use a bookworm image instead of a bullseye/buster image
  • Issue #597 obs runner is confused by multple OBS repos
  • Issue #602 lintian: the child pipeline lintian-errors is always triggered on the default branch instead of the same branch as the parent job
  • Issue #603 AUM upgrade branch fails on amd64 on all releases
  • Issue #633 dashboard: issues just after a branching
  • Issue #637 Improve the repo/pipeline used to test the lintian job
  • Issue #638 Improve the repos/pipelines used to test the abi-checker job
  • Issue #639 apertis-dev depends on eatmydata that was dropped during the rebase on Bookworm
  • Issue #643 Improve the tool import-debian-package to trigger the generation of debian/apertis/copyright on an initial import.
  • Issue #656 Improve apertis-pkg-* tools (from apertis-dev-tools) to use python-gitlab instead of relying on urllib
  • Issue #659 Remove “hmi” repository from website documentation
  • Issue #664 Improve workflow for importing packages
  • Issue #665 Write a python tool to generate apertis-oslist.json (for rpi-imager)
  • Issue #675 pkg/debugpy: investigate tests failure at build time
  • Issue #678 Test pipeline of ci-flatdeb-builder triggers too many (5) MR pipelines
  • Issue #691 tiny-container-system-connectivity-profile: test failed
  • Issue #692 tiny-container-user-connectivity-profile: test failed
  • Issue #702 Improve delta tracking in linux package
  • Issue #703 Add recommendations about gitignore usage
  • Issue #721 Improve checks on folding/branching
  • Issue #734 qa-parser relies on lqa which is unmaintained
  • Issue #736 OBS: the build of some packages disturbs OBS behaviour
  • Issue #742 dashboard reports Git repository contains an untracked debian branch debian/bullseye
  • Issue #754 ci-license-scan hangs on u-boot
  • Issue #780 tiny-container-user-basic: test failed
  • Issue #784 dashboard: report packages with a debian/apertis/pre-scan-hook
  • Issue #789 Move import-debian-package to apertis-infrastructure
  • Issue #795 rust-coreutils date is unable to parse UTC date
  • Issue #814 tiny-container-system-aa-enforcement: test failed
  • Issue #815 tiny-container-system-basic: test failed
  • Issue #818 tiny-container-user-aa-enforcement: test failed
  • Issue #823 plymouth raises warnings on install
  • Issue #826 apparmor-functional-demo: test failed
  • Issue #836 apparmor-gstreamer1-0: test failed
  • Issue #837 apparmor-ofono: test failed
  • Issue #838 apparmor-pipewire: test failed

Low

  • Issue #15 Fix the kernel command line generation in OSTRee for FIT image
  • Issue #23 Remote outputs and local output, buffer size combined in Maynard/GTK
  • Issue #65 Terminal at xfce desktop corrupted after debos call
  • Issue #607 Pipeline for sample application helloworld-https-client fails