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 |
Spr |
Newest |
Outdated |
Ignored |
|
muddy-mutt∗
|
1 |
1.5.24 |
|
|
|
mutt∗
|
41 |
1.12.223 |
1.12.18 1.12.02 1.11.46 1.11.35 1.10.114 1.10.02 1.9.52 1.9.42 1.9.3 1.9.2 1.9.12 1.8.3 1.8.22 1.8.0 1.7.24 1.7.1 1.6.1 1.5.242 1.5.233 1.5.215 1.5.21.j1 1.5.202 |
6959.42e2d07a |
|
neomutt∗
|
18 |
2018071618 |
20180622 201805122 201803232 20180223 20171215 |
99999999 20180716.r180.gb6a602e8a |
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).