Unable to install libdrm-tests in torizon/weston-am62:4

It seems that I cannot install libdrm-tests in torizon/weston-am62:4 (I have also tried torizon/qt6-wayland-examples-am62:4 with the same result). Are the versions somehow freezed or TI packages conflicting there?

root@verdin-am62-15478822:/# mkdir -p /var/lib/dpkg /var/cache/apt/archives/partial
apt update
Get:1 http://deb.debian.org/debian bookworm-backports InRelease [59.4 kB]
Get:2 http://deb.debian.org/debian bookworm InRelease [151 kB]                      
Get:3 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]
Get:4 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]
Get:5 https://feeds.toradex.com/stable/am6x/snapshots/20251217T210750Z stable InRelease [27.4 kB]
Get:6 http://deb.debian.org/debian bookworm-backports/main arm64 Packages [300 kB]
Get:7 http://deb.debian.org/debian bookworm/main arm64 Packages [8691 kB]
Get:8 http://deb.debian.org/debian bookworm-updates/main arm64 Packages [6936 B]
Get:9 http://deb.debian.org/debian-security bookworm-security/main arm64 Packages [291 kB]
Get:10 https://feeds.toradex.com/stable/am6x/snapshots/20251217T210750Z stable/non-free arm64 Packages [6696 B]
Get:11 https://feeds.toradex.com/stable/am6x/snapshots/20251217T210750Z stable/main arm64 Packages [45.9 kB]
Fetched 9683 kB in 6s (1667 kB/s)                      
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
N: Repository 'Debian bookworm' changed its 'non-free component' value from 'non-free' to 'non-free non-free-firmware'
N: More information about this can be found online in the Release notes at: https://www.debian.org/releases/bookworm/arm64/release-notes/ch-information.html#non-free-split
root@verdin-am62-15478822:/# apt install libdrm-tests
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libdrm-tests : Depends: libdrm2 (= 2.4.114-1+b1) but 2.4.123-1~bpo12+1 is to be installed
E: Unable to correct problems, you have held broken packages.

I am using Torizon OS 7.5.0 (Easy Pairing) on Verdin AM62.

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.


The error you’re encountering is due to a version conflict between the libdrm-tests package and the version of libdrm2 that’s installed in the Toradex container(1). The libdrm-tests package requires libdrm2 version 2.4.114-1+b1, but your container has version 2.4.123-1~bpo12+1 installed(1).

Understanding the Issue

The Torizon Debian containers are based on Debian Bookworm and include both standard Debian packages and Toradex-specific packages from the Toradex feeds(1). In your case, the container appears to have a newer version of libdrm2 from the backports repository, which creates a dependency conflict with libdrm-tests.

Recommended Solutions

Option 1: Use a Custom Container

Create a custom container based on the Torizon container and install the specific version you need(2). You can modify the torizonPackages.json file to manage package dependencies(2).

Option 2: Try Alternative Package Installation

You could try installing the specific version of libdrm2 that matches the libdrm-tests requirements, though this might affect other components in the container.

Option 3: Use Development Workflow

If you’re developing an application that needs these testing tools, consider using the Torizon IDE Extension development workflow(2). The extension provides templates and tools for adding dependencies to development containers through the torizonPackages.json file(2).

Package Management Best Practices

When working with Torizon containers, it’s recommended to:

  • Use the torizonPackages.json file for package management in IDE Extension projects(2)
  • Add packages to the appropriate arrays (devRuntimeDeps, prodRuntimeDeps, or buildDeps) based on your needs(2)
  • Test package compatibility in development containers before deploying to production(2)

The Torizon containers are extensively tested configurations, and package version conflicts like this can occur when mixing different repository sources or when specific package versions have strict dependencies.

Best regards, Toradex AI Assistant.


Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

Greetings @vilchanskyio,

Due to dependency and version requirements the container image for AM62 installs the bookworm-backports version of libdrm2 as seen here: torizon-containers/platform-specific/am62/wayland-base/Dockerfile at stable · torizon/torizon-containers · GitHub

As you noticed this isn’t compatible with libdrm-tests from the standard Debian feeds. You can install libdrm-tests/bookworm-backports instead. This will match the libdrm2 that is installed already so you won’t have dependency issues from apt. If the exact version of libdrm-tests isn’t important to you, then this would be the best solution.

Best Regards,
Jeremias

Aha, somehow haven’t noticed that by looking at dockerfiles. Sorry! And thanks for the quick reply, the package installs successfully now.

Glad I was able to help.

Best Regards,
Jeremias