Upstream software project

erlang-riak_core

Distributed systems infrastructure used by Riak

About erlang-riak_core

Distributed systems infrastructure used by Riak

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.

Project pictures and package coverage

erlang-riak_core repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Fedora 43: 1 package records; Fedora 44: 1 package records. Catalog coverage diagram, not an application screenshot.erlang-riak_core: recorded package coverageFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
erlang-riak_core
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43, fedora-44
License expression
Apache-2.0 and ErlPL-1.1 and MIT and MPL-1.1
Source repository
Open source repository

Source-reported description

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

Distributed systems infrastructure used by Riak.

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 erlang-riak_core

    43 (Fedora 43) (Unspecified): Distributed systems infrastructure used by Riak

    3.0.16-4.fc43: noarch

    Source: erlang-riak_core

Fedora 44

  1. Package erlang-riak_core

    44 (Fedora 44) (Unspecified): Distributed systems infrastructure used by Riak

    3.0.16-4.fc44: noarch

    Source: erlang-riak_core

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.