Linux workstation

Upstream software project

mopidy-mpd

Mopidy extension for controlling Mopidy from MPD clients

About mopidy-mpd

Mopidy extension for controlling Mopidy from MPD clients

This project links 2 native package records across 2 recorded operating-system releases. 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.

Visit project website

Project pictures and package coverage

Fedora 43: 1 package records; Fedora 44: 1 package records. Catalog coverage diagram, not an application screenshot.mopidy-mpd: recorded package coverageFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
mopidy-mpd
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43, fedora-44
License expression
Apache-2.0
Metadata completeness
100/100 (not a software quality rating)
Homepage
Visit upstream site
Source repository
Not reported

Source-reported description

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

Frontend that provides a full MPD server implementation to make Mopidy available from MPD clients.

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. mopidy-mpd

    Fedora 43 / Unspecified / source mopidy-mpd

    4.0.0~a1-5.fc43

    Mopidy extension for controlling Mopidy from MPD clients

    noarch43

Fedora 44

  1. mopidy-mpd

    Fedora 44 / Unspecified / source mopidy-mpd

    4.0.0~a4-1.fc44

    Mopidy extension for controlling Mopidy from MPD clients

    noarch44

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.