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 |
Spread |
Newest |
Outdated |
Ignored |
|
abrt∗
|
6 |
2.12.03 |
2.11.0 2.10.102 2.10.9 2.10.8 2.10.7 2.10.4 2.10.3 2.3.0 2.1.112 2.1.7 2.0.12 2.0.10 2.0.82 |
|
|
abrt-addon-python3∗
|
1 |
2.1.11 |
|
|
|
gnome-abrt∗
|
5 |
1.2.72 |
1.2.62 1.2.52 0.3.42 0.3.1 |
|
|
libreport∗
|
7 |
2.10.03 |
2.9.62 2.9.53 2.9.4 2.9.3 2.9.2 2.9.1 2.3.0 2.1.112 2.1.9 2.1.7 2.0.20 2.0.13 2.0.10 2.0.92 |
155127e |
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).