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.
3 project(s) on this page
| Project |
Spread |
Newest |
Outdated |
Ignored |
|
audit∗
|
22 |
2.8.56 |
2.8.412 2.8.33 2.8.23 2.8.12 2.7.8 2.7.73 2.7.62 2.7.4 2.7.1 2.6.7 2.6.52 2.6.4 2.5.2 2.4.53 2.4.4 2.4.1 2.4 2.3.7 2.3.62 2.3.3 2.3.23 2.1.2 1.7.18 |
3.0 |
|
audit-secondary∗
|
1 |
2.8.4 |
2.8.1 2.3.6 |
|
|
auditd-openrc∗
|
1 |
20161001 |
|
|
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).