Related projects are determined by recursively matching package homepage URLs. Note that this list may be incomplete as Repology may not be able to get homepage URLs from some repositories.
4 project(s) on this page
| Project |
Spr |
Newest |
Outdated |
Ignored |
|
corosync∗
|
15 |
3.0.35 |
3.0.23 3.0.12 3.0.0 2.99.3 2.4.52 2.4.47 2.4.35 2.4.24 2.4.1 2.4.03 2.3.6 2.3.53 2.3.43 2.3.34 2.3.2 1.4.8 1.4.73 1.4.6 1.4.2 1.4.1 1.3.5 1.2.0 |
3.0.2.r18.g0a323ff2 3.0.3.0.18.g89b0d |
|
corosync-qdevice∗
|
4 |
3.0.04 |
2.92.0 2.90.0 |
|
|
corosync2∗
|
1 |
2.4.5 |
|
|
|
corosync3∗
|
1 |
2.99.5 |
|
|
Legend:
- Spread means how many repository families (e.g. all Debian versions are a single family) contain this package.
- newest#repos - newest known version. The number shows how many repository families have this version.
- devel - newest known devel (or unstable) version. There may be both devel and newest versions for a given package.
- unique - package is only present in a single repository family, there are no other sources to compare it against, so although it's latest version known to repology, is not really reliable.
- outdated - outdated version which requires updating.
- legacy - outdated version when a newer version is present. This is assumed to be legacy version preserved for e.g. compatibility.
- rolling - package is fetched from always latest snapshot or VCS master/trunk, so it is always latest and is not a subject for comparison.
- noscheme - the project does not have official versioning scheme, so versions used in repositories which are basically random.
- incorrect - version is known to be incorrect (e.g. version not officially released yet, or lacking alpha/beta/rc qualifier).
- untrusted - this source is known to likely supply incorrect versions, so is ignored proactively.
- ignored - version is ignored and excluded from comparison for some other reason (e.g. snapshots).