Upstream software project

ignition-msgs

Development libraries and headers for ignition-msgs

About ignition-msgs

Development libraries and headers for ignition-msgs

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

Fedora 43: 3 package records. Catalog coverage diagram, not an application screenshot.ignition-msgs: recorded package coverageFedora 433 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
ignition-msgs
Publisher
Not authoritatively mapped
Native package records
3
Operating systems
fedora-43
License expression
Apache-2.0
Source repository
Not reported

Source-reported description

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

A standard set of message definitions, used by Ignition Transport, and other applications. Contains pre-compiled protobuf definitions of messages for re-use by other libraries and applications.

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.

Fedora 43

  1. Package ignition-msgs

    43 (Fedora 43) (Unspecified): Common messages for the ignition framework

    1.0.0-24.fc43: aarch64 i686 x86_64

    Source: ignition-msgs

  2. Package ignition-msgs-devel

    43 (Fedora 43) (Unspecified): Development libraries and headers for ignition-msgs

    1.0.0-24.fc43: aarch64 i686 x86_64

    Source: ignition-msgs

  3. Package ignition-msgs-doc

    43 (Fedora 43) (Unspecified): Development documentation for ignition-msgs

    1.0.0-24.fc43: noarch

    Source: ignition-msgs

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.