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.
2 project(s) on this page
| Project |
Spread |
Newest |
Outdated |
Ignored |
|
dos2unix∗
|
36 |
7.4.033 |
7.3.54 7.3.47 7.3.32 7.3.2 7.3.1 7.3 7.2.3 7.2.2 7.2.1 7.2 7.1 7.0 6.0.6 6.0.5 6.0.42 6.0.33 6.0.22 6.0.1 6.0 5.3.3 5.3.2 5.3.12 5.3 5.2 5.1.1 5.1 3.13 1.0.3 1.0.1 1.0 |
7.4.0.r0.g1182533 |
|
hd2u∗
|
4 |
1.0.42 |
1.0.32 |
|
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).