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
|| 2.10.0+git20210727.2.a65ecab▲ 2.10.0▲13 2.9.2▲2 2.9.1▲3 2.9.0▲ 188.8.131.52▲ 2.8.8▲8 2.8.6▲ 2.8.0~cvs20150510▲ 2.7▲12 2.6.1▲
|| 184.108.40.206 220.127.116.11 1.29.3 1.28+cvs20151130 1.2812 1.26
|| 0.0.67 0.0.59
|| 0.0.7.r2.g95c4bd8 0.0.7+git20210316.1.95c4bd8
- Spread means how many repository families (e.g. all Debian versions as well as Ubuntu and other derivatives make 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 the 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).
- vulnerable▲ - version is potentially vulnerable as there are related CVEs.