Upstream software project

peony

libraries for Peony components

About peony

libraries for Peony components

This project links 4 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): 4 package records. Catalog coverage diagram, not an application screenshot.peony: recorded package coverageDebian 13 (Trixie)4 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
peony
Publisher
Not authoritatively mapped
Native package records
4
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.

libraries for Peony components (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 libpeony3t64

    trixie (Debian 13 (Trixie)) (libs): libraries for Peony components

    4.0.0.2-1: amd64 arm64

    Source: peony

  2. Package libpeony-dev

    trixie (Debian 13 (Trixie)) (libdevel): libraries for Peony components (development files)

    4.0.0.2-1: amd64 arm64

    Source: peony

  3. Package peony

    trixie (Debian 13 (Trixie)) (utils): file Manager for the UKUI desktop

    4.0.0.2-1: amd64 arm64

  4. Package peony-common

    trixie (Debian 13 (Trixie)) (utils): file manager for the UKUI desktop (common files)

    4.0.0.2-1: all

    Source: peony

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.