Upstream software project

libqtdbusmock

Library for mocking DBus interactions using Qt

About libqtdbusmock

Library for mocking DBus interactions using Qt

This project links 3 native package records across 1 recorded operating-system release. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Debian 13 (Trixie): 3 package records. Catalog coverage diagram, not an application screenshot.libqtdbusmock: recorded package coverageDebian 13 (Trixie)3 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
libqtdbusmock
Publisher
Not authoritatively mapped
Native package records
3
Operating systems
debian-13
License expression
Not reported
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Library for mocking DBus interactions using Qt (development files)

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 13 (Trixie)

  1. Package libqtdbusmock1

    trixie (Debian 13 (Trixie)) (libs): Library for mocking DBus interactions using Qt

    0.9.1-3: amd64 arm64

    Source: libqtdbusmock

  2. Package libqtdbusmock1-common

    trixie (Debian 13 (Trixie)) (libs): Library for mocking DBus interactions using Qt (common files)

    0.9.1-3: all

    Source: libqtdbusmock

  3. Package libqtdbusmock1-dev

    trixie (Debian 13 (Trixie)) (libdevel): Library for mocking DBus interactions using Qt (development files)

    0.9.1-3: amd64 arm64

    Source: libqtdbusmock

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.