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 v2025dev2 is the second development release of the Apertis v2025 stable release flow that will lead to the LTS Apertis v2025.0 release in March 2025.
This Apertis release is built on top of Debian Bookworm along with several customizations and it ships the latest Linux kernel 6.7.x series. Later releases in the v2025 channel will be tracking newer kernel versions up to the next LTS as well as Debian Bookworm Stable Channel.
Test results for the v2025dev2 release are available in the following test reports:
Release flow
- 2023 Q4: v2025dev0
- 2024 Q1: v2025dev1
- 2024 Q2: v2025dev2
- 2024 Q3: v2025dev3
- 2024 Q4: v2025pre
- 2025 Q1: v2025.0
- 2025 Q2: v2025.1
- 2025 Q3: v2025.2
- 2025 Q4: v2025.3
- 2026 Q1: v2025.4
- 2026 Q2: v2025.5
- 2026 Q3: v2025.6
- 2026 Q4: v2025.7
Release downloads
| Apertis v2025dev2.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 v2025dev2 package list
The full list of packages available from the v2025dev2 APT repositories is available in tab-separated value (TSV) format for easy processing in spreadsheets:
Apertis v2025dev2 repositories
deb https://repositories.apertis.org/apertis/ v2025dev2 target development sdk non-free
New features
Improved SBOM for licensing
Continuing with the work of improving the SBOM for licensing, now the report includes license and copyright information for non binary files, such as scripts and configuration. With this new enhancement Apertis’ SBOM provides more accurate information about licensing for the standard images.
Build and integration
Test on MR configuration
Running test on MR has shown to be a key new feature in Apertis, allowing both developers and maintainers to ensure the sanity of the changes before they land. Following this idea different types of test are available, such as package centric, integration and bootstrap test. To improve readability and avoid misunderstandings, the configuration settings were adapted, becoming more natural.
Test on MR for linux
Continuing with the trend on adding test on MR, a set of custom tests have been implemented for the linux kernel. As this is a very special package with delta respect to Debian additional checks are now performed, to ensure that changes proposed by developers don’t cause regression and simplifying the review and test process.
Deprecations and ABI/API breaks
Regressions
No known regressions.
Deprecations
No known deprecations
Breaks
Package libgiod v2
In order to overcome limitations in libgiod v1 (1.6.3) it has been upgraded to its new upstream release v2 (2.1-1). This change introduces small API changes that need to be addressed by developers.
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 #364 aum-offline-upgrade-branch: test failed
- Issue #419 High level tracking of AUM issues
- Issue #431 Package rust-coreutils does not provide license mapping information
- Issue #485 AUM tests fail on v2024 and v2025dev* armhf
- Issue #490 gpgv (sequioa) crashes when added debian archives
- Issue #581 aum-offline-upgrade-signed: test failed
Normal
- Issue #7 Crash when initialising egl on ARM target
- 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 #273 Debos build output hidden on GitLab job view can only be seen in the raw log file
- Issue #322 wrap-and-sort fails to parse some debian/control.in files
- Issue #330 datefudge: 64-bit time_t support on 32-bit archs
- 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 #405 traprain: test failed
- Issue #413 obs-runner: Disabled architectures on a OBS package get re-enabled when CI creates a branch
- Issue #448 ade-commands: test failed
- Issue #459 tiny-container-system-device-sharing: test failed
- Issue #486 “webkit2gtk-ac-3d-rendering” fails in “ARMHF”.
- Issue #488 Flashing an HMI image on the eMMC of R-car H3e-2G board leads to a kernel panic.
- Issue #491 AM62x: Do not install firmware prerequisites in image for boot firmware generation
- Issue #525 RPi image list points to v2022 instead of daily development images
- 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 #539 Create automatic sdk tests in apertis-test-cases for abi-checker job
- Issue #541 QA Report App is not able to login
- Issue #554 import-debian-package doesn’t trigger the pipeline adding a debian/apertis/copyright file
- Issue #578 qa report application creates multiple entries per issue
- Issue #586 sdk-import-debian-package: test failed
- 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